casminkey 19 Posted February 27, 2016 Posted February 27, 2016 (edited) I've seen this reported a few times and seems a simple server reboot does the trick, but I've been having this happen every day for the past week or two. From what I can tell, seems to coincide with the Server restart Emby task (scheduled daily @ 3:45am). I've disabled that task to see for sure, then I can setup a Windows scheduled task to reboot the entire server if need be. Just seeing if anyone else has any thoughts or seen something similar? FYI, i'm running Server 2012 R2 Standard, Emby Version 3.0.5871.0. 2016-02-27 03:45:08.8946 Info App: Core startup complete 2016-02-27 03:45:08.9728 Error App: Failed to start UDP Server *** Error Report *** Version: 3.0.5871.0 Command line: C:\Users\Curt\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Curt\AppData\Roaming\Emby-Server Application Path: C:\Users\Curt\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Only one usage of each socket address (protocol/network address/port) is normally permitted System.Net.Sockets.SocketException at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at MediaBrowser.Server.Implementations.Udp.UdpServer.Start(Int32 port) at MediaBrowser.Server.Implementations.EntryPoints.UdpServerEntryPoint.Run() Edited February 27, 2016 by casminkey
Solution Luke 42083 Posted February 27, 2016 Solution Posted February 27, 2016 every once in a while windows will take several minutes to release a bound port. when this happens, the above will occur if you try to rebind before the original assignment has been released. the best way to prevent it from happening is avoiding restarting the server when not needed. 1
casminkey 19 Posted February 29, 2016 Author Posted February 29, 2016 Thanks Luke, it's been smooth sailing since disabling the restarts in scheduled tasks. I may just add a Windows task to kick the server once a week or so.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now