Ubuntu 18.04 fresh Install i3 NUC not loading any meta-data locally or via NAS

Server Version#: Intel i3 Nuc / Ubuntu 18.04
Player Version#: any player (Samsung TV / Phone / browser to PMS
Plex Media Server Logs_2019-11-10_09-38-33.zip (2.1 MB)

Hi all

I have had plex running on a Synology nas with lots of media its getting a bit old, cant trans code decided to upgrade to a new NUC.

I did a fresh install on Ubuntu 18.04 and followed the steps on installing Plex via deb (did it first with snap store and removed) with no issues. I mounted my NFS shares from NAS and plex can see them all ok. I added one small folder to plex to test, saw the files and started populating the library looking good…

But then i realised that the meta data wasn’t being pulled… I refreshed all meta data and waited but still no covers etc…

I thought it was permissions on my mount, so i dragged a tv show locally on the nucs SSD and added, still didn’t pull the metadata.

Maybe a permissions issue ? I cant see anything in the logs myself but I’m not familiar with them. As a note I’m not great with linux I’m a tinkerer but love to learn.

Any suggestions ?

have look at Metadata and artwork not loading for Movies, sounds a bit like it.

Interesting so it might not be me ?fingers crossed haha

I might try adding a few movies and see if i get the same results locally / NAS

Or have a look in the agent’s log file :wink:

Yep looks like I have similar issues to you

com.plexapp.agents.thetvdb.log

2019-11-10 09:31:23,047 (7fbd667fc700) :  DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/episodes/4246771?lang=en'
2019-11-10 09:31:23,051 (7fbd67fff700) :  INFO (__init__:1078) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-10 09:31:23,054 (7fbd677fe700) :  INFO (__init__:1084) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-10 09:31:23,065 (7fbd657fa700) :  INFO (__init__:1027) - Season Extra XML is empty - therefore, no episode XML

Do you have your own certificate in use anywhere?

I have another plex server still running on my Synology NAS (same network)
was going to leave up whilst I migrated.

Are you using the Synology for the NFS server with the NUC being the heavy-lifter ?

If so, and you wish to save some time with metadata matching, you can transport from the Syno to the NUC with a little bit of pathname magic (emulate syno directory structure in the NFS mounts).

Hi

Yep im using the nuc to do the the transcodes and run PMS i want to take some processing away from the nas as its a older model and just it as a file storage for library.
I did notice that plex runs allot faster from the NUC than the NAS so wouldnt mind the speed increase

If you don’t mind a little keyboard work, it’s not a big deal.

  • A few hand-made directories,
  • A temp NFS mount
  • Tar & extract across the NFS mount
  • recursive chown on the NUC.
  • Change the friendly name on the NUC side (with syno shutdown) to avoid conflicts because this is a cloning operation)

I just added 3 movies locally and from the NAS meta data worked as expected no issues to maybe its a TVdb issue ?

Thanks for the advice, does sound like a bit of work.

If I can get it working as is would be preferred, I’m so close just need to sort out the meta data to tv shows …movies all good now

I can help with the commands if you’re not 100% comfortable.

Setup: NUC and Syno PMS shutdown
Prereq: nfs-common package on Ubuntu systems.

* sudo sh
* mount  ip.addr.of.syno:/volume1/Plex /mnt
* cd /var/lib/plexmediaserver
* mkdir NewLibrary
* cd NewLibrary
* (cd /mnt ; tar cf - ./Library) | tar xf -
* chown -R plex:plex .
* cd ..
* mv Library Library.keep
* mv NewLibrary Library

# At this point,  we have the Syno metadata in the "NewLibrary" subdirectory with UID/GID already set for this host.  Now to make directories to emulate the mount points.


mkdir /volume1
mkdir /volume1/movies    ---   Make these as you need to match the Syno

chown -R your_linux_username /volume1
chmod -R 755 /volume1


# Now create the NFS mounts in /etc/fstab to mount up before PMS starts
# Since user **plex** exists on both, we'll take advantage of that.


#Something of the form (repeating as needed)
ip.addr.of.syno:/volume1/movies     /volume1/movies    nfs defaults,auto,rw,nofail,bg 0 0

# tests the mounts  (iterate as required ) get a successful mount and see content)
mount /volume1/movies
ls -la /volume1/movies


# lastly,  assert permissions across NFS because DSM doesn't assign any by default
find /volume1 -type d -exec chmod 755 {} \;
find /volume1 -type f -exec chmod 644 {} \;

Should just about do it for you

Startup the NUC, it will appear as if the Syno.
You’ll want to change its friendly name as appropriate.

Now return to the Syno,
File Station -> Plex share - library/ - Application Support / Plex media Server

Rename Preferences.xml to Preferences.xml.UNUSED
This avoids the Syno conflicting again. it will start as UNCLAIMED next time.

Thanks, appreciate you helping me .

Before I go down this route though what benefit does this give me over just running PMS on NUC with shares on NAS ?

All I did here was as you stated:

  • NUC is the primary host
  • Media still resides on the Syno, accessible over NFS

I saved you time and watched status by transferring your entire metadata Library from the Syno -> NUC “as is” and enmass.

Emulating the Synology directories directly saves you the trouble of “Moving content” steps which can be a royal pain.

ah perfect thanks ill give it a shot then :stuck_out_tongue:

You’ll notice that everything can be undone

  1. I kept the existing NUC “Library” directory which has everything it knows. Rename it and the NUC is back.

  2. On the Syno, Rename “Preferences.xml.UNUSED” to “Preferences.xml” and it is back.

Just to be sure here my NAS structure for media is

volume1/media/movies
volume1/media/tvshows
volume1media/anime
etc…

Would I need to create directories and mounts for each of these or just mount volume1/media ?

Currently waiting for this command to finish…(cd /mnt ; tar cf - ./Library) | tar xf -
seems to be taking some time

Interesting:

Yes, one mount will do /volume1/media will suffice nicely.

You could also just create /volume1

I always show the full detail because some Synology customers have multiple volumes (1-4)