Plex not discovering Photos after 5 april 2025

Server Version#: 1.41.6
Player Version#: 2025.14.0
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

2925 is 900 years from now. How are you getting photos from the future?

Its a typo. I do have some photos with dates from the future though.
I also have the following error message(s):
Er is iets fout gegaan

Er is een onverwachte fout opgetreden

Hahahaha, back from the future :rofl:

Have you checked your logs for additonal error messages? I suspect you may have a corrupt database, the logs may have a clue confirming that or not.

older photos and other media is working fine. How to repair/ rebuild the database?

Use Chuck’s PlexDBRepair tool.

I stopped the PWS, choosed the Auto option. Exit with cleaning up. Started PWS and now Plex stops directly after start. Even after a un-install, re-install of the most recent version. How to proceed?

PS.
Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.

Exporting current databases using timestamp: 2025-04-27_20.39.18
Exporting Main DB
Exporting Blobs DB
Successfully exported the main and blobs databases.
Start importing into new databases.
Importing Main DB.
Importing Blobs DB.
Successfully imported databases.
Verifying databases integrity after importing.
Verification complete. PMS main database is OK.
Verification complete. PMS blobs database is OK.
Saving current databases with ‘-BACKUP-2025-04-27_20.39.18’
Making repaired databases active
Repair complete. Please check your library settings and contents for completeness.
Recommend: Scan Files and Refresh all metadata for each library section.

Backing up of databases
Backup current databases with ‘-BACKUP-2025-04-27_20.47.51’ timestamp.
Reindexing main database
Reindexing main database successful.
Reindexing blobs database
Reindexing blobs database successful.
Reindex complete.
Automatic Check, Repair/optimize, & Index successful.

First place I would look is the log file

There hopefully will be a clue in there.

Apr 27, 2025 21:04:03.621 [140080005200528] DEBUG - MyPlex: mapping state set to ‘Unknown’.
Apr 27, 2025 21:04:03.622 [140080005200528] DEBUG - Relay: read 8 cached entries from hosts file
Apr 27, 2025 21:04:03.689 [140080005200528] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.39.4, threadsafe=1
Apr 27, 2025 21:04:03.689 [140080005200528] ERROR - SQLITE3:0x80000001, 14, cannot open file at line 41714 of [a29f994989]
Apr 27, 2025 21:04:03.689 [140080005200528] ERROR - SQLITE3:0x80000001, 14, os_unix.c:41714: (13) open(/volume1/PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db) - Permission denied
Apr 27, 2025 21:04:03.690 [140080005200528] ERROR - Promise destroyed without handling exception: Promise fell out of scope without resolving or rejecting
Apr 27, 2025 21:04:03.796 [140080005200528] DEBUG - [JobRunner] Job running: /volume1/@appstore/PlexMediaServer/CrashUploader “–directory=/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Crash Reports/1.41.6.9685-d301f511a” --version=1.41.6.9685-d301f511a --platform=Linux “–platformVersion=DSM 7.2.2.72806-3” --serverUuid=25d859eff1f17f59ad2ce322b408f0233792bd18 --userId=XYZ --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Synology --model=x86_64 --device=DS1621+ --sessionStatus=crashed --sessionStart=1745780643 --sessionDuration=0

XYZ=my user id
I don’t have a clue..

There’s a permissions error opening the sqlite3 database, did you somehow change the ownership of the db when you ran the utility?

No, i did not. To me the repair utily made it worse, Plex stopped after a few seconds. So i uninstall completly and re-install completly.

Well I don’t know anything about permissions and ownership on a sysnolgy nas install. Maybe someone here in the forums will know how you can check the permissions and ownership of the db and fix it if it is not correct. The error points to permissions as the issue.

Looks like someone stuck their fingers in the PlexMediaServer shared folder and got them slapped :slight_smile: :see_no_evil_monkey:

  1. The PlexMediaServer shared folder is for the exclusive use of PMS internal files. It is NOT as flexible as it was in the DSM 6 days.

  2. In DSM 6, we had the Plex user. This username is obsolete and should be deleted. DSM 7 required a new username PlexMediaServer, which is a System Internal User (hidden from the ‘Local Users’ menu).

  3. The remedy to this comes in two forms:

  • Fix the shared folder permissions
  • Fix the permissions of all files inside the shared folder

Part 1a

  • Control Panel - Shared Folder - Highlight PlexMediaServer - EDIT
  • Permissions tab
  • Make certain System Internal User (dropdown) grants PlexMediaServer R/W

Part 1b

  • Open FileStation
  • Left panel
  • Right-click PlexMediaServer
  • Properties
  • Permission tab
    Make certain PlexMediaServer is listed in the permissions
    –Use ‘Create’ to add it if you don’t see it
  • Check **Apply to this folder, sub-folders and files
  • SAVE

Part 2

Advise your progress

For future refence please:

  1. Don’t touch any permissions for PlexMediaServer
  2. Don’t use any “How-Tos” from DSM 6; None of them apply

NOTE: When you run the Task Scheduler job, make CERTAIN to email yourself the results. This is the only way you’ll know it’s done and ok to proceed.

@helphand

Thanks for that but DSM is configured differently.

  1. plex:plexPlexMediaServer:PlexMediaServer

  2. /var/lib/plexmediaserver/var/packages/PlexMediaServer/shares/PlexMediaServer

  3. Shortcut to logs is: PlexMediaServer/AppData/Plex Media Server/Logs
    using the FileStation graphical file manager

I tried to keep it as close to Linux standards as I could.

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