#Two -pmm: imdb?

1 messages ยท Page 1 of 1 (latest)

charred starBOT
#

Welcome @hearty ravine!

It looks like you have not yet completed #938455615741775902, this will allow us to help you quicker.

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.

hearty ravine
#

Everything else is sorting correctly, but Top is not showing up because PMM says it is set to false... which it is in the first instance.

charred starBOT
#

๐Ÿ“ If you want to review this again, katelibby_67058:
: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> ๐Ÿ“

#

๐Ÿ“ If you want to review this again, antwanchild:
: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> ๐Ÿ“

charred starBOT
# charred star
**Rec 01** - โŒ **ANIDB AUTH ERRORS**

โŒ ANIDB AUTH ERRORS
Plex Meta Manager uses AniDB settings to connect to AniDB.
This error indicates that the setting is not correctly setup in config.yml.
For more information on configuring AniDB, [https://www.metamanager.wiki/en/latest/config/anidb.html]
2 line(s) with ANIDB AUTH errors. Line number(s): 315, 317

charred starBOT
limber flume
#

would recommend following several of the recommendations from the bot

torpid archBOT
#

The Linuxserver.io image [linuxserver/plex-meta-manager] Is different to the official image [meisnate12/plex-meta-manager] in a few ways that cause problems.

The LSIO image only has latest, no develop or nightly. If you want to switch to develop or nightly to try a new feature, you can't with LSIO image.

It keeps the PMM files in a different place inside the image compared to official, so when you exec into it you can't just run PMM, you need to cd into another dir first.

It also resets ownership of the entire config dir every run. In tests, the ownership of the config dir and its contents was set to 911:911 with each run. The official image runs as root by default, and will set the ownership of the files it creates during that run to root if you don't specify a user, but lsio appears to reset the entire config tree rather than just a log file or two with every run.

Generally speaking, we suggest you use the official image instead of lsio. type !repo for more info

hearty ravine
#

Like I said, everything is running fine

#

I just want to change the sort order of the one embedded pmm, and I am not sure how to do it

#

I am just going to keep it turned off and build a separate 250 with an imdb builder

lapis hornet
#

strongly suggest you fix the following spacing in this section only... prepend 1 space per line that is "red":

charred starBOT
#

๐Ÿ“ If you want to review this again, bullmoose20:
: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> ๐Ÿ“

charred starBOT
# charred star
**User Info**

Author of Linked Message: Kate Libby
Person who Invoked the Command: bullmoose
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: Plex Configuration - Section 3
Page 08: Rec 01 - โŒ ANIDB AUTH ERRORS
Page 09: Rec 02 - โŒ๐Ÿ”’ BLANK API KEY ERROR
Page 10: Rec 03 - โŒ [ERROR]
Page 11: Rec 04 - โŒ๐Ÿ› ๏ธ INCOMPLETE LOGS
Page 12: Rec 05 - โŒ MY ANIME LIST CONNECTION ERROR
Page 13: Rec 06 - โŒโฐ PMM SCHEDULED TIME CONFLICT
Page 14: Rec 07 - โŒ PLEX LIBRARY ERROR
Page 15: Rec 08 - โŒ TRAKT CONNECTION ERROR
Page 16: Rec 09 - โš ๏ธ [WARNING]
Page 17: Rec 10 - โš ๏ธ๐Ÿ–ฅ๏ธ LINUXSERVER IMAGE DETECTED
Page 18: Rec 11 - ๐Ÿ’ฌ CONVERT ERROR
Page 19: Rec 12 - ๐Ÿ’ฌ๐Ÿ’ก๏ธ PLEX DB CACHE ADVICE
Page 20: Rec 13 - ๐Ÿ’ฌ๐ŸชŸ๐Ÿง WSL MEMORY RECOMMENDATION

hearty ravine
#

each of those needs an extra space eh?

lapis hornet
#

As Antwan mentioned, and the cakeybot also mentioned, you are not on an official image of PMM. The version you are running will limit you and have several idiosyncrasies.

lapis hornet
hearty ravine
#

How'd I manage the unofficial image?

lapis hornet
#

not sure where you got the image from

#

but nowhere in our wiki or walkthroughs do you use the lsio image

hearty ravine
#

I had a friend hlep me set it up, so I am afraid I don't know how to change the image

torpid archBOT
#

The Linuxserver.io image [linuxserver/plex-meta-manager] Is different to the official image [meisnate12/plex-meta-manager] in a few ways that cause problems.

The LSIO image only has latest, no develop or nightly. If you want to switch to develop or nightly to try a new feature, you can't with LSIO image.

It keeps the PMM files in a different place inside the image compared to official, so when you exec into it you can't just run PMM, you need to cd into another dir first.

It also resets ownership of the entire config dir every run. In tests, the ownership of the config dir and its contents was set to 911:911 with each run. The official image runs as root by default, and will set the ownership of the files it creates during that run to root if you don't specify a user, but lsio appears to reset the entire config tree rather than just a log file or two with every run.

Generally speaking, we suggest you use the official image instead of lsio. type !repo for more info

lapis hornet
#

literally replace the first line with the second line

#

you are running docker on windows

hearty ravine
#

correct

lapis hornet
#

so yeah... where you specified linuxserver/plex-meta-manager, replace that with meisnate12/plex-meta-manager

hearty ravine
#

is that in the docker compose or the config yml?

lapis hornet
#

docker compose

#

compose down

#

update stack

#

compose up

#

ummm

#

why is your pmm container called plex?

hearty ravine
#

shrug

lapis hornet
#

i think your friend copied and pasted stuff

hearty ravine
#

I am pretty sure he did

#

it works if that helps?

lapis hornet
#

i would change the container_name: pmm

#

is plex on the same machine?

#

please tell me your plex container_name is not pmm ๐Ÿ˜›

hearty ravine
#

oh sorry, that's the plex ms section

lapis hornet
#

i can only go by the screenshot you sahred.. I dont even know if that is before or after the edits

hearty ravine
#

That''s PMM

lapis hornet
#

change image:

hearty ravine
#

nightly?

lapis hornet
#

meisnate12/plex-meta-manager:develop

#

or meisnate12/plex-meta-manager:nightly

#

can you share your plex section again please?

hearty ravine
#

yep

lapis hornet
#

ok. good.. glad to see the plex image is back there

#

so update the stack

hearty ravine
#

yeah, I changed it when I thought it was PMM

lapis hornet
#

that will pull down the image from the official repo

hearty ravine
#

so I shut down the stack, and then restart it in the shell?

lapis hornet
#

and then compose up

#

i think the command from terminal is docker compose down

#

@limber flume you know the commands?

hearty ravine
#

I think I have it saved

lapis hornet
#

if you can share that here that would be great

hearty ravine
#

docker compose -f docker-compose.yml up -d

lapis hornet
#

that will bring it up

hearty ravine
#

so should I just shut everythign down from docker>?

lapis hornet
#

the command I hope you have is to update the stack

limber flume
#

docker-compose pull

lapis hornet
#

so the pull will update the stack... cool

limber flume
#

that's what i use

lapis hornet
#

do you need to take the stack down first?

hearty ravine
#

so I just have to run the pull?

limber flume
#

docker-compose up -d

#

pull will update any image that needs updating, then the up will recreate any container which was updated

hearty ravine
#

should I shut down everything in docker first?>

lapis hornet
#

no need

#

docker-compose pull

#

then docker-compose up -d

#

pretty sure that will ensure that your stacks are updated and that the containers are all up and started

#

so that will take you off of the lsio image.

#

excellenmt

hearty ravine
#

Thanks you two!!

#

Much appreciated.

lapis hornet
#

we're still not done... lol

hearty ravine
#

oh crap

#

lol

lapis hornet
#

well.. we never anwered your original question

hearty ravine
#

Oh, I think I figured a workaround

#

I just made a new YML file

#

that had the IMDB 250 in it

#

and sorted it

lapis hornet
#

can i ask why you seem to have all of our defaults, but now local?

hearty ravine
#

I think it's because my brain works that way

#

it's the way I am understanding the wiki and the code

limber flume
#

at this stage, coming from someone who has tried that, i'd recommend staying on the defaults

lapis hornet
#

you are making your life super complicated

#

And believe me Antwan tried that several times.

#

๐Ÿ™‚

hearty ravine
#

I don't actually think they are that complicated. I am not doing anything really complex

plush quail
#

What have you changed in, for example, this file?

    - file: config/!000_seasonal.yml
lapis hornet
#

this is where things get complicated

limber flume
#

right, but with the defaults and things change in pmm, they're updated with pmm, instead if you run your own files locally, you then have to go rebuild your local file. TRUST ME, i've been there

lapis hornet
#

Chaz asks the tough questions

hearty ravine
#

So, you're saying to try and work within the confines of the defaults so that as PMM updates I don't have to do anything

plush quail
limber flume
#

right, cause you can make minor changes with template_variables

hearty ravine
#

Well damn, I had everything almost the way I wanted lol, now I have to go back to the drawing board!

lapis hornet
#

no you don't have to go back tot he drawing board...

plush quail
#

Depending on how, specifically, your config/!000_seasonal.yml differs from the original default file, it may be very simple to accomplish.

limber flume
#

defaults make things 1000x easier, just sayin

lapis hornet
#

if you can share what you changed, we can probably assist

hearty ravine
#

So for example, here's my genres

plush quail
#

That's not a modification of the defaults.

#

THose are standalone collections.

hearty ravine
#

Right. But you're saying I should stay away from that right?

plush quail
#

That's fine. We're talking about the files you have that appear to be copies of the original defaults.

#

LIke the specific one I have asked about

hearty ravine
#

oh. That one I pulled from github

#

and it's a collection of lists

#

1 sec

plush quail
#

OK, let me ask a different question.

#

Your config lists a bunch of files that are named identically to the defaults, which is giving us the impression that you have copied the PMM default files and modified them.

Is that true in any case, or are all these random files you've found somewhere else?

hearty ravine
#

Oh, no, none of them are the defaults. I just simply named them that because it was convenient.

#

I got some from github, cobbled some together myself, etc.

plush quail
#

OK, then our concern is not an issue.

lapis hornet
#

ahhhh.... that threw me for a big loop

#

carry-on as they say

plush quail
#

You CAN, however, probably do those things by modifying the defaults.

hearty ravine
#

sorry y'all. I was just naming them that because it made sense to me because my nose is in the wiki a lot

hearty ravine
plush quail
#

it made sense to me because my nose is in the wiki a lot

This makes no sense to me. If you're looking at the wiki a lot, naming unrelated files the same as ones in the wiki would seem to me to be the confusing choice, since nothing the wiki says about seasonal will apply to yours. But, up to you.

limber flume
#

honestly that get's confusing for those trying to help when they see a redacted log file

hearty ravine
#

but this is what I made for the 250 imdb collection since I wasn't figuring out a way to split the 250 away from the popular in the default.

#

collections: "IMDb Top 250": imdb_chart: top_movies sort_title: "!099_imdb_top_250" visible_home: false visible_library: false collection_order: custom sync_mode: sync radarr_add_missing: true radarr_search: true radarr_ignore_cache: true sort_by: critic_rating.desc summary: "The 250 highest-rated movies according to IMDb." file_poster:

#

That way it's the same thing but I can scoot it around where I want

limber flume
#

like your genres file, and the first thing i see is "studios"

plush quail
hearty ravine
limber flume
# hearty ravine ??

look again at what you shared for genres, and the top of the file says "studio collections"

plush quail
hearty ravine
#

Oh, lol, yeah that was a left over. I haven't cleaned up some things yet.

#

But you're right @limber flume it makes for some confusing reading

lapis hornet
#

And earlier today, we were also talking about the defaults in general channel where we explicitly spoke about how that is ordered for defaults versus non-defaults... I was confused as heck because not once did you say that you are not using the defaults at all...

#

although to be fair.. now that i see your config file, you are using both

hearty ravine
#

Well, to be fair, I wasssss using the defaults for top and popular

lapis hornet
#

earlier, without seeing the config file or a meta.log... we were completely lost

hearty ravine
#

Yeah, my bad

lapis hornet
#

all good...

hearty ravine
#

context is my new mantra

lapis hornet
#

we did suggest to open a pmm-help and you did... so cheers to that

#

so... the other chalenge that we and others will have to help you is that we will never see what is in - file: lines

hearty ravine
#

Oh because the log won't catch that?

lapis hornet
#

the logs will give us clues only

#

the log does not expose what actuallly inside those files

#

and its not like the defaults where its open source and available on Github for all to see

#

but no worries

#

when we need it we will ask

limber flume
#

and having your files also named like that, giving us a box of apples and asking us what's wrong with your oranges

lapis hornet
#

at this poiont, asking questions in general may not be the best idea because most will not have a clue and posting a meta.log in the general channel is kinda spammy.

hearty ravine
#

I think @lapis hornet you should just come over, I will provide you beer and you can help me tweak the defaults to do the same as my files

lapis hornet
#

hahahahaha

#

spiced rum as its cold over here

hearty ravine
#

that's fine

#

I can do that

lapis hornet
#

a lot of people will leverage the defaults and seriously make it look very different without ever using one line of file in their config.yml file

#

#old-images

#

so its unique to you

hearty ravine
#

I can play around and see what I can do. I am sure it's simple things I am trying to do, just don't have the knowledge to do it yet

lapis hornet
#

its good.. you are learning

#

in any case, feel free to do another runa nd post the logs here

#

let luma review

#

yes.. at least we know from the name its not defaults

hearty ravine
#

Hey @bullmoose, you all suggested doing more defaults in my setup. So, I have been thinking. If I did a genre defaut, but still wanted to have Radarr pull in to Plex automatically, I would build a Radarr yml that contained all the imdb searches- or what not -that I wanted to use to manipulate Radarr. That way, I would still have everything sorted through the default and if eveyrthing went to hell it would only be 1 yml file to monkey with. I guess the only question is, is there a way to hide this hypothetical radarr.yml from library AND collections both?

lapis hornet
#

Not sure I follow. The defaults support the use of the arrs.

hearty ravine
#

I guess I am not sure how that default works then. It looks to me like pmm: genre just sorts plex without querying any outside source?

#

So this is what I am monkeying with rn. Wouldn't this just sort what's already in Plex?

lapis hornet
#

Yes. It pulls data from your Plex. Mass_update_genre can be used

hearty ravine
#

I think I am crap at explaining at what I am trying to do. So, what I want to do is I want to select certain genres to be updated via radarr from imdb automatically.

#

Like the popular list does

#

but for genres

#

Hence the lengthy yml genre file I made and showed you yesterday

limber flume
#

the popular list has nothing to do with genres

lapis hornet
#

I still am not clear on what the end result is or why?

#

You?

#

Like I don't understand the flow of data and what is trying to be attempted...

austere ridge
#

They want to dynamically create genre collections from their library and compare that against the most popular movies in that genre on imdb, and add the difference to radarr?

#

My best guess anyways

plush quail
#

In this case, there is nothing to send to radarr, since the genre default is looking at what you already have in Plex. All the "dynamic" defaults are like this. If you want to send things to radarr you have to start from an external source that will provide lists of things you don't already have.
Something like this is not a thing the default genre collections are designed to cover.

plush quail
#

If what you want is to send stuff from some imdb lists to radarr WITHOUT creating a collection:

collections:
  Send This Stuff To Radarr:
    imdb_list:
    - https://www.imdb.com/list/ls000094398/
    - https://www.imdb.com/list/ls057783436/
    - https://www.imdb.com/list/ls064427905/
    radarr_add_missing: true
    build_collection: false

Missing Items from those lists will be sent to Radarr, but no collection will be built.

hearty ravine
lapis hornet