Grabbing debug logs… how exactly?
Stopped Synology PMS. Started docker container. Tried to resume the TV show I was watching…
Settings - Server - Troubleshooting ( lower left corner of Plex/web browser ) - Download Logs.
It will give you a ZIP file .
Please attach that ZIP here.
please turn DEBUG logging back on. (it’s on by default)
Settings - Server - General - SHOW ADVANCED –
Check the box for DEBUG.
Don’t check the box for VERBOSE.
SAVE that change.
Repeat the playback attempt .
All I got here was a few lines of errors. I couldn’t track where it was. (It’s that terse)
Plex Media Server Logs_2022-02-19_20-02-31.zip (352.7 KB)
Hopefully this is better
Much better , thanks.
It’s asking you to confirm the file exists. (it can’t read the file.
Might you have forgotten to give PlexMediaServer permission to read that media (applied to this folder, sub-folders and files option)?
Not sure what you’re asking. The Synology App has been working just fine. I’ve been trying to move to use the docker image. It seems the docker image is having problems doing the same.
What would you like me to do?
Based on the file you just tried to play with Docker…
Can that same file play with the normal Plex app?
(don’t forget to stop Docker before starting the native app)
Stop docker container, start Synology PMS, got to Plex web, play same video, continues where I left off.
I’m taking this as a good sign.
As for my docker run, you agree this looks correct:
Jupiter:cat /System/bin/dockerplex
#!/bin/bash
sudo docker run \
-d \
--name plex \
--network=host \
-e TZ="America/Los_Angeles" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=297536 \
-e PLEX_GID=297536 \
-h Jupiter \
-v /volume1/PlexMediaServer/AppData:"/config/Library/Application Support" \
-v /volume1/PlexMediaServer/AppData/tmp:/tmp \
-v /volume1/PlexMediaServer/AppData/tmp:/transcode \
-v /volume1:/volume1 \
-v /volume1/Media:/data \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass
Jupiter:
OK, I’m missing something that you need here.
- The metadata is right.
- It doesn’t seem to be mapping the media files in correctly.
- Would you mind removing
-v /volume1/Media:/data \from your container configuration and then recreating the container? - The line is unnecessary because
/volume1:/volume1is what you need - Your PMS doesn’t look for media under
/data.
After recreating the container, start the container.
We’ll next go into the container
sudo docker exec -it plex /bin/bash
and go look for your media files.
They should be accessible in the same places they are when on the host app.
I presume you have your media under /volume1/Media ?
If true, from within the container.
cd /volume1/Media
ls -la
You should see your identical directory structure.
Continue down into sub folders and getting listings. Everything, especially the file you tried to play, should be there.
OK, the -v /volume1:/volume1 kinda threw me. Seems overly permissive. Anyway…
- Stopped Synology PMS app
- docker container rm plex
- Removed -v /volume1/Media:/data \ from my script
- Recreated docker container
- Tried playing video - Playback Error
Tried docker exec -it plex bash and under /volume1 I see Media. IOW ls /volume1/Media works:
root@Jupiter:/# ls -al /volume1/Media
total 12
drwxr-xr-x 1 1000 1000 106 Feb 17 19:20 .
drwxr-xr-x 1 root root 1132 Feb 5 23:05 ..
-rwxr-xr-x 1 1000 1000 8196 Oct 26 14:35 .DS_Store
dr-xr-xr-x 1 root root 18 Dec 9 11:35 .Trash-0
drwxr-xr-x 1 1000 1000 34 Aug 8 2021 .Trash-1000
drwxrwxrwx 1 root root 52 Jan 18 16:50 @eaDir
drwxr-xr-x 1 1000 1000 452 Sep 18 12:07 Music
drwxr-sr-x 1 1000 1000 670 Feb 12 11:45 Pictures
drwxr-xr-x 1 1000 1000 254 Sep 30 15:52 Videos
root@Jupiter:/#
OK, I see what you’re doing now
Sure, you can remove the blanket /volume1:/volume declaration given you have everything in /volume1/Media.
In its place -v /volume1/Media:/volume1/Media and presto. The files will appear where they’re expected with the permissiveness removed.
Whatever this is, it’s going to be stupid when we find it.
Stupid is as stupid does…
Current docker run script:
#!/bin/bash
sudo docker run \
-d \
--name plex \
--network=host \
-e TZ="America/Los_Angeles" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=297536 \
-e PLEX_GID=297536 \
-h Jupiter \
-v /volume1/PlexMediaServer/AppData:"/config/Library/Application Support" \
-v /volume1/PlexMediaServer/AppData/tmp:/tmp \
-v /volume1/PlexMediaServer/AppData/tmp:/transcode \
-v /volume1/Media:/volume1/Media \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass
Stopped and removed container. Ran the above script. Same problem - Playback Error.
Into the Docker container I see:
root@Jupiter:/# ls -l config/Library/Application\ Support/Plex\ Media\ Server/
total 8
drwx------ 1 plex plex 408 Feb 19 20:47 Cache
drwx------ 1 plex plex 212 Jan 31 07:55 Codecs
drwx------ 1 plex plex 2016 Feb 19 18:06 'Crash Reports'
drwx------ 1 plex plex 0 Jul 23 2020 Diagnostics
drwx------ 1 plex plex 3136 Feb 19 20:47 Logs
drwx------ 1 plex plex 18 Jul 23 2020 Media
drwx------ 1 plex plex 54 Jul 23 2020 Metadata
drwx------ 1 plex plex 100 Jul 22 2020 'Plug-in Support'
drwx------ 1 plex plex 30 Jul 22 2020 Plug-ins
-rwx------ 1 plex plex 1874 Feb 19 20:47 Preferences.xml
-rwx------ 1 plex plex 3 Feb 19 20:47 plexmediaserver.pid
root@Jupiter:/#
Does that say anything here?
WHOA… That is not right. Check the container’s /etc/passwd
Give me a few please. I’m going to spin up a fresh container on the Lab Syno.
Resolved… working on it now
Here’s the /etc/passwd from inside the container:
root@Jupiter:/# cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/var/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
uuidd:x:101:101::/run/uuidd:/usr/sbin/nologin
plex:x:297536:297536::/config:/bin/false
root@Jupiter:/#
That must be new to the container. I apologize. I did not know they’d changed it.
It appears they now use the default name plex instead of the name the host uses.
I am continuing to test. DS716+ DSM 7
Yes I’m at DSM 7.0.1-42218
This is informative but not helpful.
I used your definition, I used /volume1:/volume because the nas only has test files on it.
It plays fine.
Are you 100% certain you hit the Apply to this folder, subfolders and files when you granted permission to PlexMediaServer in /volume1/Media ?
Are you also certain the files are owned by your syno username and have ACLs?
(I saw a weird case a long time ago where the files were in Linux mode – aka chmod files and nothing worked until the ACLs were restored.
Don’t think I’ve ever said /volume1:/volume anywhere.
I didn’t grant permission to PlexMediaServer with some sort of Apply to this folder, subfolders, and files that I recall. Maybe something in installing PMS once the big DSM 6x → DSM 7x happened but that was a while ago and I’m more thinking about chown -R from the cmdline. In any event, the Synology PMS app has been doing just fine. I’m just trying to transition over to a docker image from a fully functional PMS environment.
Don’t know anything about syno username and ACLs. What I do know is it has been working fine for the Synology PMS app for months.
