Plex Agent no longer working and Add to Watchlist option is also now gone

[barney_19]

Sorry to hear that - I guess you are not getting error messages on the repair? I was and ignoring those was what resolved it. If you are running repair without an issue then it must be slightly different to mine in terms of root cause.

[Bipple294]

@drzoidberg33

delete from metadata_items where library_section_id = -4 and guid = '';

I tried running this command after realizing i do have an item in my db with a library id of -4 and a blank guid. But i am getting “Parse error: unknown tokenizer: collating”. i tried removing the two fts4 metadata triggers and then running it again, same error message. Does anything else need to be done to run that command?

[drzoidberg33]

@Bipple294

@drzoidberg33

For anyone having issues with the Plex Movie or Plex Series agent not working, please restart your server, wait a couple minutes, then try to refresh/match/fix match some things and grab the server logs and attach them here.

There is no backend issue I’m aware of. Nobody internally has reported any issues and I haven’t seen any issues myself so it could be a regional thing or something specific to an ISP or DNS provider. Logs would help isolate things.

As for the SQL error, you must use the Plex Sqlite command line as described in the post where you quoted that query I provided.

[PilaScat]

Tried this but it tells me segmentation fault, tried even DBRepair tool with ignore but nothing, hope the next PMS update is near, is driving me crazy, every times it reboots I need to redo all

[Bipple294]

Thanks. I was able to find the Plex SQLite at “/usr/lib/plexmediaserver/Plex SQLite” and ran that command on the library db, i didnt receive any errors after running it. But when i browse the DB, i still see a metadata item with a library of -4 and no guid. Still not able to manually or automatically match files.

[jellymunky]

@drzoidberg33 tried dbreapir, changed unraid DNS to google. restarted unraid, re-installed docker, optimized database. nothing seems to work. attached are the logs. would love some guidance.

Plex Media Server Logs_2025-05-26_19-14-52.zip (1.1 MB)

[drzoidberg33]

@Bipple294 @jellymunky There are some fixes I have in the next beta release, it should be landing pretty soon but I’ll provide a link here to the build as soon as it is ready.

[jeramie]

Hey @drzoidberg33 , thanks for looking into all of these!! Mine was doing pretty good for a while but just started back up not being able to match. I restarted plex and grabbed the logs here.

I’ve always gotten a ton of the database is too slow type of warnings, its been on different SSD’s for years but is pretty large. I’m on Unraid and binhex’s docker container.

Plex Media Server Logs_2025-05-27_08-40-09.zip (1.6 MB)

[drzoidberg33]

We’ve got a new alpha build ready which should hopefully resolve the issue for many of you here.

This is still going through QA on our side but if you want to test this build out so long I have the links below.

If you still have issues after this, please check that you’re not affected by this issue: Library.db size more than doubled in latest version and if you are, then this new build will also fix this, it only runs as a schedule task so you could force it by changing the hours that these run temporarily and let it run then change the hours back.

Desktop Platforms

• Windows

  • Intel - 32-bit
  • Intel - 64-bit

• Ubuntu/Debian

  • Intel - 32-bit
  • Intel - 64-bit
  • ARMv7
  • ARMv8

• RedHat/Fedora/CentOS

  • Intel - 32-bit
  • Intel - 64-bit

• FreeBSD

  • Intel - 64-bit

• macOS

  • Universal

NAS Devices

• Asustor

  • ARMv8
  • ARMv7
  • Intel - 32-bit
  • Intel - 64-bit

• Seagate

  • ARMv7
  • Intel - 64-bit

• Synology (DSM 6)

  • ARMv7_Neon (x15 Series (excluding DS115j, RS815), x16 Series (excluding DS216se), x17 Series, x18 Series, and DS414j)
  • ARMv7 (x13 Series, x14 Series (excluding DS414j), DS115j, RS815, and DS216se)
  • ARMv8 (x18 Series, x19 Series, x20 Series)
  • Intel - 32-bit (x10 Series, DS415play, and DS214play
  • Intel - 64-bit (DSM 6.0 or newer)

• Synology (DSM 7)

  • ARMv7_Neon (x15 Series (excluding DS115j, RS815), x16 Series (excluding DS216se), x17 Series, x18 Series, and DS414j)
  • ARMv7 (x13 Series, x14 Series (excluding DS414j), DS115j, RS815, and DS216se)
  • ARMv8
  • Intel - 32-bit
  • Intel - 64-bit

• QNAP

  • ARMv7 (TS-x31, and TS-x31U Series)
  • ARMv7_Neon (TS-x31+, TS-x31P, TS-x31P2, TS-x31X, and TS-x31XU Series)
  • ARMv8 (TS-x28 Series)
  • Intel - 64-bit

• Unraid

  • Intel - 64-bit

• Netgear

  • Intel - 64-bit
  • ARMv7
  • ARMv7 (RN2xx)

• Western Digital (OS 3)

  • WD MyCloud Mirror
  • WD MyCloud Mirror Gen2
  • WD MyCloud EX2100
  • WD MyCloud EX4100
  • WD MyCloud EX2 Ultra
  • WD MyCloud PR2100
  • WD MyCloud PR4100
  • WD MyCloud DL2100
  • WD MyCloud DL4100
  • WD MyCloud EX2

• Western Digital (OS 5)

  • WD MyCloud EX2 Ultra
  • WD MyCloud EX2100
  • WD MyCloud EX4100
  • WD MyCloud Mirror
  • WD MyCloud DL2100
  • WD MyCloud DL4100
  • WD MyCloud PR2100
  • WD MyCloud PR4100

[X_4357]

Unfortunately i’m experiencing the same issue with the agents being unable to match any content. I attached some logs after I rebooted my server. Let me know if the logs are useful.

Plex Media Server Logs_2025-05-28_18-30-57–1.41.8.9834-071366d65-x86_64.zip (515.9 KB)

[X_4357]

I’ve restarted a couple times and same issue. Going back to PlexMediaServer-1.41.5.9522-a96edc606-x86_64.

[drzoidberg33]

You seem to just have some database problems, however you don’t have debug logging enabled so the logs aren’t very useful.

Please check this too:

@drzoidberg33

If you still have issues after this, please check that you’re not affected by this issue: Library.db size more than doubled in latest version and if you are, then this new build will also fix this, it only runs as a schedule task so you could force it by changing the hours that these run temporarily and let it run then change the hours back.

[X_4357]

That’s a bit odd because I checked both options before sending you the logs. I’ll check the other link you sent later this evening or tomorrow and get back to you. Thanks for checking the logs.

[drzoidberg33]

Just don’t ever enable verbose logging unless an employee specifically asks for that, it just makes it more difficult to read the logs (and often things get lost because the logs rollover too quickly).

[X_4357]

Apologies for that. I’ll keep that option turned off next time.

[X_4357]

Here are some fresh logs with verbose logging turned on. The only change on my end was going from a database size of 8192MB to 4096MB. Looks like the agents are matching content properly. I’m wondering if the database size was too large? I’ll keep monitoring to see if the same non-matching behavior starts again.

Plex Media Server Logs_2025-05-29_07-28-52-1.41.8.9834.zip (358.8 KB)

[drzoidberg33]

@X_4357

a database size of 8192MB to 4096MB. Looks like the agents are matching content properly. I’m wondering if the database size was too large? I’ll keep monitoring to see if the same non-matching behavior starts again.

Is there some specific reason you’re changing this value and making it so high?

[X_4357]

I have a big collection so I assumed a higher value would make things run more smoothly but I’m not a Plex database expert. A lower value seemed to fix the matching issues.

[PilaScat]

For the docker image? I’m on plexinc/pms-docker:beta but no update, but dashboard tells me that a new version is available

EDIT: Okay needed VERSION=beta to work, now the metadata thing is fixed!

[drzoidberg33]

I’m honestly not even sure what sort of impact having such a huge cache size has, I doubt it makes any difference beyond a certain point and it could cause issues if set too high.

I’ve personally never needed to touch this setting and don’t have any issues with the default size.

As a general rule, it’s best not to touch advanced settings unless you fully understand the impact they have, especially the negative impacts.