knoker 0 Posted April 10, 2016 Share Posted April 10, 2016 Hello the server runs fine but eventually crashes. Could you please help out? unhandled_0aa54821-40c6-4c6e-9189-0021e833d316.txt unhandled_6aad7264-27c0-4b70-a855-57eec927131d.txt unhandled_953f1699-36f0-4765-a552-718b811925ac.txt Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 10, 2016 Share Posted April 10, 2016 Hi, welcome. Try going to advanced library setup and turning off the realtime monitor. Let us know how it goes. Thanks. Link to comment Share on other sites More sharing options...
knoker 0 Posted April 10, 2016 Author Share Posted April 10, 2016 Thank you for your response. Just turned off, we'll see how it does, usually by morning it doesn't respond to http requests. I'll get back to you soon. Link to comment Share on other sites More sharing options...
knoker 0 Posted April 11, 2016 Author Share Posted April 11, 2016 So far it seems to have solved the problem. Statistically it should have happened by now. Thank you Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 11, 2016 Share Posted April 11, 2016 Well done. Link to comment Share on other sites More sharing options...
knoker 0 Posted April 11, 2016 Author Share Posted April 11, 2016 Nop just crashed again. And the Enable real time monitoring is set to NO. unhandled_babde9e5-7c8e-4c0d-8a1d-dbfac22d4a13.txt unhandled_f239125d-5082-4bc2-8329-6ba07290215c.txt Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 11, 2016 Share Posted April 11, 2016 The first log looks like the realtime monitor, so i would suggest double checking the setting. The second one is different and has been addresses for the next release. You could get it now but you'd have to switch to the beta docker package. Link to comment Share on other sites More sharing options...
knoker 0 Posted April 11, 2016 Author Share Posted April 11, 2016 If this is the setting you are referring to its off, at least on the front end. Do you have any ETA on the version that will fix this problem? For a quick and dirty fix I'll configure a monit instance to make http requests to emby and restart it's docker if there is no answer to the request. Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 11, 2016 Share Posted April 11, 2016 yea that's the one. the beta should go stable in the next week or so. Link to comment Share on other sites More sharing options...
TrainAss 22 Posted April 22, 2016 Share Posted April 22, 2016 yea that's the one. the beta should go stable in the next week or so. Hey @@Luke, I'm having the exact same issue. Only started today when I upgraded to Server version 3.0.5931.0. I've been watching my Docker logs for the EmbyServer image and it's crashing and restarting like clockwork. What logs would you like to help maybe determine where the issue is? I have no problem running dev or beta builds. Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 22, 2016 Share Posted April 22, 2016 The ones mentioned here: http://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks. Link to comment Share on other sites More sharing options...
knoker 0 Posted April 22, 2016 Author Share Posted April 22, 2016 I had to reinstall my setup completely (my intel nuc gave up on me). Now i'm using https://hub.docker.com/r/binhex/arch-emby/ on a arch linux machine. So far no problem whatsoever. Link to comment Share on other sites More sharing options...
TrainAss 22 Posted April 22, 2016 Share Posted April 22, 2016 (edited) The ones mentioned here: http://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks. @@Luke sorry about that. Took me a little bit, but I found the docker logs for the container. I've attached the 3 latest Emby Server logs, as well as the logs from the Emby Server image for Docker. I hope these help. I looked at the log for Docker and noticed this one bit Running startup tasks Info, App, ServerId: 620ff152988d4f87810bd9cdfe5aced2 Info, App, Core startup complete Warn, Connect, Cannot update Emby Connect information without a WanApiAddress Warn, Connect, Cannot update Emby Connect information without a WanApiAddress Warn, Connect, Cannot update Emby Connect information without a WanApiAddress Error launching url: Cannot find the specified file Cannot find the specified file Info, SsdpHandler, MultiCast socket created Info, App, Loading live tv data from /config/data/livetv/timers Error, App, Error launching url: http://localhost:8096/web/wizardstart.html*** Error Report ***Version: 3.0.5931.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 3.16.0.0 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: /config Mono: 4.2.2 (Stable 4.2.2.30/996df3c Fri Feb 12 15:45:05 UTC 2016) Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe Cannot find the specified file System.ComponentModel.Win32Exception at System.Diagnostics.Process.Start_shell (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process) <0x40552af0 + 0x002ab> in <filename unknown>:0 at System.Diagnostics.Process.Start_common (System.Diagnostics.ProcessStartInfo startInfo, System.Diagnostics.Process process) <0x403b6890 + 0x000a3> in <filename unknown>:0 at System.Diagnostics.Process.Start () <0x403b6820 + 0x00047> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Start () at MediaBrowser.Server.Startup.Common.Browser.BrowserLauncher.OpenUrl (System.String url, ILogger logger) <0x405516a0 + 0x0015f> in <filename unknown>:0 Info, IDeviceDiscovery, Creating SSDP listener on 127.0.0.1 Info, IDeviceDiscovery, Creating SSDP listener on 172.17.0.3 Session terminated, killing shell... ...killed. Not sure if that has anything to do with it, or not. I'm running OMV 2.2 and everything is up to date. embydockerlog.log server-63596904123.txt server-63596904183.txt server-63596904243.txt Edited April 22, 2016 by TrainAss Link to comment Share on other sites More sharing options...
TrainAss 22 Posted April 24, 2016 Share Posted April 24, 2016 (edited) @@Luke I tried upgrading to the beta build of Emby server (Ver. 3.0.5943.0) and the issue is present here too.I wonder if the last (stable) build changed something that docker doesn't like... Update: So after trying to see what could have caused it, I upgraded my OMV server, broke it, rebuilt it (twice... Lesson learned, don't rebuild a server while on cold meds), and tried again; and Emby is now working. I don't know. At least I have my Emby back. Edited April 24, 2016 by TrainAss Link to comment Share on other sites More sharing options...
Luke 37095 Posted April 25, 2016 Share Posted April 25, 2016 Thanks. It's trying to open a url in a browser (startup wizard), and when it fails it's supposed to be handling the error and logging a message telling you to open the url manually. In this case though the mono runtime was just crashing. So I have removed even attempting to do that at all. I haven't pushed it to any builds yet but the fix is checked into latest sources. 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