Plex not adding new media after update

Server Version#: 1.18.2.2041
Player Version#: Web 4.8.4
My Log Plex Media Server Logs_2019-11-20_00-11-56.zip (4.7 MB)

So after downloading and installing the update from the 13th (I also updated today to see if it would help, it didn’t) which was a hassle and a half there, requiring me to completely uninstall the old install and restart to install the new version, I am finding that Plex is not adding any new media even when I have it scan the libraries. All the libraries are on drives plugged in to the motherboard via sata, no middle man set up or anything just plain old drives. It was working before the update just fine and it’s starting to frustrate me as I mainly use Plex to sync to my phone to walk things at work on my lunch and breaks. Any help would be greatly helpful.

Bumping. I have tried to revert back to 1.18.0.1944 but it’s still not updating.

I have this problem after updating to this same build, but worse (I can no longer play media files or even access some entire libraries). This is the third time this has happened with Plex, and so far my only solution has been to completely reinstall my Plex Media Server which is crazy because of how long it take because of all the customization I have to do (lot of anime content which Plex doesn’t exactly like). If you figure out a way to fix this, or if anyone has any suggestions for you please update this thread.

Sadly, I am just going to rebuild my whole server as nothing could fix this. I tried the whole way back to 1.17 builds with no luck.

I got the same problem, but on macOS.

Plex isn‘t adding new movies I‘m copying to my external drive. I have no idea why and I already tried to copy the movies to another drive. No success.

The same happens with some TV show episodes. Weirdest thing here is, that former episodes in the same folder were picked up, but new episodes are not.

I also checked permissions and correct unix owners/groups of the files. Everything is the same as the movie files that were picked up by Plex.

I‘m following the naming scheme strictly, and haven‘t changed it in years.

Another thing I noticed is, that when I switch to folder view in Plex, it shows the movie folder, but not the file inside of it. It seems like Plex doesn‘t even realize the movie file exists.

I even tried to create a new library and added my folders there. Plex says the library is empty. I can still play all indexed movies in the regular library, so Plex can do “something” with my files.

I‘m seriously out of ideas right now and have no idea how to troubleshoot this.

Did you ever find a solution?

I’m seeing the same behavior after upgrading from 1.17.0 to 1.18.2.2058 on Linux, debian. Looking in the scanner logs, it seems to map all new files to the same id:

Nov 23, 2019 14:51:52.400 [0x7f40bc122680] DEBUG - Added new metadata item (One-punch man) with ID 20395
Nov 23, 2019 14:51:52.404 [0x7f40bc122680] DEBUG - Updating metadata item (save) (One-punch man) with ID 20395

And for a completely unrelated movie, in another library:

Nov 23, 2019 16:53:36.908 [0x7f77aee4a680] DEBUG - Looking for path match for [/storage/Swedish/The Grinch (2018).mkv]
Nov 23, 2019 16:53:36.916 [0x7f77aee4a680] DEBUG - Added new metadata item (The Grinch) with ID 20395

Downgrading to 1.17.0.1709 instantly fixes the problem. I was really looking forward to the subtitles fixes in 1.18 and hoped it would have stabilized by now, but boy was I wrong… :joy:

same.
“(Agents) Make the Framework use modern HTTP libs, fixes certain TheTVDB requests failing among others.”

this wannabe fix made it worse

Plex and metadata … it’s a never ending story of bugs

I checked my logs, and it’s the same problem as @jishi, Plex is adding everything under the same ID

Nov 23, 2019 20:07:20.499 [0x7fffabdf13c0] DEBUG - Added new metadata item (Moviename) with ID 141721

Downgrading PMS to 1.17 fixed it for now.

Are you saying that 1.18.1 might work fine? Because I would still like to be on 1.18 for the subtitles fixes.

It’s beyond me how one can intermix features and bugfixes like this, especially since regression testing seems to be non-existent.

Sadly I just deleted my cache, which was a battle and a half due its massive size, and reimported my media. Picked up everything now including new media.

But it’s not an acceptable solution to have to re-import your whole library, especially since 1.17 works fine with the same library.

They need to get their ■■■■ together, and actually maintain a stable version which receives all bugfixes, then they can go to town with the unstable version all they want.

Right now it is impossible to keep track of which version actually works decently for your specific case, and it’s a constant battle to find “the next, working version”. Just the fact that people keep putting updates on hold is a good indicator that they have failed with their release quality tremendously, since the dawn of day, I would add.

Anybody found a solution for this? I would like to update to the latest version, but not if it still won’t find any of my media

No, not sure why this isn’t taken seriously.

I now noticed in the logs with the latest version (1.18.3.2129), and I think the reason for the repeated metadata ID is because I get an error when adding:

0x7fc223b42680] ERROR - SQLITE3:(nil), 1, table media_items has no column named color_trc in "insert into media_items (library_section_id,section_location_id,metadata_item_id,type_id,width,height,size,duration,bitrate,container,video_codec,audio_codec
Dec 09, 2019 19:01:05.256 [0x7fc213fff700] DEBUG - HTTP 200 response from GET http://127.0.0.1:32400/:/metadata/flushMetadataCounterCache
Dec 09, 2019 19:01:05.262 [0x7fc223b42680] ERROR - Exception inside transaction (inside=1) (…/Library/MetadataItem.cpp:3536): sqlite3_statement_backend::prepare: table media_items has no column named color_trc for SQL: insert into media_items (library_section_id,section_location_id,metadata_item_id,type_id,width,height,size,duration,bitrate,container,video_codec,audio_codec,display_aspect_ratio,frames_per_second,audio_channels,interlaced,source,hints,display_offset,settings,created_at,updated_at,optimized_for_streaming,deleted_at,media_analysis_version,sample_aspect_ratio,proxy_type,extra_data,channel_id,begins_at,ends_at,color_trc) values (:media_items_library_section_id,:media_items_section_location_id,:media_items_metadata_item_id,:media_items_type_id,:media_items_width,:media_items_height,:media_items_size,:media_items_duration,:media_items_bitrate,:media_items_container,:media_items_video_codec,:media_items_audio_codec,:media_items_display_aspect_ratio,:media_items_frames_per_second,:media_items_audio_channels,:media_items_interlaced,:media_items_source,:media_items_hints,:media_items_display_offset,:media_items_settings,:media_items_created_at,:media_items_updated_at,:media_items_optimized_for_streaming,:media_items_deleted_at,:media_items_media_analysis_version,:media_items_sample_aspect_ratio,:media_items_proxy_type,:media_items_extra_data,:media_items_channel_id,:media_items_begins_at,:media_items_ends_at,:media_items_color_trc)
Dec 09, 2019 19:01:05.263 [0x7fc223b42680] ERROR - Exception assimilating media item in Silicon valley: sqlite3_statement_backend::prepare: table media_items has no column named color_trc for SQL: insert into media_items (library_section_id,section_location_id,metadata_item_id,type_id,width,height,size,duration,bitrate,container,video_codec,audio_codec,display_aspect_ratio,frames_per_second,audio_channels,interlaced,source,hints,display_offset,settings,created_at,updated_at,optimized_for_streaming,deleted_at,media_analysis_version,sample_aspect_ratio,proxy_type,extra_data,channel_id,begins_at,ends_at,color_trc) values (:media_items_library_section_id,:media_items_section_location_id,:media_items_metadata_item_id,:media_items_type_id,:media_items_width,:media_items_height,:media_items_size,:media_items_duration,:media_items_bitrate,:media_items_container,:media_items_video_codec,:media_items_audio_codec,:media_items_display_aspect_ratio,:media_items_frames_per_second,:media_items_audio_channels,:media_items_interlaced,:media_items_source,:media_items_hints,:media_items_display_offset,:media_items_settings,:media_items_created_at,:media_items_updated_at,:media_items_optimized_for_streaming,:media_items_deleted_at,:media_items_media_analysis_version,:media_items_sample_aspect_ratio,:media_items_proxy_type,:media_items_extra_data,:media_items_channel_id,:media_items_begins_at,:media_items_ends_at,:media_items_color_trc)
Dec 09, 2019 19:01:05.264 [

Seems like there is some kind of db migration error here.

Are you seeing the same error in your Scanner log? @lauridsd?

I upgraded a friends server from 1.10 -> 1.18.2 and his installation works, so this affects a smaller number of users probable due to which versions you have jumped through.

Also makes it really hard to pinpoint when you don’t have access to all previous version of Plex Server. ■■■■ decision especially with the buggy history of this software.

Adding some more info, since this got me thinking that migrations actually fail when upgrading. Checked for errors, and found these during startup after upgrade:

Dec 09, 2019 22:59:27.057 [0x7f1ae0332740] ERROR - SQLITE3:(nil), 1555, abort at 6 in [INSERT INTO vacuum_db.‘tags’ SELECT*FROM"main".‘tags’]: UNIQUE constraint failed: tags.id
Dec 09, 2019 22:59:27.065 [0x7f1ae0332740] ERROR - SQLITE3:(nil), 19, statement aborts at 1: [VACUUM] UNIQUE constraint failed: tags.id
Dec 09, 2019 22:59:27.072 [0x7f1ae0332740] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: UNIQUE constraint failed: tags.id

And also this one, related to the error I get:

Dec 09, 2019 22:59:27.220 [0x7f1ae0332740] DEBUG - Running forward migration 20190616032400.
Dec 09, 2019 22:59:27.220 [0x7f1ae0332740] DEBUG - Captured session 0.
Dec 09, 2019 22:59:27.221 [0x7f1ae0332740] DEBUG - Captured session 1.
Dec 09, 2019 22:59:27.221 [0x7f1ae0332740] ERROR - SQLITE3:(nil), 1, duplicate column name: color_trc in “ALTER TABLE ‘media_items’ ADD ‘color_trc’ varchar(255)”
Dec 09, 2019 22:59:27.221 [0x7f1ae0332740] DEBUG - Analyzing database.
Dec 09, 2019 22:59:27.223 [0x7f1ae0332740] DEBUG - Vacuuming database.
Dec 09, 2019 22:59:27.334 [0x7f1ae0332740] INFO - SQLITE3:(nil), 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Dec 09, 2019 22:59:27.338 [0x7f1ae0332740] DEBUG - Completed forward migration 20190616032400.

Which also makes me wonder how it figures that the migration was successful…

For me, not even 1.17.0.1841 works anymore. I just can’t add any more media at all…

Don’t have access to the logs right now, but will check them tomorrow!

I don’t quite understand why Plex isn’t noticing this either.

In case anybody with the same problem comes across this thread: I fixed by doing a database repair: https://support.plex.tv/articles/201100678-repair-a-corrupt-database/