On restart web server becomes completely inaccessible

[archangelz 13]

Server seems to be becoming inaccessible during reboots over the couple of month of versions. It seems like every second or third time a new version was being pushed half of the time I would run into a problem where the server stops being accessible even though the process appears to be running in the background without memory leaks. 

 

Looks like the server is stalling out trying to load the http server.

 

2015-11-14 03:47:18.8245 Error - ServerManager: The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

2015-11-14 03:47:18.8245 Error - App: Error starting http server

 

Running 3.0.5781.1 right now on windows 10 but I've seen it stall on a lot of other versions. I can kill the process and start it again but this usually doesn't help. Tried scheduling nightly emby server reloads thinking perhaps it was memory related but that made it worse because of more restarts. Once it gets into this state I don't have a choice other than to reboot the whole machine.

 

Does anyone know what is going on and stop this from happening? I thinking of turning off auto server updates and scheduled reloads until the issue is fixed or I have some kind of workaround that doesn't involve me running a reboot script on my server to monitor when the http isn't accessible.

server-63583069635.txt

Edited November 14, 2015 by archangelz

[Luke 37253]

It looks like you're giving us a log of the restart but the previous log would be more useful so that we can learn why you restarted in the first place.

 

When you see this error:

The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

Try rebooting your system. Sometimes when you restart the server windows will take a little time to release the port from the previous instance. Rebooting will clear it up immediately. This is something that really only happens once in a great while. If you're seeing it with regularity, you're either repeatedly restarting your Emby Server or there's something going on on your system.