emby server crashing and restart solution

[noybman 7]

Necro thread or not? OP never followed up and it's been more than a few years.

I'm having this issue presently and it seems "maybe" I should uninstall and reinstall because it started after the Emby executable got foobar'd. I recently updated my media pc from a much older i5-4th to an i9-14th, and as annoying as it is, the Intel 14th is a power hungry hot running PO_. Memory manufacturers of DDR5 are meh, and the MOBO company has released 12 BIOS updates in 5 months, 9 of which are "stability" related. And to top it all off, I figured "why not get the latest Samsung M.2?" I went Samsung 990 Pro 2TB Gen 4) and they too have hardware issues where the drive corrupts itself to the point it is not salvageable (allegedly). Anyways...

 

I reinstalled Emby on top of the existing install, and all the users work, the mounts work, the plugins work, all looks good... for less than 24 hours. Suddenly the server is no longer responsive on the web port (even locally), and if I "restart" it from the taskbar icon (I'm on Win 11 Pro), it wont work still. But if I exit it, then manually releaunch it, it works again.... for about 24 hours.

The last chunk of log data says:

2024-05-01 01:11:59.231 Info Server: http/1.1 POST https://‌‍‍WWW.WEBSERVER.COM‌/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=123456789-SOME-ID-123456789&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=‌123456789-SOME-ID-123456789‌&reqformat=json. UserAgent: Emby/2 CFNetwork/1494.0.7 Darwin/23.4.0
2024-05-01 01:11:59.231 Info SessionManager: Adding playSession 123456789-SOME-ID-123456789 to session 123456789-SOME-ID-123456789
2024-05-01 01:11:59.232 Info Server: http/1.1 Response 204 to ‌‍‍111.17.111.111‌. Time: 1ms. POST https://‌‍‍WWW.WEBSERVER.COM‌/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=123456789-SOME-ID-123456789&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=‌123456789-SOME-ID-123456789‌&reqformat=json
2024-05-01 01:11:59.233 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : 123456789-SOME-ID-123456789|123456789-SOME-ID-123456789|2304099|DirectStream
2024-05-01 01:11:59.255 Info App: Sqlite: 284 - automatic index on LastWatchedEpisodes(SeriesPresentationUniqueKey)
2024-05-01 01:11:59.424 Info PlaybackReporting - EventMonitorEntryPoint: Adding PlaybackInfo to playback_trackers : 123456789-SOME-ID-123456789|123456789-SOME-ID-123456789|2304099|DirectStream
2024-05-01 01:11:59.424 Info PlaybackReporting - EventMonitorEntryPoint: Saving PlaybackInfo to DB
2024-05-01 01:12:59.251 Info SessionManager: Session 123456789-SOME-ID-123456789 has gone idle while playing
2024-05-01 01:12:59.251 Info SessionManager: Playback stopped reported by app Emby for Apple TV 1.8.8 (2) on Apple TV playing THE THING. Stopped at 6574000 ms
2024-05-01 01:12:59.252 Info SessionManager: Removing playSession 123456789-SOME-ID-123456789 from session 123456789-SOME-ID-123456789
2024-05-01 01:12:59.254 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStop : Entered
2024-05-01 01:12:59.254 Info PlaybackReporting - EventMonitorEntryPoint: Saving final duration for Item : 123456789-SOME-ID-123456789|123456789-SOME-ID-123456789|2304099|DirectStream
2024-05-01 01:12:59.260 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : 123456789-SOME-ID-123456789|123456789-SOME-ID-123456789|2304099|DirectStream

I realize I neutered that log file, but honestly, all thats there before it, is while it's working, and its playback. When I ask the emby server to "restart" by means of the taskbar icon, it doesn't do anything. Logs dont get updated, nothing happens. It appears the computer continues to run properly. Just curious if there is some advanced debugger I can run?

[Luke 37253]

hi @noybmanplease attach the complete emby server log file from when the problem occurred. Thanks.

[noybman 7]

I'm reluctant to attach the log because its full of nothing useful. (I promise).

I've had instances where the server is idle for many many hours, and then it crashes. I cannot restart it as noted above, I have to exit the app and relaunch it. When I review the log activty, I see that there a long period of inactivity, then.... nothing - the new log file for the startup (after I've killed it and relaunched).

I'm beginning to belive this is more OS/hardware related because I am still struggling with hardware instability too. The events are NOT coincident (I would almost wish they were)... but I can say for certain there is nothing in the log file of interest.

If it would even log the attempted restarts via the emby taskbar icon request to restart, I would upload the log. But again, nothing gets written. None of these issues surfaced until I upgraded the hardware.

[Luke 37253]

Ok, first place I would start is to remove any plugins you installed beyond the ones that are included with the server.