bylj 1 Posted January 18, 2020 Share Posted January 18, 2020 (edited) Hi, I'm running Emby in a LXC container on Proxmox (Debian based). At some point the emby servers crashes, seems to be an app error: downloading news when Emby tried to check for updates for the plugins. I hope somebody could help me point me into the right direction. Full log attached. log.txt Edited January 18, 2020 by bylj Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted January 18, 2020 Share Posted January 18, 2020 If you're not using DLNA, disable it. Disable your plugins and see if the issue persists. Link to comment Share on other sites More sharing options...
Luke 37009 Posted January 19, 2020 Share Posted January 19, 2020 Hi, did it crash during the time of this log file? Because judjing from the bottom of the log it looks like it may have gotten a signal from the OS or container to shutdown. In other words, the shutdown at the bottom looks more like a graceful shutdown. It's not the typical abrupt stop that you would normally see with a crash. After you start the server how long does it take for this to happen? Does it coincide with any particular event that occurs on the machine? Link to comment Share on other sites More sharing options...
bylj 1 Posted January 19, 2020 Author Share Posted January 19, 2020 (edited) Hi, The server does get the signal to shutdown from me, because emby is unreachble at that time. After the last error Emby isn't responding. The server runs for about 24-25 hours before it happens. The container only runs Emby, proxmox does run an other container, but this should not effect the container which runs Emby. Edited January 19, 2020 by bylj Link to comment Share on other sites More sharing options...
bylj 1 Posted January 19, 2020 Author Share Posted January 19, 2020 It happened again today It happens after Emby wants to check for updates, but it fails. At that point Emby will be unavailable. Full log attachted log_19_1.txt Link to comment Share on other sites More sharing options...
Solution bylj 1 Posted January 21, 2020 Author Solution Share Posted January 21, 2020 So research said with same error in logs that network might be blocking off things. Turned everything upside down but couldn't find anything. Finally found out that the debug stated that the NetworkManager had changed the networkenvironment or a similar like that after 24 hours. Somehow a bit weird since I made the IP of this container static in my DHCP settings. So I setup the static ip adress in the Proxmox environment and now it's running still after 24 hours and the plugin updates went ok! For now I do think this was my solution. Will keep an eye on it. 1 Link to comment Share on other sites More sharing options...
Luke 37009 Posted January 21, 2020 Share Posted January 21, 2020 Thanks for the feedback ! 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