sonic orioleBOT
Welcome @nimble dragon!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
sonic orioleBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
When trying to make a TMDb dynamic collection, I'm noticing that all of of my movies are showing No TMDb ID for Guid: plex://movie/<guid>. I do see that I connect to TMDb successfully in the logs, and if Ilook at the XML for a movie I can see it has a TMDb ID in the contents (i've attached an XML for kick-ass). I did try doing a full metadata refresh, but doesn't seem to have helped. Any insight is appreciated
reef shore
@nimble dragon what is the naming of an example movie? Sounds like items are not matched in plex.
reef shore
The name in Plex
Your file name
nimble dragon
/movies/Kick-Ass (2010)/Kick-Ass (2010) [HDTV-1080p].mkv
reef shore
Plex does have a recommended naming scheme. That does not match plex’s recommended naming scheme. And Kometa recommends TRaSH naming convention
nimble dragon
The plex agent doesn't have any issue identifyting the movie though
reef shore
If you go to your library and show all unmatched what do you see?
slate birch
Can you provide the full log file, not whatever this is?
rigid plankBOT
Thanks for using Kometa
nimble dragon
I did provide the full log file
Oh no I didn't, one moment
@reef shore no matches for "unmatched"
reef shore
<@1012477002328064070> no matches for "unmatched"
Ok. Just was curious
nimble dragon
Can you provide the full log file, not whatever this is?
I cleared the meta.log, rerunning now to generate a new one
For reference, what I provided is the terminal output
reef shore
For reference, what I provided is the terminal output
But your Kometa log folder has 10 logs
nimble dragon
Runs take about 10 minutes, will provide a fresh valid log from the logs folder once it's done
I lied, 3 mintues this time lol
reef shore
Looks like you have a server error and plex does not like the image size. So that will kill it. Or at least that portion of your run
And also wouldn’t recommend keeping cache set to false
nimble dragon
I run my setup a little strange as a kubernetes cronjob, I'm ok with cache false for now
The plex image size is for a single entry, glad to kow what's has been wrong there, but it doesn't look to stop processing that section
slate birch
With no cache, it could be that when attempting to build the dynamic collections [which happens prior to updating the cache db], there is no cached lookup data to leverage, resulting in this "no TMDB ID" error.
That's just a guess based on the symptom.
nimble dragon
Alright, one moment, let me try turning it on and running it twice more
Once with cache enabled to populate cache, a second time to utilize the cache
Weiiiird, that looks to be fixing it, already seeing tmdb ID's populated on the first run through
Gonna wait until it's done just to validate
Eyyy, it's working now! Thanks, I'll look at making sure I keep my cache around as well. Appreciate all the help!
