Addedat time in XML showing 79 years in the future

Plex Media Server Desktops & Laptops
1

Server Version#: 1.13.9.5456 and 1.14.0.5470 (tried both, no change)
Player Version#: Browser

Hey guys,

I recently buit out a new VM for Plex that upgraded from Ubuntu Server 16.04 to 18.04. To give some context, my plex server is a VM on my ESXi host that then mounts my NAS via fstab. The NAS and Plex VM live off to separate zones on my firewall. Basic diagram would be

Plex > Firewall DMZ > Firewall Inside > Router > NAS - SMB/CIFS share

After about 24 hours, all of the metadata for my media populated, but I am running into an issue where 4 movies, 1 season of 1 TV show, and 2 entire TV shows (8 seasons on one, 21 on another) are showing an added value of ‘addedAt=“4039387200”’, which converts to 79 years from now. All of this media has the exact same time.

I know there are other posts on this from the past, but let my rule out what I’ve already tried:
-Clean sweep: moved the files to a different directory on the NAS, scanned for library files, clean bundles, confirm the Plex doesn’t have them anymore, and move them back;
-I’ve tried using sqllite3 to inject the added at value in the past for anything on the server. Example below:
sqlite3 com.plexapp.plugins.library.db "UPDATE metadata_items SET added_at='2016-12-25 00:00:00' WHERE id='%';"
-I tried disabling IPv6 because I saw in older posts from years ago that caused issues, but that actually forced the VM into a read-only file system, so I had to restore from a previous VM snapshot.

This is my second go around with a new 18.04 VM and I’ve had issues with different media each time, so I know it’s not the specific movies or TV shows I’m running into currently.

Any help would be greatly appreciated. I’m not the best SQL coder (network-based security engineer lol), and I think that’s the easiest way to fix it. Just don’t know if it’s the code or something with plex…

Thanks!

Example body of XML (XXXXXXXXX used to remove identifying data)

<Video ratingKey="373" key="/library/metadata/373" guid="com.plexapp.agents.imdb://tt5913184?lang=en" librarySectionTitle="Movies" librarySectionID="1" librarySectionKey="/library/sections/1" studio="XXXXXXXXX" type="movie" title="XXXXXXXXX" contentRating="XXXXXXXXX" summary="XXXXXXXXX" rating="XXXXXXXXX" year="2018" tagline="XXXXXXXXX" thumb="/library/metadata/373/thumb/1544315211" art="/library/metadata/373/art/XXXXXXX" duration="XXXXXXXXX" originallyAvailableAt="XXXXXXXXX" addedAt="4039387200" updatedAt="1544315211" ratingImage="imdb://image.rating">

2

If you revert to the previous PMS version,
Remove and re-add the media,
Does it correct what you see?

3

Negative. I tried this yesterday and when the metadata was finished populating this morning, the same issue occurred. Because of that addedat time stays the same, the “recently added” lists just always hold those movies and TV shows as the first few.

4

The procedure I imply is:

  1. Remove media from the monitored location
  2. Scan files
  3. Empty Trash
  4. Clean bundles
    – media is now gone –
  5. Revert to previous version of PMS
  6. Move media back into position
  7. Scan and allow to be added as new
5

I do question the VM, and its date/time. What does its clock report?
I suspect it’s not properly sync’d to NTP / using the correct “real time clock” setting.

6

NTP is set and synced properly. All my internal subnets are synced to the same internal NTP server, which is fetching NTP from pool.ntp.org US-based servers. I can try the method you’re noting above. I’ll export the VM and spin up another, identical VM and try that to see if it works,

7

The procedure I am instructing is the official “Plex Dance”.

It purges the metadata as well as the database records.
This is why it is done as described.
Anything else is incomplete.

8

The plex dance doesn’t include downgrading the plex version. The official plex article is here. That’s why I’m skeptical, but like I said, I will try it. The version, given it’s a brand new VM, shouldn’t matter. I started on 1.13, the issue was present, upgraded to 1.14, brand new VM on 1.40, same issue. This doesn’t appear to be a version-based issue, as this has been reported since 2012 with Plex. But again, I’ll give it a shot.

9

The Plex Dance (to remove metadata) is independent of the software version.

I am attempting to help determine if this is an issue in this release or an issue with your system configuration on particular since this is the first report I have of it for this version.

If you need a lower version, I can provide one.

10

Thanks, Chuck. If you can provide me something like 1.13.51XX, I think that’s what my old VM was running. Because it’s corrupt, I’m trying to decrypt the VMDK so I can get a deb pkg listing, but it’s taking some time to do that. I’m not 100% what version that was running with this setup not being an issue (VM cifs sharing to a NAS, that is).

11

Here is PMS 1.13.4.5271 It predates the 1.13.5 HTTP preferences just in case there are other lurking issues. Networking is more pure and easy to diagnose with it.

If you’re running Linux -> Linux NAS using CIFS, that needs to change pronto.

Debian add package nfs-common and you now have NFS capability to the Linux NAS.

https://drive.google.com/open?id=1hvqdbdlXbeRT4JI_KvGdhzpRp7TBS530

12

Thanks, Chuck. It’s using fstab and cifs-utils but it’s running over SMBv3. I wouldn’t run just straight cifs purely because of the security risks, more so than the obselete nature of straight cifs :stuck_out_tongue: I just finished exporting the latest OVA of the current VM so I’m gonna spin up a separate VM to try the old software. I’ll update with my findings.

13

clarify please the CIFS relationship? the VM or the DATA is over a CIFS mount?

14

The media the VM polls from the NAS is via fstab, using cifs but forced over SMBv3

15

The NAS is a Linux NAS?

16

Yes. Originally I used this method with a QNAP and now I have a Synology.

17

If you want the security,

  1. Synology - File Services - NFS - Advanced - Enable NFSv4
  2. Add the nfs-common
  3. Now you can switch to NFS and mount with option vers=4.2
18

I have both QNAP and Syno machines here. No issues whatsoever provided I remain in NFS

19

I’ll try that out on this OVA redeployment. OVA template is 80% imported so I’ll start with that and then deploy the old PMS version.

20

This is an OMV container ?

That changes a lot

First and foremost, before attempting to get PMS working, I strongly recommend getting NFS working correctly.

You should be able to manually add a file on the Syno, see the same date/time created in your VM