s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening emby

[nascent 2]

I've been having a lot of issues trying to get emby/embyserver running in docker.

Any time I try to start the container I get "s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening emby" in the docker log.

The only fix seems to be completely deleting the entire emby folder.  It'll start up fine, but then subsequent starts will result in the same error.

I've even tried copying the contents of the emby folder from a working installation and it's resulted in the same error.  The only thing that works is completely deleting the emby config folder and then having to reconfigure all my libraries and premiere license etc.

the moment I next need to start the container the 's6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening emby' error reoccurs and I'm unable to progress.

I've had no issue with jellyfin, which I understand is based on emby, but I really wanted to get emby working especially as a premiere license holder.

[Abobader 3464]

Hello nascent,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42077]

HI there, can you please provide the complete terminal output? Thanks !

[darkassassin07 652]

Please also post your docker run command/compose file.

Edited January 22, 2025 by darkassassin07

[nascent 2]

which terminal output? it's a synology, the forum wont let me update my post to state that I'm using docker in a synology. it's gui not terminal
im not sure what a run/compose file is.  
i downloaded the emby/embyserver container

Edited January 22, 2025 by nascent

[DonMacaroni 54]

1 hour ago, nascent said:

which terminal output? it's a synology, the forum wont let me update my post to state that I'm using docker in a synology. it's gui not terminal
im not sure what a run/compose file is.  
i downloaded the emby/embyserver container

I run Emby natively, but Container Manager (Docker) on Synology does have terminal, it is accessible via "Action" menu.

 

[DonMacaroni 54]

I think, by terminal output, @Lukeis actually interested about container Log which you can export via "Export" button.
Hope this helps.

@nascentjust curious, why not use Emby Server package?
Only things I personally use Docker for, is to run things, which don't have native package for Synology.

Edited January 22, 2025 by DonMacaroni

[nascent 2]

1 hour ago, DonMacaroni said:

I think, by terminal output, @Lukeis actually interested about container Log which you can export via "Export" button.
Hope this helps.

Many thanks, I was looking in the wrong place for error logs (the filesystem and within the container ui), I didn't spot the log tab on the main docker window. Oops.

 

I was repeatedly seeing lines like:

Start container emby failed: {"message":"driver failed programming external connectivity on endpoint emby (aea78e5aeeaaeeebc5cbc345aea78e5aeeaaeeebc5cbc345 Bind for 0.0.0.0:8920 failed: port is already allocated"}.

I previously changed the port 8096 to avoid conflicts with jellyfin and the old native emby install.  but it seems i neglected to remap 8920.  i thought it as config corruption as the client was working fine on first launch, but that was a read herring.

many thanks for the support.

[DonMacaroni 54]

@nascentso you managed to solve it and it was simply container configuration error, on your side?

[Neminem 1518]

Look like you also might have jellyfin installed, right.

Since jellyfin uses the same port.

[Carlo 4560]

@nascent

Mind, if I ask you why you are running Emby Server in Docker vs running the native Synology version of Emby Server?

[DonMacaroni 54]

@CarloI actually came up with such scenario, where it would be beneficial, and I am considering it myself.

Reason in my case would be, easy migration beween systems as I personally plan to get rid of Synology and move to cusrom box and Unraid in near future. Also I may not stick with Unraid necessarily.

Edited February 12, 2025 by DonMacaroni

[Luke 42077]

@nascenthas your question been answered?

[nascent 2]

16 hours ago, Luke said:

@nascenthas your question been answered?

Yup thanks, I didn't realise I needed to mark a solution.

Done now, cheers.

[Carlo 4560]

On 2/12/2025 at 4:42 PM, DonMacaroni said:

@CarloI actually came up with such scenario, where it would be beneficial, and I am considering it myself.

Reason in my case would be, easy migration beween systems as I personally plan to get rid of Synology and move to cusrom box and Unraid in near future. Also I may not stick with Unraid necessarily.

This may or may not work. It's going to be more a function of the underlying storage system configuration.

For example, if you had 4 to 8 disks combined in some type of RAID with a share called Media holding all your content for Emby, your libraries mount points would likely use something like:
/Media/Movies
/Media/Shows
/Media/Music
/Media/Photos
/Media/Recordings
/Media/HomeVideo

With or without docker you can pickup/copy your system to another box, make a couple edits and have it work as usual if the new box has a similar storage setup and a share called Media.

If however, you move from a system using a 4 disk RAID to Unraid setup to use each disk individually or in sets of mirrors there will be multiple share points so all content will no longer be able to be found under Media. In this case it won't matter if docker was used or not since the content is now located in a different directory tree and ech library will need to be rescanned causing files to be removed and then added again which could cause issues for things like playlists. Media could also end up with different graphics and metadata as well if these were not stored previously with the media as well as bif and NFO files.

To me personally, the extra layers and complexity that docker generally adds isn't worth the tradeoff, but that's just me. Each use case is different and defined by the person running the box, which is what matters the most.