#Collections not updating

1 messages · Page 1 of 1 (latest)

next atlas
#

I have a slight issue:
It seems to be that my collections are not updating. Neither over night, nor when I try to trigger it manually. Could you check whether my yml is incorrect?
Thanks for your support.

📎 config.yml 📎 collections.yml
opal badgeBOT
#

Welcome @next atlas!

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.

opal badgeBOT
fiery meadow
#

Can you provide a log of this happening?

next atlas
#

Yes, give me a sec

weary badgerBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯\(ツ)/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Plex Meta Manager!
gritty birch
next atlas
opal badgeBOT
#

📝 If you want to review this again, incredibad91:
: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> 📝

fiery meadow
#

This issue:

| urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPSConnection object at 0x7f4d9dd4b250>: Failed to resolve 'letterboxd.comharakiri' ([Errno -2] Name or service not known) |

was fixed awhile ago in PMM nightly, but you're well behind. I'd suggest updating to 1.19.1, and if it still happens to most recent nightly.

next atlas
#

Thanks for finding it out! Sorry for the follow up: Could you tell me the easiest way to update PMM itself?

weary badgerBOT
#
Updating PMM

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.

Thanks for using Plex Meta Manager!
bronze jacinth
bronze jacinth