tullytv 1 Posted August 22, 2019 Share Posted August 22, 2019 Ubuntu 18.04 # systemctl status emby-server ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2019-08-22 15:23:00 EDT; 4s ago Process: 31627 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS) Main PID: 31627 (code=exited, status=0/SUCCESS) Aug 22 15:23:00 Dragon emby-server[31627]: at SocketHttpListener.Net.HttpEndPointManager.AddPrefixInternal(ILogger logger, Strin Aug 22 15:23:00 Dragon emby-server[31627]: at SocketHttpListener.Net.HttpEndPointManager.AddListener(ILogger logger, HttpListene Aug 22 15:23:00 Dragon emby-server[31627]: at SocketHttpListener.Net.HttpListener.Start() Aug 22 15:23:00 Dragon emby-server[31627]: at Emby.Server.Implementations.ApplicationHost.StartServer() Aug 22 15:23:00 Dragon emby-server[31627]: at Emby.Server.Implementations.ApplicationHost.Init() Aug 22 15:23:00 Dragon emby-server[31627]: at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Aug 22 15:23:00 Dragon emby-server[31627]: Source: SocketHttpListener Aug 22 15:23:00 Dragon emby-server[31627]: TargetSite: SocketHttpListener.Net.HttpEndPointListener GetEPListener(MediaBrowser.Model Aug 22 15:23:00 Dragon emby-server[31627]: Aug 22 15:23:00 Dragon emby-server[31627]: Info Main: Shutdown complete Log attached. Tried re downloading wget https://github.com/MediaBrowser/Emby.Releases/releases/download/4.2.1.0/emby-server-deb_4.2.1.0_amd64.deb (deleting old once first) Then starting server systemctl start emby-server Nothing seems to work Link to comment Share on other sites More sharing options...
Luke 37358 Posted August 22, 2019 Share Posted August 22, 2019 Hi, looks like the server is being denied access to the port. Can you try rebooting your machine? Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 I've done that 3 times so far. I'd try again now. Any other suggestions? What port is being denied? Link to comment Share on other sites More sharing options...
Luke 37358 Posted August 22, 2019 Share Posted August 22, 2019 Was any emby server log generated? Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 Log files before and after a reboot embyserver.txt embyserver-63702085368.txt Link to comment Share on other sites More sharing options...
Luke 37358 Posted August 22, 2019 Share Posted August 22, 2019 Can you try running as sudo? You shouldn't have to do that, but we need to find out why access is being denied to the port. Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 Im logged in as root root@Dragon:~# sudo service emby-server start root@Dragon:~# sudo systemctl status emby-server ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2019-08-22 15:57:54 EDT; 17s ago Process: 12267 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=0/SUCCESS) Main PID: 12267 (code=exited, status=0/SUCCESS) Aug 22 15:57:54 Dragon emby-server[12267]: at SocketHttpListener.Net.HttpEndPointManager.AddPrefixInternal(ILogger logger, Strin Aug 22 15:57:54 Dragon emby-server[12267]: at SocketHttpListener.Net.HttpEndPointManager.AddListener(ILogger logger, HttpListene Aug 22 15:57:54 Dragon emby-server[12267]: at SocketHttpListener.Net.HttpListener.Start() Aug 22 15:57:54 Dragon emby-server[12267]: at Emby.Server.Implementations.ApplicationHost.StartServer() Aug 22 15:57:54 Dragon emby-server[12267]: at Emby.Server.Implementations.ApplicationHost.Init() Aug 22 15:57:54 Dragon emby-server[12267]: at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Aug 22 15:57:54 Dragon emby-server[12267]: Source: SocketHttpListener Aug 22 15:57:54 Dragon emby-server[12267]: TargetSite: SocketHttpListener.Net.HttpEndPointListener GetEPListener(MediaBrowser.Model Aug 22 15:57:54 Dragon emby-server[12267]: Aug 22 15:57:54 Dragon emby-server[12267]: Info Main: Shutdown complete lines 1-16/16 (END) Link to comment Share on other sites More sharing options...
Happy2Play 8409 Posted August 22, 2019 Share Posted August 22, 2019 Not sure if these two topics are related as they are different OSes but this users ended up restarting multiple times. https://emby.media/community/index.php?/topic/76530-server-wont-start-if-port-not-available/ Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 I'm willing to keep restarting it, not sure what on the server side would be blocking the port. UFW is inactive Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 (edited) Removed Edited August 22, 2019 by tullytv Link to comment Share on other sites More sharing options...
Happy2Play 8409 Posted August 22, 2019 Share Posted August 22, 2019 Ideally you should use the Server Configuration Backup plugin. But depending on what exactly you are trying to do you may be able to transfer your "Program data path: /var/lib/emby-server" to your new install. As that folder contains all Emby's config and userdata. Link to comment Share on other sites More sharing options...
Happy2Play 8409 Posted August 22, 2019 Share Posted August 22, 2019 Did you try running the netstat command and look at your configure ports? If you run netstat -an from a command prompt then you can see all port assignments. Look for any entries already assigned to 8096 or 8920. Link to comment Share on other sites More sharing options...
sargenthp 29 Posted August 22, 2019 Share Posted August 22, 2019 Something already running on that port? Try shutting down emby server. Then run: sudo netstat -an | egrep '8096|443' See if anything shows up. You could also try: sudo fuser 8096/tcp And see if it lists any PIDS that then you could look for. Sent from my PH-1 using Tapatalk Link to comment Share on other sites More sharing options...
Q-Droid 673 Posted August 22, 2019 Share Posted August 22, 2019 (edited) Had you modified the emby-server service to run as a user other than emby before the upgrade? Had you run setuid on the server executable to run as root? You are trying to bind to port 443 which the emby user can't do out of the box. I'm guessing that on the previous version you had tweaked some things to allow binding to 443. Starting/stopping the service as root doesn't change the runtime user. Whatever you did before you have to repeat after the upgrade or reset the HTTPS port back to the default. Edited August 22, 2019 by Q-Droid Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 Something already running on that port? Try shutting down emby server. Then run: sudo netstat -an | egrep '8096|443' See if anything shows up. >>> sudo netstat -an | egrep '8096|443' tcp6 0 0 :::35443 :::* LISTEN You could also try: sudo fuser 8096/tcp >>> Nothin And see if it lists any PIDS that then you could look for. Sent from my PH-1 using Tapatalk Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 Did you try running the netstat command and look at your configure ports? Doesnt seem anything else is using 8096 netstat -an Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:39925 0.0.0.0:* LISTEN tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3322 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:56573 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:7878 0.0.0.0:* LISTEN tcp 0 0 10.1.10.9:47564 10.1.10.21:445 ESTABLISHED tcp 0 0 10.1.10.9:33492 10.1.10.19:445 ESTABLISHED tcp 0 0 10.1.10.9:855 10.1.10.3:2049 ESTABLISHED tcp 0 0 10.1.10.9:3322 10.1.10.3:46394 ESTABLISHED tcp 0 0 10.1.10.9:3322 10.1.10.1:27974 ESTABLISHED tcp 0 0 10.1.10.9:3322 10.1.10.1:27973 ESTABLISHED tcp 0 0 10.1.10.9:8080 10.1.10.1:27949 ESTABLISHED tcp 0 0 10.1.10.9:8080 10.1.10.9:49828 TIME_WAIT tcp 0 0 10.1.10.9:8080 10.1.10.9:49830 TIME_WAIT tcp6 0 0 :::139 :::* LISTEN tcp6 0 0 :::111 :::* LISTEN tcp6 0 0 :::10000 :::* LISTEN tcp6 0 0 :::33907 :::* LISTEN tcp6 0 0 :::35443 :::* LISTEN tcp6 0 0 ::1:6010 :::* LISTEN tcp6 0 0 :::3322 :::* LISTEN tcp6 0 0 :::445 :::* LISTEN tcp6 0 0 :::9090 :::* LISTEN udp 0 0 0.0.0.0:35399 0.0.0.0:* udp 0 0 0.0.0.0:35465 0.0.0.0:* udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 0.0.0.0:56173 0.0.0.0:* udp 0 0 0.0.0.0:10000 0.0.0.0:* udp 0 0 127.0.0.53:53 0.0.0.0:* udp 0 0 0.0.0.0:68 0.0.0.0:* udp 0 0 0.0.0.0:68 0.0.0.0:* udp 0 0 0.0.0.0:111 0.0.0.0:* udp 0 0 10.1.10.255:137 0.0.0.0:* udp 0 0 10.1.10.4:137 0.0.0.0:* udp 0 0 10.1.10.255:137 0.0.0.0:* udp 0 0 10.1.10.9:137 0.0.0.0:* udp 0 0 0.0.0.0:137 0.0.0.0:* udp 0 0 10.1.10.255:138 0.0.0.0:* udp 0 0 10.1.10.4:138 0.0.0.0:* udp 0 0 10.1.10.255:138 0.0.0.0:* udp 0 0 10.1.10.9:138 0.0.0.0:* udp 0 0 0.0.0.0:138 0.0.0.0:* udp 0 0 127.0.0.1:681 0.0.0.0:* udp 0 0 0.0.0.0:800 0.0.0.0:* udp6 0 0 :::53189 :::* udp6 0 0 :::5353 :::* udp6 0 0 :::42261 :::* udp6 0 0 :::59097 :::* udp6 0 0 :::111 :::* udp6 0 0 :::800 :::* raw6 0 0 :::58 :::* Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 22, 2019 Author Share Posted August 22, 2019 Had you modified the emby-server service to run as a user other than emby before the upgrade? >> No Had you run setuid on the server executable to run as root? >> Not sure I fully undrerstand, I ran the dpkg as root You are trying to bind to port 443 which the emby user can't do out of the box. I'm guessing that on the previous version you had tweaked some things to allow binding to 443. Starting/stopping the service as root doesn't change the runtime user. Whatever you did before you have to repeat after the upgrade or reset the HTTPS port back to the default. >> No trying to bind to 8096. Link to comment Share on other sites More sharing options...
Q-Droid 673 Posted August 22, 2019 Share Posted August 22, 2019 This is in your server log file: 2019-08-22 15:42:48.031 Info HttpServer: Adding HttpListener prefix http://+:8096/ 2019-08-22 15:42:48.031 Info HttpServer: Adding HttpListener prefix https://+:443/ 2019-08-22 15:42:48.032 Error App: Error starting http server Link to comment Share on other sites More sharing options...
sargenthp 29 Posted August 23, 2019 Share Posted August 23, 2019 Mind posting your config file... /var/lib/emby/config/system.xml Sent from my PH-1 using Tapatalk Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 23, 2019 Author Share Posted August 23, 2019 Mind posting your config file... /var/lib/emby/config/system.xml Sent from my PH-1 using Tapatalk Attached system.xml Link to comment Share on other sites More sharing options...
Solution sargenthp 29 Posted August 23, 2019 Solution Share Posted August 23, 2019 Try updating to.... <PublicPort>8096</PublicPort> <PublicHttpsPort>8920</PublicHttpsPort> <HttpServerPortNumber>8096</HttpServerPortNumber> <HttpsPortNumber>8920</HttpsPortNumber> <EnableHttps>false</EnableHttps> Sent from my PH-1 using Tapatalk 1 Link to comment Share on other sites More sharing options...
Luke 37358 Posted August 23, 2019 Share Posted August 23, 2019 If the customized https Port is the problem, the next release will be able to recover from that and automatically revert back to default. Historically we always had that in 4.2 it's not recovering and reverting like it should. Granted that's not your solution, it only means the server will handle the situation a little bit better. 1 Link to comment Share on other sites More sharing options...
tullytv 1 Posted August 23, 2019 Author Share Posted August 23, 2019 Try updating to.... <PublicPort>8096</PublicPort> <PublicHttpsPort>8920</PublicHttpsPort> <HttpServerPortNumber>8096</HttpServerPortNumber> <HttpsPortNumber>8920</HttpsPortNumber> <EnableHttps>false</EnableHttps> Sent from my PH-1 using Tapatalk It worked!!! Thank you! 1 Link to comment Share on other sites More sharing options...
sargenthp 29 Posted August 23, 2019 Share Posted August 23, 2019 Sweet! You are welcome! Sent from my PH-1 using Tapatalk Link to comment Share on other sites More sharing options...
bandolerissimo 0 Posted May 8, 2020 Share Posted May 8, 2020 Hi, very same issue here, on manjaro. I checked my system.xml and it is already coerent with sargenthp suggestion. What else to try? cheers Link to comment Share on other sites More sharing options...
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