Upgrade/Restart Failure Version 3.0.5768.7

[Chuck 17]

After quite a few fresh reinstalls, I have Version 3.0.5768.7 running without issue.

 

However, after the initial upgrade run, neither the initial page or the configuration page would load in the web browser.  (it seems to me that I had a similar problem with the last version upgrade as well)

 

Also, when things seemed to be good, a server restart could cause the same problem.

 

I thought it might be due to a restart if either the library scan or chapter image extraction was running.  So, I tried a restart after fully stopping these scans before a restart.  But, same issue.

 

When I first attempted an uninstall in order to get back and running, the uninstall wizard hung.  I came to find out that fmpeg.exe was still running in the background, causing the full uninstall to fail.  At one point, I noticed that fmpeg.exe had two instances of fmpeg.exe running in the task manager (unfortunately, I wasn't paying close enough attention to remember which time this happened, or what steps I had taken to get to that point).

 

So, during an uninstall, I verified, or force stopped, fmpeg.exe after stopping the service (running Emby as a Windows service under an administrator account with Run As Service rights so that access to the NAS works correctly)

 

After this last clean install, the initial library scan completed without issue, the scheduled chapter image extraction ran with out issue overnight, and the server is running as expected.

 

If I had to guess, there may be a delay in stopping fmpeg.exe when the service stops if Emby is running some task in the background.  So, if I hit the restart service, there isn't time for fmpeg.exe to stop before the service start executes, and causing a process conflict that corrupts the server some how.  (only a wild guess)  Or, if Emby is running a background task, restarting the server while that invisible task is running causes a corruption. But, that doesn't explain why the initial server stop and executing the upgrade install would have caused the failure.  Unless, fmpeg.exe was still hung/running in the background after shutting down the service while running the upgrade install.

 

One thing is for sure, once this problem has been experienced, stopping the service and verifying that fmpeg.exe isn't running, there's no going back. Even with a server reboot it's hosed, but good.

[Luke 42080]

Thanks for the info. In these situations it's always good to accompany with log file(s) from the relevant time frames:

 

http://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Also I would suggest removing plugins and just using the core server, then adding them back later.

[Chuck 17]

Unfortunately, I don't have logs from this process.  They were deleted when trying to get back to a virgin state to get to a clean install.