not sure whats going on here... but its like the third time i have closed them all, only to comeback hours later and see them multiplying again.
Jump to content
Posted 29 March 2020 - 09:38 PM
Just as an FYI emby wouldnt upgrade on its own to 188.8.131.52 today, because i had like 23 instances of emby server running..... I had to manually force close them all via task mgr... I now Have one of my program monitors disallowing more than one instance of embyserver.exe but thats a band-aid just letting you know. Non of the other versions could actually start because there was another running already (the working copy) but they all sat there as if they were running... maybe some check in the emby server app that doesnt allow multiple instances?
Posted 30 March 2020 - 05:57 PM
it looks like emby is trying to upgrade it's self and keeps failing, then retrying...
you need a better mechanism that doesmt keep old instances running if failed, or have it quit trying after a few fails.....
Log attached, they all look about the same...
Edited by pir8radio, 30 March 2020 - 05:58 PM.
Posted 30 March 2020 - 06:24 PM
Windows exit code 1 so emby knows its not exiting... why does it continue on... I also do not see anything obvious in the log as to why it didnt exit.
03/30/2020 05:01:18 PM LogName=Security SourceName=Microsoft Windows security auditing. EventCode=4689 EventType=0 Type=Information ComputerName=nam TaskCategory=Process Termination OpCode=Info RecordNumber=115701533 Keywords=Audit Success Message=A process has exited. Subject: Security ID: NAM\nam Account Name: nam Account Domain: NAM Logon ID: 0x8973C Process Information: Process ID: 0x9d88 Process Name: C:\Users\nam\AppData\Roaming\Emby-Server\system\EmbyServer.exe Exit Status: 0x1
Edited by pir8radio, 30 March 2020 - 06:27 PM.
Posted 30 March 2020 - 10:08 PM
I mean you can see in all of the logs: Info App: Automatically restarting the system because it is idle and a restart is required.
then the next log says: Info App: Update Revision 184.108.40.206 available. Updating...
it looks like emby is trying to update when idle after 15 mins then tries to restart emby, each time. I bet in the emby code, you reboot after idle for 15 mins?
That said, I can not remotely reboot my emby server either, it does the same thing... It reboots but leaves the original instance of the EXE running even though its not providing any services. So this issue seems related to not killing the old instance.
My splunk logs from the last 24 hours below: There have not been that many updates in the last 24 hours to cause all of the "required reboots"... The new version never gets installed because the old instance never got killed off... it tries again, now there are three instances running, idle 15mins later it tries again, four instances running, none of the other instances ever die unless force terminated.
Edited by pir8radio, 30 March 2020 - 10:20 PM.
0 members, 0 guests, 0 anonymous users