Unable to upgrade library scanner

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

Hey All,

I’m trying to upgrade my libraries to use the newer scanner (Plex Series Scanner) in conjunction with the movie db agent. When I flip the settings in the library and save… it tells me the library needs to be upgraded. When I click upgrade… nothing happens except the settings flipping back.

I’ve tried making new libraries and setting them manually… nothing

I’ve made a completely new plex config… no dice.

I’ve made the edit in the DB manually… no dice.

one interesting note is if I flip the scanner in the DB, but leave the agent alone (non compatible now), when I refresh the metadata… plex crashes… so it is doing something… I just don’t know what. Also I am running this server in a container, but all of the mount points are r/w and the container sems to have the correct perms. I can drop my logs in here, but they don’t seem to show anything

Can you please provide the server DEBUG logs ZIP file?

It sounds like something’s broken in there.
The logs should show it

Absolutely. I had verbose on, so I wiped all logs, enabled debug and reproduced… these logs should be fairly clean.

Plex Media Scanner.zip (26.1 KB)

apparently there is a button to grab em so here is that file. Again, this is a container, and I had a DNS issue a few months back I ended up resolving across all containers.

Plex Media Server Logs_2025-08-28_20-52-38.zip (2.3 MB)

Which version were you using before this ?

In “Settings - Account” do you have Watch History Sync enabled ?

I have a build script that will rebuild the container with the newest version. I would say I’m fairly consistent in hitting all official versions. And yes, sync settings and ratings is on for my primary account.

Given what’s happening, and having a rapid way to rebuild, I would nuke the existing and create fresh.

Ok so I have tried a completely clean build and it failed to create the libraries. I’ll do a completely clean build with a blank config and see what happens. I’ll let ya know when I get it working in a few days

In your build procedure, do you use PUT / POST statememts which set the agents ?

If so – Remove them and try again
(The old endpoints are no longer functional)

Okay so I did a completely new blank container, I did a new install on the host with the existing config, I also did a blank config and had the same results every time…the next thing I’m going to try is bypassing merge FS which is what I’m using for the file system… that is the only common denominator

Same result… I genuinely think this is a problem somewhere in the application on the Linux distro.

Ok so I have tried new container with old config. New container with new config. Host with old config. Host with new config. Host with old config and new filesystem and host with new config a new filesystem. I am out of things to test. The exact same behavior persists through all tests.

Sent you a PM (upper right corner)

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