Transcoder stops due to an error - I tried everything

Plex Media Server Desktops & Laptops
1

Server Version#: 1.19.3.2843
Player Version#:

Hello all,
I cannot transcode anything since “the transcoder exited due to an error”.

I am running PMS in a container with docker on openmediavault.

May 24, 2020 08:21:13.581 [0x7faa9bfff700] Erreur — [Transcoder] Unrecognized option 'crf:0'.
May 24, 2020 08:21:13.581 [0x7faa7cff9700] Erreur — [Transcoder] Error splitting the argument list: Option not found

The config folder for plex is on /dev/disk/by-label/systeme, here is the fstab :

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=37f6d35d-6164-4029-920e-5282e03ccdf4 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=793A-1D09  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p3 during installation
UUID=bd91d3af-3649-4e45-8627-4bf86ba10538 none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-id/ata-ST4000VN008-2DR166_ZDH7N7FR-part1           /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH7N7FR-part1       ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jq$
/dev/disk/by-id/ata-ST4000VN008-2DR166_ZDH7NTGR-part1           /srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH7NTGR-part1       ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jq$
/dev/disk/by-label/systeme              /srv/dev-disk-by-label-systeme  ext4    defaults,nofail,user_xattr,exec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/dev/disk/by-id/usb-ST2000LM_003_HN-M201RAD_3321A947801424-0:0          /srv/dev-disk-by-id-usb-ST2000LM_003_HN-M201RAD_3321A947801424-0-0      ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota$
# <<< [openmediavault]

And all codecs are in the appropriate folder :

-rwxrwxrwx+ 1 Matthieu users  265440 mai   23 19:17 libaac_encoder.so
-rwxrwxrwx+ 1 Matthieu users  175024 mai   24 09:29 libac3_decoder.so
-rwxrwxrwx+ 1 Matthieu users 1948720 mai   13 16:54 libh264_decoder.so
-rwxrwxrwx+ 1 Matthieu users 1559600 mai   13 16:54 libhevc_decoder.so
-rwxrwxrwx+ 1 Matthieu users 1888600 mai   22 14:24 liblibx264_encoder.so
-rwxrwxrwx+ 1 Matthieu users  187328 mai   23 19:17 libmp3_decoder.so
-rwxrwxrwx+ 1 Matthieu users  860848 mai   13 16:55 libmpeg4_decoder.so

What can I do more ? Thank you very much

2

Just a thought, but I feel like the codec files should be owned by Plex. What do the permissions on other Plex files look like? For me all Plex files are owned by Plex, I just put my own user in the Plex group.

3

So I should create an user “plex” in openmediavault then create the plex server with its ID ?

4

This thread should really be tagged server-docker.

As for the ownership of the codecs (and everything else located in the Library tree), those files are owned by the user:group that the docker container runs as.

On systems running Plex in a docker it is not at all unusual for there to be no user or group named plex.

I am curious as to why the codes have the exec bit set. Mine don’t and they run fine without it.

One thing that is harmless to try is to delete the codecs and let Plex redownload them the first time they are needed.

5

No. But knowing more about how the docker was setup might be helpful.

6

Here are the docker setup :
image from plexinc/pms-docker

PLEX_UID	1002
PLEX_GID	1000
PATH	/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
TERM	xterm
LANG	C.UTF-8
LC_ALL	C.UTF-8
CHANGE_CONFIG_DIR_OWNERSHIP	true
HOME	/config

/srv/dev-disk-by-label-systeme/Config/plex	/config
/srv/dev-disk-by-label-systeme/Config/plex-transcode	/transcode
/srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH7N7FR-part1/Films	/Films
/srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH7N7FR-part1/Series	/Series
/srv/dev-disk-by-id-ata-ST4000VN008-2DR166_ZDH7NTGR-part1/Formations

host mode

And the ids come from :

root@mediacenter:/# id plex
uid=1002(plex) gid=100(users) groupes=100(users),1000(Plex)

Do you see anything uncommon ?
I reinstalled everything and now all folders and files under /config/plex owns to plex/Plex

7

And the exec is manually modified by me since it was “no-exec” before and I saw somewhere in this forum that we should modify to “exec” to expect to resolve the issue

8

So you do have a user named plex and a group named Plex. I wouldn’t mix case in user or group names, but that’s just style and probably not a problem.

I would keep an eye on your fstab because if you make manual edits there they can get undone by OMV. There is a proper way to do this and the OMV forum has links to the method.

So, what do the ownerships and permissions of the codecs look like now?

What specific errors is Plex now throwing, assuming transcoding is still broken?

9

So now everything look like this :

-rw-r--r-- 1 plex Plex  265440 mai   24 16:38 libaac_encoder.so
-rw-r--r-- 1 plex Plex  175024 mai   24 16:38 libac3_decoder.so
-rw-r--r-- 1 plex Plex 1948720 mai   24 16:44 libh264_decoder.so
-rw-r--r-- 1 plex Plex 1559600 mai   24 16:38 libhevc_decoder.so
-rw-r--r-- 1 plex Plex 1888600 mai   24 16:38 liblibx264_encoder.so
-rw-r--r-- 1 plex Plex  187328 mai   25 13:51 libmp3_decoder.so
-rw-r--r-- 1 plex Plex  860848 mai   25 13:24 libmpeg4_decoder.so

And the error is still :

May 25, 2020 11:54:17.945 [0x7fa9fe7fc700] Erreur — [Transcoder] Unrecognized option 'crf:0'.
May 25, 2020 11:54:17.945 [0x7faa05ffb700] Erreur — [Transcoder] Error splitting the argument list: Option not found
May 25, 2020 11:54:18.451 [0x7fa9eeffd700] Attention — Got a request to stop a transcode session without a session GUID (or with an invalid one).

I set back the fstab to noexec then

10

I am out of ideas, but you will have to remove noexec from that drive eventually. Best suggestion I have for you is to delete the container and build it again.

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.