Collection tmd status will randomly error. Next run will fix it. Errors attached. Theres nothing different between the two runs, it just error out randomly
#Certain collection will error out in random runs
restive dust
shell hullBOT
Welcome @restive dust!
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.
shell hullBOT
shell hullBOT
shell hullBOT
ruby dirge
We will need a log showing it working and a log showing it failing.
Also, what is a "status collection"? Which specific collections are you talking about and what precisely does "error out" actually mean?
restive dust
Also, what is a "status collection"? Which specific collections are you talking...
its the upcoming movie tv show and tv show status collection
heres a working log, which basically the exact same thing with no changes from me but it just works
shell hullBOT
ruby dirge
Which collections am I looking for? What do "error out" and "just works" mean?
restive dust
Which collections am I looking for? What do "error out" and "just works" mean?
file: config/tssk/TSSK_TV_ENDED_OVERLAYS.yml
so errors out i mean this happens attached
just work i mean its processed finr with no errors
ruby dirge
There are no collection-related errors in either of these logs.
There are a few errors that differ between the two logs:
This is the error in your screenshot. TMDB is returning a 404 error when Kometa apparently asks for season information. Kometa has no control over that; it's entirely on TMDB's side. It's happening when attempting to apply an overlay. Happens on 2/3, not on 2/2.
| 6 | Unknown Error: (404 [Not Found]) Requested Item Not Found - overlay problem, issue on TMDB side
This error differs in that it happens one fewer time on 2/3 than 2/2. This happens while setting ratings or the like.
| 5 | MDBList Error: Not Found
| (37/960) Scarpetta
| (229/960) Cunk on Earth
| (391/960) Home Before Dark
| (508/960) Madison
| (784/960) Spartacus: House of Ashur
| 4 | MDBList Error: Not Found
| (37/960) Scarpetta
| (392/960) Home Before Dark
| (509/960) Madison
| (785/960) Spartacus: House of Ashur
Same sort of thing here, but four times on 2/3, three time on 2/2. This is while processing metadata files.
| 3 | Metadata File Error: TVDb ID not mapped
| TVDb ID Mapping: 73141
| TVDb ID Mapping: 75978
| TVDb ID Mapping: 368207
| 4 | Metadata File Error: TVDb ID not mapped
| TVDb ID Mapping: 73141
| TVDb ID Mapping: 75978
| TVDb ID Mapping: 352408
| TVDb ID Mapping: 368207
The common errors are all not collection-related, either.
restive dust
thx mate, i will pass it by the dev of the tool
ruby dirge
Nobody but TMDB can address intermittent 404 from TMDB on the same request at different times.
I am assuming that none of these files changed between 2/2 and 2/3
inland remnant
@restive dust you're alking about overlays, not collections.
It's a simple overlay file to apply an overlay based on tmdb_status
No idea why it 404 on you one run and not the next.
I use the same overlay file without issues
restive dust
<@819643994031652914> you're alking about overlays, not collections.
It's a si...
yea but i thought the error is due to the collevtion the overlays connect to, apologies for the confusion
i went to the last 10 meta logs, it failed in 3 and passed 7, again i had zero interaction with it
inland remnant
no, it has nothing to do with collections
it just looks for
plex_all: true
filters:
tmdb_status: ended
That 404 error has nothing to do with collections; it's occurring during an attempted to connection to TMDB.
There's a different error that is caused by a label that doesn't exist:
| Plex Error: label: RequestNeeded not found
Perhaps that's a collection.
inland remnant
not sure why it would be looking for season details. the overlay is applied on show level
inland remnant
There's a different error that is caused by a label that doesn't exist:
```
| Pl...
yea that's not the issue they're talking about. (@Iomar: that one we can easily fix)
ruby dirge
Just suggesting that as a possible reason that collections came up.
inland remnant
right yea perhaps
thats why I stepped in cause things are being mixed up here
Iomar is talking about the overlay file that applies an overlay based on tmdb status: on show level
on most runs it processes without issues
but some runs it 404s resulting in the overlays to be removed
ruby dirge
The check for seasons is part of the routine initialization code behind creating a TMDbShow object:
| return TMDbShow(self, tmdb_id, ignore_cache=ignore_cache)
Not conditionalized at all; always happens.
FWIW
inland remnant
right. well I got no idea why the 404 would happen for them..sometimes
ruby dirge
Something on the TMDB side, I imagine. Runs performed with --log-requests would show the actual request being sent, which would show if the request is changing for some reason on the Kometa side.
orchid saffronBOT
antwanchild used !aenh
@restive dust, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.