Question about 3.0.5781.4

[devshack 0]

The Update of 3.0.5781.4 kill my Emby Server permanent. Rollback of previous not possible. what is the Problem?

server-63584557159.txt

Edited December 1, 2015 by devshack

[Tranquil 94]

The Port of the Server was still in use so the new instance could not create a listening socket.

 

I had this problem in the past - sometimes - when I run Emby as a service and not in stand alone mode.

Because of this, I would suggest you to update Emby when Emby is not running as a service. The old instance was not stopped and therefore, the new instance could not be created.

[MSattler 390]

The Port of the Server was still in use so the new instance could not create a listening socket.

 

I had this problem in the past - sometimes - when I run Emby as a service and not in stand alone mode.

Because of this, I would suggest you to update Emby when Emby is not running as a service. The old instance was not stopped and therefore, the new instance could not be created.

 

So I actually run Emby as a service as well.  I always make sure to stop the service as well before running the installer for the upgrade.  In nearly every upgrade as of late I run into the same issue.  Now, once the service is stopped, the socket should be freed, but it does not appear to be the case.

 

@@ebr @@Luke Any thoughts on this?  

 

I could understand if this happened because someone ran the installer while the service is still running, but in my case the service is stopped.

[ebr 16187]

Make sure there isn't an ffmpeg process also left running.

 

In any case, restarting the machine should fix it.