[MetaCipher]

I am running v9.04 Beta 1 (though I've also tried this on the stable 8.10). Whenever I have XBMC set to auto-start (right click and set to open at login), the web server will not work. But if I close XBMC, and then reopen it, the web server works correctly. Does anyone know of a way to fix this?

Thanks.

[althekiller]

Perhaps your network interface isn't ready yet when the auto start happens? Pastebin a full debug log.

[MetaCipher]

http://pastebin.com/f122fe5e6

Edit:
This second debug log is with me trying to connect to the web server (if it's possibly a connection issue). The first is a simple startup log.
http://pastebin.com/f4047c386

[MetaCipher]

Bump. Nothing?

[sircube]

interesting, this problem has been reported to be fixed after Atlantis bf1 release. Looks it was not related to the eth0 status. Had no time to check whether fix was successful or not at that time but looked to be an XBMC application-level glitch.
Seems now it comes again with Babylon.

see: http://forum.xbmc.org/showthread.php?tid=47238

[MetaCipher]

I checked out the SVN, seems that the change is still there. I'm wondering if this is something Mac OS X specific.

[davilla]

I checked out the SVN, seems that the change is still there. I'm wondering if this is something Mac OS X specific.

are you wired or wireless, dhcp or static?

post the output of "ifconfig".

[MetaCipher]

I am wired with a static IP.

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::217:f2ff:fef3:6e77%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.90 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:17:f2:f3:6e:77
media: autoselect (100baseTX <full-duplex,flow-control>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loop
back> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-l
oopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <ful
l-duplex,flow-control> none
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:19:e3:03:a4:dc
media: autoselect (<unknown type>) status: inactive
supported media: autoselect
wlt1: flags=41<UP,RUNNING> mtu 1500
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:19:e3:ff:fe:1d:64:ce
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
tap0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 74:61:70:00:00:00
closed
tun0: flags=8850<POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
closed

[davilla]

not a clue, wired, static should be up pretty quick.

http://harrybailey.com/2008/12/delay-log...ng-idrive/

[MetaCipher]

I noticed a new release just came out a few minutes ago. I'll download that, and then try the startup script. I'll report back. Thanks.

[davilla]

might also try disabling ip6.

[MetaCipher]

The delayed startup script has fixed it (though I also disabled IPv6). Thanks. My general assumption is that somehow the network is not ready when XBMC starts up the web server.

[Fiasco]

Is there a way to make the webserver restart automaticaly when it crashes?

[davilla]

Is there a way to make the webserver restart automaticaly when it crashes?

It's not polite to hi-jack a thread, start a new one with a pastebin of xbmc.log/crash log if you have a crash problem.