FGaray Posted August 2 Share Posted August 2 Need assistance troubleshooting an issue. My emby server crashes and fails to restart post auto update. The only way to fix it is for me to download the update an apply it manually. The logs are attched. embyserver-63794983518.txt embyserver-63795018484.txt Link to comment Share on other sites More sharing options...
FGaray Posted August 2 Author Share Posted August 2 Further, I have it configured as a service to auto restart when I reboot the server. Now the service won't restart. Link to comment Share on other sites More sharing options...
ebr Posted August 2 Share Posted August 2 Hi. The server does not appear to be crashing. It is just trying to update. My guess would be there is some sort of permissions issue. Is there an update log? Link to comment Share on other sites More sharing options...
FGaray Posted August 2 Author Share Posted August 2 Can you kindly point me to the location for the update log file? Link to comment Share on other sites More sharing options...
Luke Posted August 2 Share Posted August 2 By service do you mean you've configured a windows background service? Link to comment Share on other sites More sharing options...
FGaray Posted August 2 Author Share Posted August 2 Running the emby account as a service: https://support.emby.media/support/solutions/articles/44001159984-running-emby-server-as-a-windows-service Link to comment Share on other sites More sharing options...
Luke Posted August 2 Share Posted August 2 You haven't configured the emby server command line arguments properly. It should be -service, not -server Link to comment Share on other sites More sharing options...
FGaray Posted August 2 Author Share Posted August 2 1 hour ago, Luke said: on configuring the Emby account as a service? Where can I find the upgrade logs? Link to comment Share on other sites More sharing options...
Luke Posted August 3 Share Posted August 3 If it's the automatic update then there isn't really much of an upgrade log. Anything about the upgrade is just printed to the server log before it takes place. The most likely explanation is that you're doing something that we don't test ourselves and is not officially supported, which is auto-updating via the windows background service. If you make the command line change that I mentioned above then the server won't even attempt it. 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