Emby Docker container suddenly shut down during playback

[UsamaWaheed 8]

Hi all,

Looking for some guidance on a strange issue I’ve just run into.

While watching a movie tonight, my Emby server suddenly shut down without any warning. I didn’t issue any stop or restart command — either from the Unraid dashboard, the Emby web UI, or any connected client.

After checking, I found that the container had exited on its own. I right-clicked the container in Unraid and viewed the logs, which showed the following right after the shutdown:

 

s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d] executing container finish scripts... [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

It seems like the s6 supervisor triggered a clean shutdown, but I’m not sure why — there was no manual trigger or crash message from Emby itself.

I’m attaching:

• EmbyServer logs (both the previous and the current active log)

• Docker log output (captured just after the shutdown and restarting of the server)

If anyone can help interpret what might have caused this — whether it’s an Emby crash, Docker issue, or s6 overlay failure — I’d really appreciate it.
This is the first time I’ve seen the container terminate mid-playback like this.

Thanks in advance for any pointers!

P.S: Not sure how I can recreate the issue.

embyserver Current.txt embyserver-63897066580.txt Docker Logs - embylog.txt

Edited October 25, 2025 by UsamaWaheed
Fixed typo and added P.S

[rechigo 364]

I stumbled across this topic by accident, and it immediately caught my eye. I've ran into this exact same error + issue myself on a few occasions. iirc this has always been during playback for me as well, but maybe that's just by coincidence. 

 

My interpretation of the logs is that s6 itself has encountered an irrecoverable error (see s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d]), so it shuts down the services and exits the container.

 

What might cause that error I'm not sure... All I know is after it happened enough I realized I forgot to add a "restart: unless-stopped" to my compose... that was a simple bandaid fix for me. Now when it happens, the server restarts so quick I don't even notice.

Edited October 26, 2025 by rechigo

[Luke 42077]

Hi, please try removing these plugins:

2025-10-26 09:09:41.268 Info App: Loading playback_reporting, Version=2.1.0.7, Culture=neutral, PublicKeyToken=null from /config/plugins/playback_reporting.dll
2025-10-26 09:09:41.268 Info App: Loading statistics, Version=3.4.2.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Statistics.dll

Then restart the server and see if it happens again. Thanks.

[HappyZombiSlayr 10]

Hi all, I saw this too, looking up a similar issue I've been encountering.

 

I recently migrated my Emby Server to run containerized on a virtual machine running portainer. It runs fine, and all its data is stored on the volume I gave it. However, when I restart the virtual machine, on startup, Emby will fail. The output seems similar to what was referenced here regarding S6, and as this was so recent, I decided I'd reply.

 

Here's the log output:

	Library Folder: Movies, id: 4: path: smb://192.168.X.X/Movies
	Library:  TV shows, id: 5, CollectionType: tvshows, CollapseSingleItemFolders: False
	Configured paths: smb://192.168.X.X/TV Shows
	Library Folder: TV Shows, id: 6: path: smb://192.168.X.X/TV Shows
	Library:  DVDs, id: 7, CollectionType: movies, CollapseSingleItemFolders: False
	Configured paths: smb://192.168.X.X/DVDs/DVD Films
	Library Folder: DVD Films, id: 8: path: smb://192.168.X.X/DVDs/DVD Films
	Library:  Music, id: 9, CollectionType: music, CollapseSingleItemFolders: False
	Configured paths: smb://192.168.X.X/Music
	Library Folder: Music, id: 10: path: smb://192.168.X.X/Music
	Library:  Recordings, id: 2028, CollectionType: , CollapseSingleItemFolders: False
	Configured paths: smb://192.168.X.X/LiveTV Recordings
	Library Folder: LiveTV Recordings, id: 2029: path: smb://192.168.X.X/LiveTV Recordings
	Library:  Collections, id: 73533, CollectionType: boxsets, CollapseSingleItemFolders: False
	Configured paths: 
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LogLibrariesEntryPoint. Duration: 0.0023206 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0016536 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0004251 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0002401 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0002595 seconds
Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0024823 seconds
Info App: Starting entry point Emby.LiveTV.EntryPoint
Info LiveTV: Loading live tv data from /config/data/livetv/timers
Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0
Info LiveTV: Creating recording timer for df126ddb15cd64023d42d5cd73741999, Saturday Night Live. Timer will fire in 941.2593987366666 minutes
Info LiveTV: Creating recording timer for 726c72f09e434aade58853853be8b8c3, Saturday Night Live. Timer will fire in 1061.2593905666668 minutes
Info LiveTV: Creating recording timer for a582856be182cb2468e0ef585c42f2ce, Saturday Night Live. Timer will fire in 2321.25939019 minutes
Info LiveTV: Creating recording timer for 2f89b06b3483c85a39859d42aeba5510, Saturday Night Live. Timer will fire in 2381.2593899866665 minutes
Info LiveTV: Creating recording timer for 9258960561ee2860d6a523599eab6813, Saturday Night Live. Timer will fire in 2501.259389741667 minutes
Info LiveTV: Creating recording timer for ce8a400f63c864b660dfc9004ed1dbb7, Saturday Night Live. Timer will fire in 4001.2593895166665 minutes
Info LiveTV: Creating recording timer for 34db9dc8b2e224dc5dd581c470749f17, Saturday Night Live. Timer will fire in 4061.2593893266667 minutes
Info LiveTV: Creating recording timer for a243cbad2c4aea787e5494140bd87f20, Saturday Night Live. Timer will fire in 5710.25938909 minutes
Info LiveTV: Creating recording timer for 55fd92523dcb431762283ee02b245798, Saturday Night Live. Timer will fire in 6701.259388601667 minutes
Info LiveTV: Creating recording timer for e20ebd888058a1cc60778b1b248f2f6c, Saturday Night Live. Timer will fire in 6761.259388263334 minutes
Info LiveTV: Creating recording timer for 180acb1d1be7120f947848b92c57931b, Saturday Night Live. Timer will fire in 6821.259388078333 minutes
Info LiveTV: Creating recording timer for 201cf46d5858acda088560d90dcc9849, Saturday Night Live. Timer will fire in 6881.259387855 minutes
Info LiveTV: Creating recording timer for 15909734ea112f38681ebd62fc9927d7, Saturday Night Live. Timer will fire in 8321.259387533333 minutes
Info LiveTV: Creating recording timer for bd65828418a4321c01f89609ac64e62a, Saturday Night Live. Timer will fire in 9761.259387298333 minutes
Info LiveTV: Creating recording timer for 96d003bb005195cad226f0f0e365cf1c, The Bob Newhart Show. Timer will fire in 41.259386731666666 minutes
Info LiveTV: Creating recording timer for 561bbb284c583b2019ae4e7e3cc19a50, The Bob Newhart Show. Timer will fire in 1481.2593854133333 minutes
Info LiveTV: Creating recording timer for 9a0d83620c5bef1fbee40fc550f6cf69, The Bob Newhart Show. Timer will fire in 2921.2593844216667 minutes
Info LiveTV: Creating recording timer for 71430c804ccd4e76cc1973b28bdbd33f, The Bob Newhart Show. Timer will fire in 4361.259384173333 minutes
Info LiveTV: Creating recording timer for e50c9f69ba8237c2f21fbbc166052bf0, The Bob Newhart Show. Timer will fire in 8741.259383938333 minutes
Info LiveTV: Creating recording timer for 55eedbc3fea0a6787c06fc10336a96bc, Cheers. Timer will fire in 1361.2593837483332 minutes
Info LiveTV: Creating recording timer for 75df951065060319b21d19d483620732, Cheers. Timer will fire in 1391.2593835616667 minutes
Info LiveTV: Creating recording timer for 9de5b595138a5fff012439a5f9334021, Cheers. Timer will fire in 2801.259383368333 minutes
Info LiveTV: Creating recording timer for dc1195a6814e404a8a3adac2c18d0c16, Cheers. Timer will fire in 2831.259382978333 minutes
Info LiveTV: Creating recording timer for 4fb748f99191f555c4b32f1d2107b84b, Cheers. Timer will fire in 4241.25938263 minutes
Info LiveTV: Creating recording timer for cbf05aa11cba8bd5ecfa82bfe99eb8a0, Cheers. Timer will fire in 4271.259382445 minutes
Info LiveTV: Creating recording timer for da110f5bf79582aa161d3bfb1c1f60b3, Cheers. Timer will fire in 5681.259382266667 minutes
Info LiveTV: Creating recording timer for a7a25acb79c33302ee076452011d02f8, Cheers. Timer will fire in 5711.2593813016665 minutes
Info LiveTV: Creating recording timer for db739c17147fb0a93f9f1190df94b002, Cheers. Timer will fire in 5741.259380923333 minutes
Info LiveTV: Creating recording timer for 6875c30b48043d4a6c6682fd53f32a6e, Cheers. Timer will fire in 5771.259380718333 minutes
Info LiveTV: Creating recording timer for 21e32f7806afaca722938f361c6b6795, Cheers. Timer will fire in 8621.259380526666 minutes
Info LiveTV: Creating recording timer for f1b49264a12a3e04c1b4ea4f66d1fce2, Cheers. Timer will fire in 8651.259380346666 minutes
Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.046257 seconds
Info App: Starting entry point Emby.LiveTV.RecordingNotifier
Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0013171 seconds
Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0007163 seconds
Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint
Info Notifications: Registering event nofitier Activity Log
Info Notifications: Registering event nofitier Emby Server User Notifications
Info Notifications: Registering event factory CoreNotificationTypeFactory
Info Notifications: Registering event factory BackupNotificationTypeFactory
Info App: Init BeginReceive on 0.0.0.0
Info App: Init BeginReceive on 0.0.0.0
Info App: Init BeginReceive on 172.17.0.2
Info App: Init BeginReceive on 127.0.0.1
Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0235642 seconds
Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0010623 seconds
Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 9.39E-05 seconds
Info App: Starting entry point MovieDb.Security.PluginStartup
Info App: Entry point completed: MovieDb.Security.PluginStartup. Duration: 0.001016 seconds
Info App: Starting entry point MBBackup.ServerEntryPoint
Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 0.0001019 seconds
Info App: Starting entry point NfoMetadata.EntryPoint
Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.000137 seconds
Info App: Starting entry point Tvdb.EntryPoint
Info App: Entry point completed: Tvdb.EntryPoint. Duration: 5.34E-05 seconds
Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding
Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.000666 seconds
Info App: Starting entry point Emby.Security.PluginSecurityManager
Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 5.09E-05 seconds
Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint
Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0002726 seconds
Info App: All entry points have started
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

[Luke 42077]

Has this happened again?

[UsamaWaheed 8]

Sorry for the late reply. This hasn't happened again - so lets close this ticket for now. I will keep an eye out for this and reach out with a new forum topic if it happens again.

[UsamaWaheed 8]

You had suggested disabling the listed plugins, however I didn’t proceed with that step at the time because the crash did not occur again after your message, and the server remained stable.

However, the server unexpectedly crashed again today.

I’ve attached the latest logs for your review. Please let me know if this still points to one of the plugins as the likely cause.

If it is plugin-related, is there a way to diagnose this further (e.g. more detailed logging or isolation steps), or are issues with community-developed plugins generally difficult to troubleshoot beyond disabling them?

For context, I’m also sharing the link to the earlier forum post below.

embyserver-63901300060.txt hardware_detection-63901300063.txt embyserver (2).txt

[Luke 42077]

Hi @UsamaWaheedI have merged your topics so that we can keep relevant discussion together.

[Luke 42077]

Quote

Please let me know if this still points to one of the plugins as the likely cause.

If it is plugin-related, is there a way to diagnose this further (e.g. more detailed logging or isolation steps), or are issues with community-developed plugins generally difficult to troubleshoot beyond disabling them?

Hi, we don't know yet, however removing them is still the best way to begin diagnosing. At least for now until we know the cause, it is important to remove unknown variables from the equation.

[UsamaWaheed 8]

2 hours ago, Luke said:

Hi, we don't know yet, however removing them is still the best way to begin diagnosing. At least for now until we know the cause, it is important to remove unknown variables from the equation.

Noted. I have uninstalled both of these plugins and restarted the server. I will come back and report any crash if it happens (it's waiting game now I guess)

[UsamaWaheed 8]

Hi @Luke

Emby server restarted again today in the morning at 9:09 AM (thank god for pushover alerts).

 

I have attached logs, please check if you can find the cause. Kindly note as per my above post both the plugins have already been removed.

 

Thanks

hardware_detection-63902509792.txt embyserver-63902509780.txt embyserver-63902476799.txt embyserver (4).txt

[UsamaWaheed 8]

Hi @Lukeany luck with the above logs?

[Luke 42077]

I don’t really see anything obvious. Do you need the real-time monitor?

 You could try disabling that for each of your libraries. Then restart the server and see if it happens again.

[UsamaWaheed 8]

I add alot of things and want them to be automatically detected immediately rather than wait for scheduled scan library task.

 

Hmmm as an alternate I can use the 'Connect' feature in *arr stack to generate a 'on import' scan. Do you have any idea if that work with Emby? And are there caveats like the folder paths need to be same for both Emby and the *arrs?

[Luke 42077]

4 hours ago, UsamaWaheed said:

And are there caveats like the folder paths need to be same for both Emby and the *arrs?

Hi, I believe this is generally recommended, yes.

[UsamaWaheed 8]

If I change the path in Emby, it will rescan the library again. Any way to do it without rescanning?

[Luke 42077]

On 1/9/2026 at 11:27 PM, UsamaWaheed said:

If I change the path in Emby, it will rescan the library again. Any way to do it without rescanning?

Hi, not currently but this is planned for future updates. Thanks.