Plex Media Scanner on Synology DS218+

Plex Media Server NAS & Devices
1

Hey, I’m having some trouble using the Plex Media Scanner on my Synology NAS.
I tried using it like this:
First I did this: (logged in as root)

export LD_LIBRARY_PATH=/volume1/Plex/Library/“Application Support”/“Plex Media Server”/

And then:

/volume1/Plex/Library/“Application Support”/“Plex Media Scanner” --scan

(I followed this guide when trying this)

This didn’t work and gave me this error:

-ash: /volume1/Plex/Library/Application Support/Plex Media Scanner: No such file or directory

Is someone able to clarify what I have to do?

Thanks

2
  1. PMS is username sensitive. PMS runs as user plex on Synology, not as root. All Plex executables must also run as plex to avoid permission problems.
  2. Executables and LD libraries (scanner) are not stored where you think they are. They’re in the appstore under the control of Package Center. /var/packages/Plex Media Server/target

PS: We have a Synology forum (tag). I’ve taken the liberty of moving this thread there where it’s easier for all to see.

3

What’s the password of the Plex user? According to this it’s random and I should be able to change it. Is that correct?

Thanks

4

Proper admin (root) access to the Syno doesn’t need a password assigned for user Plex. I create a 64 character uuid-gen password for each system as PMS installs

Mind my asking how comfortable you are at the Linux command line?

5

Eh, I’m not good at it I’m just trying things. The only thing I want to happen is that my library refreshes after my bash script has executed since auto refresh when files have been added/removed doesn’t seem to work.
Anyway, when I try to use it it gives me this:

/var/packages/Plex Media Server/target/Plex Media Scanner: /lib/libstdc++.so.6: no version information available (required by /var/packages/Plex Media Server/target/libgnsdk_dsp.so.3.07.7)
/var/packages/Plex Media Server/target/Plex Media Scanner: /lib/libstdc++.so.6: no version information available (required by /var/packages/Plex Media Server/target/libgnsdk_dsp.so.3.07.7)
/var/packages/Plex Media Server/target/Plex Media Scanner: /lib/libstdc++.so.6: no version information available (required by /var/packages/Plex Media Server/target/libgnsdk_fp.so.3.07.7)
/var/packages/Plex Media Server/target/Plex Media Scanner: /lib/libstdc++.so.6: no version information available (required by /var/packages/Plex Media Server/target/libgnsdk_fp.so.3.07.7)

Thanks

6

Those are normal.

Synology strips the version and symbol table from their binaries to save memory space.

Respectfully,
If you’re writing a bash script, where are you writing it? Are you using the Control Panel - Task Scheduler feature?

7

I wrote it in nano and saved it somewhere. Task scheduler just executes the file. But I tried the command above just in the plex user, not in the script.

8

You can write the entire command sequence (script) and put it in the task. There is no need to add the extra indirection of a file somewhere else for you to maintain. This way, when you want to make changes, it’s readily and immediately available and uses DSM’s logging of the output

9

I still get logs in my e-mail. But anyway, when I execute the command it just says the binary stuff and not anything else. I tried --list and it said nothing

10

Execute 1 command as user plex using /bin/sh as the shell. semicolons between quotes, to allow multiple commands on line line, is allowed

su plex -s /bin/sh -c "shell-script-or-command-line-here"
``
11

When I’m sudoing as ‘plex’ the var/packages/“Plex Media Server” location cannot be found because it starts looking from /volume1/.
Any workaround on this?

12

Be specific in how you reference it.

"/var/packages/Plex Media Server/target" is a location-independent location which DSM provides (a bind mount) and don’t forget to quote the entire path or escape the spaces.

"/var/packages/Plex Media Server/target"
equivalent to
/var/packages/Plex\ Media\ Server/target

Please do avail yourself of bash scripting tutorials?

13

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