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

Plex Media Server Metadata & Adding Files
209

I’m happy to report my fix match is working again and all of my stuff is working as intended.

I have no idea what when navigating between tabs something is not happy trying to be displayed but that’s for another day. I am happy.

Thank you!

image
image900×556 174 KB

210

Attaching my logs - did the attempt at a manual match at 16:03:xx still got this issue
Plex Media Server.log (524.7 KB)

211

Yep, yours is also due to the database being slow/locked up.

See my post here about what’s going on: Plex Agent no longer working and Add to Watchlist option is also now gone - #202 by drzoidberg33

212

Sorry about that, I did add your user to my allowed list but then didn’t save the changes :person_facepalming:

You should be able to DM me now.

213

Yes.
The first links response is empty, the second one is “o hai”.

214

Thank you for the insights.
I am very disappointed that you stop fixing newly introduced bugs for users that still are bound to the legacy agents before your company does.

I understand that there’s no new development and that everybody should switch to the new agents, but until you publish a robust and fully working API for your current products, I am bound to what I call the classic agents.

Please re-consider your decision. If this stops me from updating the my Plex Media server then your policy is worth nothing.

I can fully understand that you don’t like to fix bugs for two sets of agents. But the easy way woud be (as a company) to test properly before you publish updates that break up functionality. PMS still has them and so should you feel the urge to support those that really are bound to use it (until you API becomes available) or stop using Plex at all.

My personal feeling about that is “why don’t you care about me as a user?”. From a developer’s view, I can understand your sentiment. Please see those that you leave behind not as people who just don’t want to change - as a burden.

I really hope to still be a valuable customer.

1 Like
215

All good! Data sent!

216

Okay, DB is running on Unraid RAID 0 NVME SSDs - should be pretty darn fast. Tried running the ChuckDB repair on it yesterday and that failed. What steps should I be doing / taking on this?

217

Thanks got it!

I’ve tracked down the exact bug causing your issue, I’ve already pushed a fix internally but don’t yet know which release this will be in.

It’s easy to fix though by making a single database query, if you’re comfortable doing that.

The instructions for using the SQLite database command are here: https://support.plex.tv/articles/repair-a-corrupted-database/#toc-1 (You don’t need to run any of the recovery commands here, and only need to run the one below).

Any time you work with the database just make sure that PMS is shut down first.

Then using the instructions above, open your database the SQLite command linked above and run the following query:

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

Then just call:

.quit

And start the server up again. The clean up operation that was locking up the database should not complete successfully.

218

@barney_19 you could also try the above fix, although yours looks a bit more messed up :sweat_smile:

Feel free to DM me your database file also - I’d be happy to take a look to see if there is anything else wrong or it it’s the same underlying problem.

220

I have tried this but same results. Do you want me to send you logs and DB file again?

FYI - My plex runs in a docker container so what I did was:

  1. docker cp plex:/usr/lib/plexmediaserver /volume1/docker/plex/temp (While the container was running)
  2. Shut down the container
  3. Navigate to volume1/docker/plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases
  4. Run /volume1/docker/plex/temp/plexmediaserver/Plex\ Media\ Server --sqlite com.plexapp.plugins.library.db
  5. delete from metadata_items where library_section_id = -4 and guid = ‘’;
  6. .quit

EDIT 2:
I optimized database after the change and that seems to have resolved the issue now. We’ll see if it comes back! Thanks for the help.

1 Like
221

I got it fixed; ran the PlexDBRepair tool twice; first with ignore on, then not. Good to go now.

1 Like
223

Same problem, some logs:
Plex Media Server Logs_2025-05-23_13-05-40.zip (5.0 MB)
Plex Media Server Logs_2025-05-23_13-06-54.zip (5.0 MB)

224

Looks like yours is exactly the same issue as the above, see Plex Agent no longer working and Add to Watchlist option is also now gone - #217 by drzoidberg33

A fix for this will be in the next beta release, otherwise follow the above instructions and let me know if that helps.

Also see @barney_19’s post above, if you don’t come right.

225

I’ll wait for the next beta, hope soon

226

What was very interesting is that the issue on the DBRepair complained about records with duplicate IDs on the Activities table. I cracked open the DB and ran some queries to find the offending records to manually purge them, but I couldn’t find any. Very strange indeed, but just happy to have this resolved and you guys with a fix in the pipeline.

227

I am experiencing the same issue using a docker on unRaid. I have run repairs and checks on my DB twice now, no impact to my issue. I have my docker set to use 8.8.8.8 as a DNS. Only “fix” is to revert back to 1.41.5.9522.

While on 1.41.7.9799 i do see these errors when refreshing metadata on some of my files: [Req#28f24] MetadataAgentPostProcessor: failed to find agent for identifier tv.plex.agents.movie

and

[Req#2b18b] Unknown metadata type: folder

228

Hey @Bipple294 seeing similar issues that I had; I am also on Unraid with Docker. This is the same offending line I was seeing:

May 23, 2025 14:18:32.201 [23185764633400] ERROR - Waited over 10 seconds for a busy database; giving up.

Looks like your DB is getting locked up; have you run this utility from within the Plex Docker console? GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases I had to run it twice; once with Ignore on, and the second time without. Media scans started working as soon as I started PMS back up, both automated and manual.

230

I’ve tried switching to TVDB or TMDB Agents respectively and it could load the metadata of media for some reason. Is there an issue by doing this while we wait for the fix?
Trying to run the sqlite command on unraid seems to be a bit more painful than on other systems hence I would just wait for the update to arrive (hopefully soonish)

231

i have run the repair on my DB three times now. First was with ignore disabled then the last two had ignore turned on. Still no effect on my issue. I tried the latest version 1.41.7.9823, still no fix.