MetaData not refreshing - Ubuntu 16.04.02 / PMS 1.7.2.3878

General Discussions
1

Hi Guys,

I have been looking into the for the past few days, its happening to both movie and tv content. First off I thought it might be IPv6 related as I now have native IPv6, so I disabled that, no go. I tried upgrading, am now running plexmediaserver_1.7.2.3878-8088811b8_amd64.deb. Googling and looking at the forums didn’t seem to help either. I have tried:

  • Using my ISP’s DNS Servers as I use OpenDNS for content Filtering
  • Disabling IPv6
  • Removing user installed Plugins

I’m running:

  • Ubuntu 16.04.2 LTS
  • PMS Version 1.7.2.3878

TIA,

Bill

2

Did you relocate (symlink) your PMS Library or do you have a script which runs?

Please sudo chown -R plex:plex /var/lib/plexmediaserver/Library

Jun 01, 2017 13:27:44.417 [0x7f5117bfb700] ERROR - Error creating directory /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost/2: boost::filesystem::create_directories: File exists: "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Media/localhost"

Also,
Please optimize your database.

Jun 01, 2017 13:19:34.734 [0x7f5b483fe700] WARN - SLOW QUERY: It took 220.000000 ms to retrieve 97 items.
3

Ah, its a symlink, I didn’t know that. I didn’t move it, but its on a Synology NAS.

The NAS had a disk failure a few weeks ago that required the OS to be re-installed, my guess is the permissions must have been reset during that process.

Thanks for your help. Which log did you see that info in?

4

I saw that in your Plex Media server.log.x files.

If you prefer, and is better, create a service override in /etc/systemd/system/plexmediaserver.serivice.d/override.conf.

In it, place

#
#
[Service]
Environment="PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/path/to/new/Library directory spaces allowed/Application Support"

systemctl daemon-reload
systemctl restart plexmediaserver

Now, you’ll never have to worry about it. Plex will never look for the symlink nor will it ever go to /var again

5

Cool, I’ll do that. Thanks.

6

file was in a slightly different place on my system /etc/systemd/system/plexmediaserver.service, I don’t have the plexmediaserver.serivice.d folder.

7

Create the directory.

I should have clarified. The /etc/systemd/system/plexmediaserver.service file is because of Ubuntu’s flip-flopping on how they want things. One moment they want it in /lib/system/system/plexmediaserver.service and the next moment in /etc. The override file survives uninstall as well as updates. I overwrite the /etc and /lib plexmediaserver.service files with each update.

8

Could I just remove the Symlink, create a folder called localhost and move the data there?

9

It’s Linux. Other than the symlink, you can do what you want. You can even do a --bind mount but I advise against it. In a pinch, I would go with bind over symlinks any day but the reason the dev and I worked to put the support in for overrides was to guarantee flexibility and portability.

There’s a lot override.conf can do for you. It can change user or group, default file creation mask, and anything else SystemD overrides support.
Any of Plex’s environment variables, which used to be in /etc/defaults/plexmediaserver are now fully supported here.

The decision point is this:

cat /proc/1/comm . If it returns systemd, the i advise using the override as it’s the way Linux is headed. If it returns init, then go with the bind mount (man mount for details or let me know). It does look like this in /etc/fstab. /home/plexdir is where I completely relocated everything under /var/lib/plexmediaserver.

# PMS bind mount
#/home/plexdir    /var/lib/plexmediaserver               none bind 0 0

I have since created /etc/systemd/system/plexmediaserver.service.d/override.conf containing

[chuck@lizum ~.102]$ cat /etc/systemd/system/plexmediaserver.service.d/override.conf 
#
#
[Service]
Environment="PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/home/plexdir/Library/Application Support"
#
#
[chuck@lizum ~.103]$

Both do the same job. The latter (override) doesn’t occupy a mount table slot ( a consideration on some Linux distros)

10

Awesome, thanks for the info.