#PMM doesnt find all ID's from mdblist

1 messages Β· Page 1 of 1 (latest)

fossil zinc
#

So I have this list with 672 items in it: https://mdblist.com/lists/deniax/romantic-trending
But for some reason, only 289 are picked up/identified:

[2023-12-04 15:27:18,025] [plex_meta_manager.py:703]  [INFO]     |                                                                                                    |
[2023-12-04 15:27:18,025] [mdblist.py:182]            [INFO]     | Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending                    |
[2023-12-04 15:27:18,025] [mdblist.py:183]            [INFO]     | Sort By: rank.asc                                                                                  |
[2023-12-04 15:27:18,059] [builder.py:1939]           [DEBUG]    |                                                                                                    |
[2023-12-04 15:27:18,059] [builder.py:1940]           [DEBUG]    | 289 IDs Found ```

An example movie that is missing, is for example Christmas Under Wraps with themoviedbID 299584 , which is both a valid number and is visible in the above list, but not picked up by PMM? 
I already tried to remove the cache file, but to no avail.

Probably Im overlooking something, but I dont know what πŸ™‚
mdblist.com

Create your own dynamic Trakt.tv list using multiple ratings and keywords

uncut owlBOT
#

Welcome @fossil zinc!

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.

fossil zinc
uncut owlBOT
#

πŸ“ 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> πŸ“

uncut owlBOT
# uncut owl
**PMM Info**
PMM Header

Version: 1.19.1 (Linuxserver)
PlexAPI library version: 4.15.2
Platform: Linux-6.1.49-Unraid-x86_64-with
Memory: 126 GB

Run Command: /app/pmm/plex_meta_manager.py --run --config /config/config.yml

PMM Footer

Finished Run
Version: 1.19.1
Finished: 15:35:49 2023-12-04 Run Time: 0:09:06

Available PMM Versions

as of 2023-12-04 17:18:27

PMM Version (Master branch)

1.19.1

PMM Version (Develop branch)

1.19.1-develop33

PMM Version (Nightly branch)

1.19.1-nightly39

uncut owlBOT
pure zodiacBOT
#

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

eager shoal
#

I put in a little extra logging to see where the missing movies may have been dropped, and I cannot reproduce it.

|============================= Validating Romance Collection Attributes 
|                                                                       
| Looking for: Romance Collection                                       
|                                                                       
| Validating Method: sync_mode                                          
| Value: sync                                                           
|                                                                       
| Validating Method: collection_order                                   
| Value: random                                                         
|                                                                       
| Validating Method: mdblist_list                                       
| Value: {'url': 'https://mdblist.com/lists/deniax/romantic-trending', 'limit': 0, 'sort_by': 'rank.asc'} |
|                                                                       
| Validating Method: sort_title                                         
| Value: *104                                                           
|                                                                       
| Validating Method: radarr_add_missing                                 
| Value: False                                                          
| Collection Error: radarr_add_missing requires Radarr to be configured 
|                                                                       
| Validating Method: url_poster                                         
| Value: https://theposterdb.com/api/assets/69221                       
|                                                                       
| Validation Successful                                                 
|                                                                       
|============================== Running Romance Collection Collection 
|                                                                     
| Sync Mode: sync                                                     
|                                                                     
| Builder: mdblist_list: {'url': 'https://mdblist.com/lists/deniax/romantic-trending', 'limit': 0, 'sort_by': 'rank.asc'} |
|                                                                     
| mdblist_list: getting tmdb_ids from {'url': 'https://mdblist.com/lists/deniax/romantic-trending', 'limit': 0, 'sort_by': 'rank.asc'} |
| Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending
| Sort By: rank.asc                                                              
| returning 672 of 672                                                           
|                                                                                
| 672 IDs Found                                                                  
|                                                                                
| Parsing ID 42/672
#

My collection definition looks like this:

collections:
  Romance Collection:
    mdblist_list:
      url: https://mdblist.com/lists/deniax/romantic-trending
      limit: 0
      sort_by: rank.asc
    sync_mode: sync
    collection_order: random
    sort_title: "*104"
    radarr_add_missing: False
    url_poster: https://theposterdb.com/api/assets/69221                                
fossil zinc
#

I will try to get a different container then the linuxserver one and try again

eager shoal
#

About the only places the list would be shortened that I can see are:

  1. mdblist only returned a list of 289
  2. 383 of the 672 things returned weren't identified as either "movie" or "show"

I had added logging to identify those 383 things.

simple ingot
eager shoal
#

had you recently added 383 things? Perhaps the mdblist API was still returning 289?

fossil zinc
#

Bullmoose: ok will do. MrCarrot, maybe, I did actually selected a wrong filter on that collection causing mdblist to show only 1 result. I corrected that, and then for an hour was trying to get pmm pickup all entries there. I will try with a "fresh" non linuxserver docker on the develop branch and see what happens

fossil zinc
#

So seems it works, altough with a small but πŸ™‚
I installed the develop branch, but I did not remove the cache file. And then it told it found only 1 ID.
I deleted the cache and now it seems all is ok. (Note that with the stable version I also tried to delete the cache file, but it didnt work)

So I'm not sure if it was due to the API giving wrong results, the non-linuxserver version, or sometrhing else, but for now it works πŸ™‚

[2023-12-04 19:40:41,638] [plex_meta_manager.py:703]  [DEBUG]    |                                                                                                    |
[2023-12-04 19:40:41,638] [plex_meta_manager.py:704]  [DEBUG]    | Builder: mdblist_list: {'url': 'https://mdblist.com/lists/deniax/romantic-trending', 'limit': 0, 'sort_by': 'rank.asc'} |
[2023-12-04 19:40:41,638] [plex_meta_manager.py:705]  [INFO]     |                                                                                                    |
[2023-12-04 19:40:41,638] [mdblist.py:182]            [INFO]     | Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending                    |
[2023-12-04 19:40:41,638] [mdblist.py:183]            [INFO]     | Sort By: rank.asc                                                                                  |
[2023-12-04 19:40:41,804] [builder.py:1928]           [DEBUG]    |                                                                                                    |
[2023-12-04 19:40:41,804] [builder.py:1929]           [DEBUG]    | 672 IDs Found ```
simple ingot
#

Nice. When that finishes, feel free to drop your meta.log in here and review the luma logscan recommendations

fossil zinc
uncut owlBOT
#

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

#
**User Info**

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 - πŸ’₯ BAD PLEX VERSION ERROR
Page 09: Rec 02 - ❌ [ERROR]
Page 10: Rec 03 - ⚠️ [WARNING]
Page 11: Rec 04 - πŸ’¬ LEGACY SCHEMA DETECTED
Page 12: Rec 05 - πŸ’₯ INTERNAL SERVER ERROR
Page 13: Rec 06 - ❌ METADATA LOAD ERRORS
Page 14: Rec 07 - πŸ’¬ LEGACY SCHEMA DETECTED
Page 15: Rec 08 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 16: Rec 09 - πŸ’‘οΈ PLEX DB CACHE ADVICE

eager shoal
#

Not sure why you're doing this:

|     - file: config/metadata/seasonal.yml

but it's causing a variety of problems.

The 500 errors you're seeing are because you're on 1.32.7

fossil zinc
#

hehe just 1 min ago I added - pmm: seasonal to the config . The config file is really old. Im going through the errors/warning now

#

Concerning the 1.32.7 problem, according to Plex they will not "fix" the issue that is causing the 500 errors? (kinda offtopic)

#

Thanks for the support , appriciate it!

eager shoal
#

It's fixed in 1.32.8; where did they said they wouldn't fix it?

#

It doesn't occur in 1.32.6, regression in 1.32.7, fixed in 1.32.8

fossil zinc
#

Ah, I misread their reply in that thread. Ok, good to know! Thanks again Mr Carrot, all is woking now, the rest of the debugging should be just going through the logs!

eager shoal
#

They didn't reset the testing clock to get it into 1.32.7

fossil zinc
#

Hmm, Im playing around to remove all errors, so I need to run PMM a lot, but now again the original problem is back that sometimes its getting wrong results from mdblist:

[2023-12-04 20:55:44,761] [plex_meta_manager.py:705]  [INFO]     |                                                                                                    |
[2023-12-04 20:55:44,761] [mdblist.py:182]            [INFO]     | Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending                    |
[2023-12-04 20:55:44,761] [mdblist.py:183]            [INFO]     | Sort By: rank.asc                                                                                  |
[2023-12-04 20:55:44,772] [builder.py:1928]           [DEBUG]    |                                                                                                    |
[2023-12-04 20:55:44,772] [builder.py:1929]           [DEBUG]    | 1 IDs Found```
uncut owlBOT
#

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

eager shoal
#

let me try again

#

No change:

| Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending
| Sort By: rank.asc
| returning 672 of 672
|
| 672 IDs Found
fossil zinc
#

I will delete cache file again, as all the other I did (develop branch, non Linuxserver) and check what happens

#

No, still " 1 IDs Found " 😦 So if you tried twice/3 times and every time you get the 672 ID's , then clearly its something in my config files.
So this is how I create it, which is afaik how it should be?

  Romance Collection:
    mdblist_list: 
      url: https://mdblist.com/lists/deniax/romantic-trending
    collection_order: random
    sync_mode: sync
    sort_title: "*104"
    radarr_add_missing: false
    url_poster: https://theposterdb.com/api/assets/69221```
eager shoal
#

Mine looks like this:

collections:
  Romance Collection:
    mdblist_list:
      url: https://mdblist.com/lists/deniax/romantic-trending
      limit: 0
      sort_by: rank.asc
    sync_mode: sync
    collection_order: random
    sort_title: "*104"
    radarr_add_missing: False
    url_poster: https://theposterdb.com/api/assets/69221                                

I didn't notice I was setting a limit of 0, which must get interpreted as "no limit"

I just copy-pasted from the log to build it.

fossil zinc
#

I just copy-pasted your config, just to try it, but:

[2023-12-04 21:35:37,652] [plex_meta_manager.py:705]  [INFO]     |                                                                                                    |
[2023-12-04 21:35:37,652] [mdblist.py:182]            [INFO]     | Processing Mdblist.com List: https://mdblist.com/lists/deniax/romantic-trending                    |
[2023-12-04 21:35:37,652] [mdblist.py:183]            [INFO]     | Sort By: rank.asc                                                                                  |
[2023-12-04 21:35:37,666] [builder.py:1928]           [DEBUG]    |                                                                                                    |
[2023-12-04 21:35:37,666] [builder.py:1929]           [DEBUG]    | 289 IDs Found     ```

Its so random, why 289 now....:D 
I will now just try to create a whole new list, but then on Trakt, and see if that can solve the problem. Its extremely weird
eager shoal
#

Yeah, for me it's been absolutely consistent 672 every run.

fossil zinc
#

Seems moving to traktlist, solved my issue. All 672 items found πŸ™‚
Still weird though, but Im happy it works!

[2023-12-04 21:46:13,955] [plex_meta_manager.py:703]  [DEBUG]    |                                                                                                    |
[2023-12-04 21:46:13,955] [plex_meta_manager.py:704]  [DEBUG]    | Builder: trakt_list: https://trakt.tv/users/deniax/lists/romantic-trending?sort=rank,asc           |
[2023-12-04 21:46:13,955] [plex_meta_manager.py:705]  [INFO]     |                                                                                                    |
[2023-12-04 21:46:13,955] [trakt.py:495]              [INFO]     | Processing Trakt List: https://trakt.tv/users/deniax/lists/romantic-trending?sort=rank,asc         |
[2023-12-04 21:46:14,405] [builder.py:1928]           [DEBUG]    |                                                                                                    |
[2023-12-04 21:46:14,405] [builder.py:1929]           [DEBUG]    | 672 IDs Found```

Thanks again Mr Carrot for your time!
eager shoal
#

Anything further needed here?