DSM 7: "Scan my Library Automatically" no longer works

I updated my Synology DS418play to DSM 7.
Added the new Plex from https://www.plex.tv/media-server-downloads/
Added the Read/Write rights.

Everything seemed to work properly, except that when I ADD or REMOVE data from one of the libraries, the Library is no longer automatically updated.
I have to manually perform a “Scan Library Files” to update the library…
The setting In Settings/Library > “Scan my library automatically” is enabled though.

Worked fine before the update.
Installed Plex Version = 1.23.6.4881-7000 (Fresh from the Plex download site)

Re-applying the permissions fixed it.
Thank you very much !

Plex Media Server Logs_2021-09-06_12-49-57.zip (4.9 MB)
Hello,

I’m going to bump this threat since I have a very similar issue for which (re)setting the permissions doesn’t seem to work. When media is added, after fixing permissions the library is scanned automatically and new content appears. However, when deleting a content at file level, the library scan is no longer initiated. The deleted content is removed from the library only when:

  • Scheduled library scan runs (for me set once a day)
  • New content is added and the whole library is being scanned (since it is set not to only check the directory that has changed)
  • Manual library scan is started by me

Please see attached logs. I used !TESTDIRECTORY and TESTDIRECTORY2 to reproduce the problem. You can hopefully see that the first first directory is picked up upon creation, however not removed after deleting, only when the second directory is created.

I have not had this problem before the DSM7 upgrade and migration.

Any help is appreciated, let me know if you need more input.

Thanks,
Csaba

@springdale

I’m trying to figure this one out.

It looks like a bug in DSM 7 itself.
I’m checking against the other Linux distributions to make 100% certain it’s not a PMS regression.

Would you mind doing the following?

  1. Verify DEBUG logging ON, VERBOSE logging OFF.
  2. Restart PMS
  3. Wait 2 minutes of it being completely idle (so the inotify system can setup)
  4. Download the logs ZIP and attach it.
1 Like

Plex Media Server Logs_2021-09-06_22-00-17.zip (4.1 MB)

@ChuckPa

Sure, here you go. Thanks for looking into it!

Thank you for your reply. Instead of disabling the recycle bin, could it work if I add #recycle/ to the .plexignore file? Also the Synology Download Station stores incomplete downloads on a separate shared folder and moves them only after completion so that should not be a problem IMHO.

I appreciate your comments but for our current usage pattern it is good the way it is. Turned out I already added the recycle bin and the BTRFS snapshots folder (which I made visible) to the .plexignore file and they don’t show up in the libraries. Why is still the recyle bin folder mentioned in the logs I don’t know, but I don’t think it has to do anything with the issue I have mentioned. @ChuckPa what do you think?

Well…

@springdale

Apologies for the delay.

I spoke with the dev about this. There exists another situation where the notify loader generates an exception and stops adding.

In general, it doesn’t like “permission denied” – which should not be fatal to the scan.

The issue is open with Engineering to fix.

@ChuckPa thanks and no problem. However the directory’s name with no access is in the .plexignore file, how could that be included in the logs?

There are two mechanisms at work here.

  1. Automatic change notification (which, by default, includes all directories under the top directory). This list is loaded when PMS starts. This is where you’re seeing the error.

  2. The ignore rules (.plexignore) – which tells the scanner/matcher the ones to ignore.

The normal flow would be :

  1. You change a file in a monitored directory
  2. The Linux kernel raises the notification of change
  3. PMS responds
  4. It prepares to scan & match
  5. However, it realizes the file is to be ignored per the ignore file – so it stops
  6. When not excluded, normal addition process occurs.

In my writeup for engineering, what I see as the main problem here is a regression.

Specifically, “Permission Denied” errors should not be fatal.

1 Like

@ChuckPa thank you very much for explaining and taking care of this issue. Keep up the great work! :slight_smile:

All the best,
Csaba

HI any update on this issue? I 'm also experiencing the same problem? Thanks in advance for your help.

@amadeodonofrio

May I see the DEBUG logs ZIP where this is happening again?

Having your data will allow me to show their solution was insufficient.

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