#overlays not working?
1 messages · Page 1 of 1 (latest)
Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.
Including the meta.log from the beginning is a huge help use !logs for more information.
The log would be the first thing to check.
You have been asked to provide your log file, which will allow us to support you further.
You can find your meta.log file within the logs folder of your Plex Meta Manager config folder [right next to config.yml].
You can drag-and-drop your meta.log file directly into Discord, you do not need to upload it to a third-party site unless it exceeds the 50mb size limit.
Please DO NOT manually extract, copy and paste text from your log files directly into Discord as the formatting can be difficult to read and can often redact parts of the log file that are important for full context.
and actually, i cant even get the thing to run now, hence my newest log file being from the 24th.
so reinstalling / fixing python, pip, etc etc. ill get it all going again and then do another run and follow up if its still not applying overlays since i clearly have other things going on at the moment.
ok. so back to functioning again. but still some errors and no overlays arent being applied to new items. heres log:
so theres a number of errors im wondering about, theres a bunch at the very end of the log, but also a few such as
File "/opt/homebrew/lib/python3.10/site-packages/plexapi/server.py", line 704, in query
| raise NotFound(message)
| plexapi.exceptions.NotFound: (404) not_found; (redacted)/library/sections/None/all?collection.locked=1&collection%5B%5D.tag.tag-=Gold%20Star%20Horror&id=400769&type=1 <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
|
[2022-10-01 17:46:24,957] [plex_meta_manager.py:703] [ERROR] | Unknown Error: (404) not_found; (redacted)/library/sections/None/all?collection.locked=1&collection%5B%5D.tag.tag-=Gold%20Star%20Horror&id=400769&type=1 <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
which talks about some collections being locked? why are they locked and how do i unlock them and.. does it even matter? does the collection update anyway if its locked or does not update if locked?
well one issue is my plex token changed, so fixed that
in all these errors:
Unknown Error: (404) not_found; (redacted)/library/sections/None/all?collection.locked=1&coll
That "None" should be a number, the internal ID of a library.
I can't explain why offhand, but in these cases, PMM is getting an empty value for the section ID and is therefore inserting "None" into the URL in place of some number like 3.
That results in the 404 [can't find this] from Plex. The parameters are unrelated to this problem, since Plex can't find the thing it's trying to apply those parameters to.
These:
[WARNING] | Asset Warning: Unable to find asset folder: '3D'
Can all be ignored; you've got asset_folders: true, so PMM is looking for folders named after your collections and is not finding them.
These:
| Letterboxd Error: TMDb Movie ID not found in https://www.themoviedb.org/tv/17139/
Are reporting that a movie ID can't found for that tv thing.
There are a few of these:
[INFO] |== Updating Details of Theme - Witches Collection
[INFO] |
[INFO] | Collection Metadata Edits
| Label | +PMM
[ERROR] | Details: Failed to Update Please delete the collection and run again
Sometimes a collection gets into a state where PMM cannot update it. The fix is to delete it and let PMM recreate it, as noted there.
[WARNING] | mdblist attribute not found
[WARNING] | mal attribute not found
[WARNING] | playlist_files attribute not found
You've removed those sections from your config.
[ERROR] | Unknown Error: Failed to Connect to https://api.themoviedb.org/3: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check'))
TMDB sent a response that wasn't what it said it was. Probably a transient error with TMDB.
When it starts to process overlays, this error kills it right away:
[2022-10-01 19:06:46,573] [plex_meta_manager.py:522] [CRITICAL] | Unknown filter field "label" for libtype "movie". Available filters: ['genre', 'year', 'decade', 'contentRating', 'collection', 'director', 'actor', 'writer', 'producer', 'country', 'studio', 'resolution', 'hdr', 'unwatched', 'inProgress', 'unmatched', 'audioLanguage', 'subtitleLanguage', 'editionTitle', 'duplicate']
Seems like a new Plex token has been seen to fix that.