Emby recording failed on 4.2.1.0

[sfatula 207]

It failed and got restarted. (Big Brother)

 

Please look near timestamp 19.18.39.482 for one issue, something about a lock. That's in one log file (embyserver.txt). The root cause seems to be it restarted, that's the other log file. I have no idea why, no one was using emby at all, yet, server restarted.

 

Why would it have restarted??? Should it restart while it is recording?

 

The good news is it restarted the recording, so, I just have 2 .ts files now. I had to run the post processing script for the first .ts file since Emby restarted and didn't spawn that off.

embyserver.txt

embyserver-63702357517.txt

Edited August 26, 2019 by sfatula

[sfatula 207]

No answer?

[Luke 42086]

It's hard to say. The server restarted but i'm not sure why.  The only restart reason I can think of that might not show up in the server log would be if it received a shutdown command from the OS. We can add more logging for that so that we can identify it though.

[sfatula 207]

I doubt ubuntu decided to shut it down. Extra logging might be a good idea.

[sfatula 207]

I didn't give up on your idea, in fact I found out the why. Letsencrypt and my post update script restarted emby, which is needed to put the new SSL cert info place. This has worked for over a year. However, it's a bad idea since that can run at who knows what time, including, during a recording. And it did.

 

So, I just weekly restart emby in the middle of the night when I would not record now.

Edited August 29, 2019 by sfatula

[Luke 42086]

Right I didn't mean that the OS decided to shut it down, I just meant the command came from the OS.