#Updated version, new items not receiving overlay.
1 messages · Page 1 of 1 (latest)
Welcome @sudden ridge!
Someone from <@&938443185347244033> will assist when they're available.
Including the meta.log from the beginning is a huge help, type !logs for more information.
You can press the "Close Post" button above or type /close at any time to close this post.
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Author of Linked Message: Papertankz
Person who Invoked the Command: Papertankz
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - 💥 [CRITICAL]
Page 08: Rec 02 - ❌ ANIDB AUTH ERRORS
Page 09: Rec 03 - ❌🔒 BLANK API KEY ERROR
Page 10: Rec 04 - ❌ [ERROR]
Page 11: Rec 05 - ❌🛠️ INCOMPLETE LOGS
Page 12: Rec 06 - ❌ MY ANIME LIST CONNECTION ERROR
Page 13: Rec 07 - ❌ TRAKT CONNECTION ERROR
Page 14: Rec 08 - ⚠️ [WARNING]
Page 15: Rec 09 - 💬💡️ PLEX DB CACHE ADVICE
You need to update your config file for the new version. See: https://metamanager.wiki/en/latest/pmm/faqs/#pmm-120-release-changes
so based on my config, I need to remove overlay_path: and replace it with overlay_files:
Well I have collections and overlay, so I need to add both collection_files and overlay_files?
I dont have seperate files for these, all of that lives off the main config.yml file. would I point the path to config.yml?
YAML checked and is NOT valid. Error message:
while parsing a block collection
in "<unicode string>", line 5, column 5:
- remove_overlays: false
^
expected <block end>, but found '?'
in "<unicode string>", line 6, column 5:
overlay_files:
^
Good thing you deleted that before I hit save lol.
overlay_path becomes overlay_files. metadata_path becomes collections.
Yeah, sorry. Trying to figure out the issue. It looks good but there must be some strange character somewhere.
No worries! I updated the four lines and running it again. Will check back in a few mins.
overlay_files and collections for both TV and Movies.
With the release of PMM 1.20, several changes have taken place that we would like to make you aware of, please read the below.
If you do not read the below and update your configurations, you will see new errors in your log files
The attributes metadata_path and overlay_path are now legacy, and will likely produce an error similar to metadata attribute is required when running PMM.
Click here to learn more
The attributes remove_overlays, reset_overlays, reapply_overlays and schedule_overlays are now Library Attributes and are called at the library level rather than within overlay_files.
Click here to learn more
As a result of IMDb changing their back-end code, imdb_list can no longer be used for URLs which start with https://www.imdb.com/search/title/ or https://www.imdb.com/search/keyword/
Click here to learn more
Due to FlixPatrol moving a lot of their data behind a paywall, the existing setup no longer works.
Click here to learn more
The PMM Default file other_award is now deprecated and will no longer function.
Individual PMM Default files have been introduced for several Awards, see the Awards List for more information on the new options.
overlay_path becomes overlay_files. metadata_path becomes collection_files. playlist_sync_to_user should be playlist_sync_to_users. I'm not sure exactly what the issue is with the formatting though.
YAML checked and is NOT valid. Error message:
while parsing a block collection
in "<unicode string>", line 5, column 5:
- remove_overlays: false
^
expected <block end>, but found '?'
in "<unicode string>", line 6, column 5:
overlay_files:
^
So the remove_overlays has to be moved to the library operations. In the example I uploaded, the "- " has to be removed and the it will validate the yaml. I'll upload it again with the changes.
Updated and running now. Will check back in 15-30 mins.
Cool... you got it. Btw, what editor are you using to do this @sudden ridge ?
notepad++
Didnt seem to solve it
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Author of Linked Message: Papertankz
Person who Invoked the Command: Papertankz
File Name: meta1.log
Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - 💥 [CRITICAL]
Page 08: Rec 02 - ❌ ANIDB AUTH ERRORS
Page 09: Rec 03 - ❌🔒 BLANK API KEY ERROR
Page 10: Rec 04 - ❌ [ERROR]
Page 11: Rec 05 - ❌ MY ANIME LIST CONNECTION ERROR
Page 12: Rec 06 - ❌ TO BE CONFIGURED ERROR
Page 13: Rec 07 - ❌ TRAKT CONNECTION ERROR
Page 14: Rec 08 - ⚠️ [WARNING]
I double checked the API key for sonarr/radarr. The root folder is the only thing I thought was weird. I tried to add the top level of the TV directory and it didnt work. I tried to add the specific folders within the TV folder as well.
I edited the config to only 1 of the root folders, got a successful connection this time. Running again, will update soon.
We highly recommend to use a decent editor software to manage PMM's .yml files.
Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in PMM.
This can save a lot of time and headaches.
Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/meisnate12/Plex-Meta-Manager/nightly/json-schema/config-schema.json
Other options:
Notepad++ (Windows only, Opensource & Free)
Website
Sublime Text (Windows/Mac/Linux, Paid)
Website
For further details and a short list of highly recommended extensions, you can also take a look here.
Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our PMM schema (Click on image to get a better view):
This is why I asked... about the editor.
I don't think you shared back your changes and from what you wrote, I did not think it would work...
Yeah I changed it, ran it and saw a successful connection to radarr/sonarr. I can cancel it and send the log again real quick
Would you like more information on how to provide a log file?
Answer yes to both logscan prompts please
The parsed config file is what we want to open with the vscode with those extensions
Drop meta.log in here and answer yes to both prompts please. Thanks
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Author of Linked Message: Papertankz
Person who Invoked the Command: Papertankz
File Name: meta2.log
Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - 💥 [CRITICAL]
Page 08: Rec 02 - ❌ ANIDB AUTH ERRORS
Page 09: Rec 03 - ❌🔒 BLANK API KEY ERROR
Page 10: Rec 04 - ❌ [ERROR]
Page 11: Rec 05 - ❌🛠️ INCOMPLETE LOGS
Page 12: Rec 06 - ❌ MY ANIME LIST CONNECTION ERROR
Page 13: Rec 07 - ❌ TRAKT CONNECTION ERROR
Page 14: Rec 08 - ⚠️ [WARNING]
I cancelled the scan, grabbed the meta.log, and hit yes to both prompts
Perfect. Is vscode with those two extensions running on Your machine?
I dont believe so, is that required for the new version? I was not running it for the previous version which worked perfectly.
It's about using an editor that leverages our schema-json
And editing the config file with more accuracy
ah gotcha, I typically use Notepadd++
Which won't help
1 sec as I open your file
See the issue?
At least 1 is shown here
plural?
notepad++ does not highlight that
This is why we suggest the editor and those two extensions along with the first schema line
makes sense, I will get that installed.
We want to help people fish... not just with a line and hook (Notepad++) but with a fishing pole, boat, bait, depth sounder (VS Code)
Whoops! Made a typo! Better check under the TV shows, too!
Vscode with schema will give you automatic fill like shown to reduce typos
Are you using AniDb? Or Trakt anywhere? Until you fill those out, anything in PMM/plex that needs it won't work.
I am not using those, I can delete them or comment them out
Yes.
Comment the top line out with a #
Property playlist_sync_to_user is not allowed.yaml-schema: settings
Not sure what this means? if its erroring out, just comment it out?
Should be users (plural).
Thank you!
Tip... if that happens again, backspace far enough back to then type the next character a d the VScode will offer autocomplete options ...
Tried to show you that here but it's a static image so not obvious: #1201212862824190003 message
Updated the config file, no errors that I can see in VSC.
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Version: 1.20.0 (Python 3.10.12)
File Error: requirements.txt not found
PlexAPI Version: 4.13.4
Platform: Linux-5.15.0-92-generic-x86_64-with-glibc2.35
Memory: 31 GB
Run Command: Plex-Meta-Manager/plex_meta_manager.py -r
Finished Run
Version: 1.20.0
Finished: 16:47:06 2024-01-28 Run Time: 1:01:37
as of 2024-01-29 01:26:40
1.20.0
1.20.0-develop14
1.20.0-nightly24
Looks like you might need to get those apikeys set up in your config...
Page 11 seems to say so at least
Did you install requirements? I see an error "File Error: requirements.txt not found ". Also, your assets directory doesn't exist.
NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.
The update method depends on how you installed it.
I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.
This is the "fussiest" method of update.
I'm running locally and retrieved the code via git:
cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull
For BRANCH_NAME, substitute master, develop, or nightly
You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt
Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.
I'm using docker locally:
docker pull meisnate12/plex-meta-manager:TAG_HERE
replace TAG_HERE with latest, develop, or nightly
Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].
I'm using docker on a NAS or some other remote context:
Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.
Install requirements please as per bot...
And do that from within your activated PMM-venv
I commented those out. Not sure why its still showing an error there.
There is an error around requirements
We need you to install the requirements as per the bot message
#1201212862824190003 message
Cakeybot message
If I delete everything, keeping a copy of the config, and doing a clean install then copying the config would that solve the issue?
Shouldn't have to do all that; just installing the requirements should be sufficient.
I followed the commands from Cakey Bot, that should fix the issues I assume
But if you want to start fresh you can do so. the config file should be fine unless you are referring to your own YAMLs or images.
If you share the commands that you are using and what is output after those commands, we can guide you on whether things are good or not. Rather than starting all over
I already did those commands, didnt take any screen grabs. Movies seems to be fixed, the new ones added have received the overlay. It is choochin through TV atm.
can you drop the meta.log in here (even if its not finished yet) to quickly review it?
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Version: 1.20.0-nightly24 (Python 3.10.12)
File Error: requirements.txt not found
PlexAPI Version: 4.15.7
Platform: Linux-5.15.0-92-generic-x86_64-with-glibc2.35
Memory: 31 GB
Run Command: Plex-Meta-Manager/plex_meta_manager.py -r
The footer was empty/not found in meta1.log. Go see recommendations pages.
as of 2024-01-29 18:28:09
1.20.0
1.20.0-develop14
1.20.0-nightly24
Done
File Error: requirements.txt not found
So I need to create that .txt, do I need to populate it with anything?
that should already be there... almost seems like you altered the files or removed files that were part of the git pull
I ran the commands from the bot. If that file wasnt created automatically should I run the commands again?
1 sec
these are the commands I run from my W11 machine with an open powershell terminal:
c:
cd C:\Users\bullmoose20\Plex-Meta-Manager
.\pmm-venv\Scripts\activate
git checkout nightly
git stash
git stash clear
git pull
python -m pip install -r requirements.txt
only once all those commands return without error... do I run PMM
where is the activate?
did you not create the pmm-venv?
looks like you are on a linux machine?
ok.. and not in a pmm-venv
Not sure what pmm-venv means
its using python3 native
that link has the exact step in our linux walkthrough for a local install
not sure if you did that step or not
I can do that, what benefit is this going to have?
as the page explains... ensures that there are no conflicts
This walkthrough is going to use a "virtual environment", since that provides a simple way to keep the requirements for a given thing self-contained; think of it as a "sandbox" for this script. It also provides a clean way to recover from mistakes, and keeps the host system clean.
so the commands would likely end up being:
cd Plex-Meta-Manager
source pmm-venv/bin/activate
git checkout nightly
git stash
git stash clear
git pull
python -m pip install -r requirements.txt
once the pmm-venv is created as per that step in the walkthrough
seems to work in the test environment. Should I run the install requirements command in the main directory for PMM?
you already tried that and it did not work. please run pmm from that pmm-venv prompt
python plex_meta_manager.py -r
and then after about 1 minute, drop the meta.log into here so we can see if that requirements.txt line is gone or not
📝 If you want to review this again, papertankz:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Version: 1.20.0-nightly24 (Python 3.10.12) (Git: nightly)
PlexAPI Version: 4.15.7
Platform: Linux-5.15.0-92-generic-x86_64-with-glibc2.35
Memory: 31 GB
Run Command: plex_meta_manager.py -r
The footer was empty/not found in meta2.log. Go see recommendations pages.
as of 2024-01-29 19:16:11
1.20.0
1.20.0-develop14
1.20.0-nightly24
Eureka!!!
not sure what yuo mean by main
the pmm-venv is a python virtual environment... that would still use your Plex-Meta-Manager folder
oh ok... you are not being dumb. I was pretty lost way back when I started as well...
So the requirements issue is gone it seems. Should I run python plex_meta_manager.py -r?
not in the test virtual environment
so please remember that when you run PMM, you should activate your pmm-venv
its not a test environment
it is your pmm-venv
you should always run pmm through that
cd Plex-Meta-Manager
source pmm-venv/bin/activate
git checkout nightly
git stash
git stash clear
git pull
python -m pip install -r requirements.txt```
running the above will always ensure that you have the latest nightly and all requirements installed and updated
then you would run python plex_meta_manager.py -r
alternatively... if you dont want any updates
source pmm-venv/bin/activate
python plex_meta_manager.py -r
Okay, its running now. I will check back on it in 30-60 mins.
Fingers crossed no more issues.
Thank you so much Bullmoose, MyPostingID, and Mr. Carrot.
yup.. just to ensure that e draw your attention tot he walkthrough and this is what I was trying to explain:
Yup, I am updating my nightly script for this
cd Plex-Meta-Manager
source pmm-venv/bin/activate
python plex_meta_manager.py -r
bingo
You can skip the activation [which often goes wrong in scripts] by doing:
cd Plex-Meta-Manager
pmm-venv/bin/python plex_meta_manager.py -r
Is what I have
That script of your does also assume that your current working directory when it runs will be some specific directory.
so kill line 2
Don't kill it.
I would make this script:
cd /home/papertankz/Plex-Meta-Manager
pmm-venv/bin/python plex_meta_manager.py -r
the first line makes sure it works wherever you happen to be [not just in /home/papertankz] and the second does the "activate and run" in one command.
Thanks Mr Carrot.. my unix is rusty
Appreciate it!
curious because i though the actual directory where plex-meta-manager was in is found in the root of his system... /
hang on... i missed the tilde
~
so that is his home directory
cool
Everything seems to be in perfect working order. Thank you again for all the effort, knowledge transfer, and patience. Greatly appreciate the help!