#TMDB v TVDB but both exist and have for a month
1 messages ยท Page 1 of 1 (latest)
Welcome @stone jolt!
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.
๐ If you want to review this again, keatingfish:
: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> ๐
โ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that Kometa did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
1 line(s) with [ERROR] messages. Line number(s): 16247
A 500 Internal Server Error happens when the server has an unexpected error when responding to an API request.
Effectively Plex is saying "Something went wrong, but no developer foresaw it to add error handling and no tester ran into it to make error handling get added, so all I can say is 'the bad thing happened'"
There could be any number of reasons why this happens and it depends on what server Kometa is talking to although its most likely coming from your Plex Server.
Most of the time these errors need to be resolved by changing something specific to your set up but some do come up that can be fixed (i.e. Plex throws one if you upload a photo larger then 10 MB)
Many Appbox Setups will throw this error when too many requests are sent
Take a look at the following logs:
1๏ธโฃ Settings | Manage | Console -> then filter on Error and Warning to see what might be going on
2๏ธโฃ Check the plex logs (container or other) for the "Busy DB Sleeping for 200ms)
@stone jolt not much Kometa can do about the 500 error
just using this to see why the erorr is happening
i dont get the 500 error though
im running kometa on the actual box
oh
500 error to the movie db right?
yeah makes sense.
its trying to hit themoviedb to check returning/airing
and moviedb must be down on the api or something
I was like I never changed anything lol ๐ :P)
(500) internal_server_error; (redacted)/library/metadata/118587/posters <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html>
thats what the critical summary says
i know what the message says. LOL. i'm reading the log
have you recently changed a poster?
I removed some items from plex
thats about it
but i dont know why id get a 500 error for that
the movie part goes through fine
only on tv and only after the returning overlay is ran
does it die
oh boy.
no clue how im going to find that
is there a detailed log I can enable
i dont see what it could be though
i haven't added any new tv shows
since yesterday when it worked fine
I also haven't modified any tv posters
in your /config/overlays, do you have a tv original posters directory or something like it
ok never mind
just looked over all my tv show posters and none are even at 2mb
there really is not for for anyone, except maybe plex, to know what happened
yeah but why can't i get a log that shows where it broke
that would let me narrow it to the show at least
maybe the plex log might have some info for you
instead Kometa just errors out and spits nothing
I cant even check the last one that went through fine
the error came from plex, not Kometa. Basically this is Kometa making a request to Plex and then something explodes inside plex. There isn't anything Kometa can do about it. possibly a database issue
Kometa is making a request to Plex, and something explodes inside Plex, so Plex returns a 500.
Kometa has no way to know what happened inside Plex.
I understand that piece of it.
Perhaps the Plex log around that time has something to say.
There's no way from a Kometa log to have it show the last file that went through without a 500 though
cuz then i could easily find where the break is
since it does them alphabetically
it may not be a file issue. it may just been something else in plex that exploded
alright rerunning with console in plex active
You could enable log-requests or perhaps trace logging; they might shed some light.
definitely something voer 10mb
but plex doesnt even tell me what
damn it
118587
wait i should be able to xml that
weird. what if poster is breaking it
but didnt break it yesterdaay
lol
so its in the overlay section also @fair raven so could it be an overlay issue. If so, was there a way to remove all overlays then reapply?
only overlay i use is returning/airing btw.
ok the 500 is gone but i still get Unknown Error: (404 [Not Found]) Requested Item Not Found
๐ If you want to review this again, keatingfish:
: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> ๐
โ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that Kometa did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
1 line(s) with [ERROR] messages. Line number(s): 16247
yeah cant figure out the 404 not found error that I have now
still in the returning overlay section
related to what if. so I just need to figure out how to remove that overlay from all shows, then I can rerun with my normal config
you could run with --log-requests and see what you get?
I think i figured it out
I had to do a plex dance on the tv show
and then modify out the poster
but now its erroring cuz the overlay is gone
or the label for the overlay
so just trying to figure out how to remove it via kometa
so I can re-add it again
also i think the reason it didn't break prior was that the What If show just got flagged as returning
so it was trying to add an overlay and that pushed it over the 10mb
i just cant figure out how to fix that overlay error now
do you use assets?
do you set posters in plex, or how do you set posters?
So I throw the poster into the asset folder for Kometa then run Kometa
the posters load fine
then for TV, I use the returning/airing overlay only.
that is literally what i just asked you
Sorry got off work and my brain is still on medical spreadsheet stuff
So what happened I think is.
What if got marked as returning in tmdb
right, so if you have the poster in the asset folder, Kometa should reapply it
and it pushed the poster over the top
so I had to them modify the poster and I just overwrote what was in the asset folder
so then find a different poster
the poster is only 400kb now
but now its erroring on the overlay
saying it can't find anything
how is it erroring?
Unknown Error: (404 [Not Found]) Requested Item Not Found
its trying to do the overlay piece and dies on the what if show
in plex that show has no label assigned to it
and no overlay now
because of my poster fix
so Kometa thinks it has an overlay? but isn't finding it? just not sure how to fix the error since I plex danced, and changed posters
kometa doesn't think it has an overlay because the label isn't there
wiped out the kometa asset folder for the show
to see if it will jus auto gen a blank one
in plex, empty trash, optimize and clean bundles
ok did all 3
also wiped out the show folder in assets
re-running
still giving me a 404 error
it did generate the assets folder again though
let me add posters back in and re-run
404 is probably tmdb
๐ If you want to review this again, keatingfish:
: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> ๐
โ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that Kometa did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
1 line(s) with [ERROR] messages. Line number(s): 16247
you could run with trace logging
kometa right?
yes
si
spits it out in the log folder i assume
also appreciate this. first actual big error ive faced since initial setup
yeah just a requested item not found
hmmm
but i just checked the show, my folder, my ids, plex, and tmdb and they align
๐ If you want to review this again, keatingfish:
: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> ๐
Author of Linked Message: Keating
Person who Invoked the Command: Keating
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation โ
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - โ [ERROR]
what if you delete your cache file
kometa cache right? config.cache?
yes
re-running ๐
ok all posters a-ok, overlay time
76238 tvdb id
no tmdb id found
time to find out what that is
the hunger. ah
so that doesnt make sense
cuz the tmdb id for The Hunger has the tvdb id in it
hasn't been touched in a month
Convert Warning: No TMDb ID Found for TVDb ID: 76238 is the new error
Convert Error: No TVDb ID Found for TMDb ID: 15733
Convert Error: No TMDb ID Found for IMDb ID: tt14431252
These sorts of errors indicate that the thing can't be cross-referenced between sites. For example, at the time of that error, the TMDB record for "The Two Mrs. Grenvilles" [ID 15733] didn't contain a TVDB ID. This could be because the record just hasn't been updated, or because "The Two Mrs. Grenvilles" isn't listed on TVDB.
The fix is for someone [like you, perhaps] to go to the relevant site and fill in the missing data.
and last update May for TMDB, and May for TVDB also
and its still not applying an overlay to what if
sigh
why no overlay?
I have no idea anymore.
No clue why The Hunger is saying it can't find the TMDB ID from the TVDB ID when both are there and have been for a month
no clue why What If is broke, so just deleting it since I'll never watch anyways.lol
and still getting the 404
its basically breaking on returning
cuz im getting 0 returning overlays but all my airing are hitting
๐ If you want to review this again, keatingfish:
: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> ๐
๐ฌ CONVERT WARNING
Convert Warning: No * ID Found for * ID.
These sorts of errors indicate that the thing can't be cross-referenced between sites. For example:
Convert Warning: No TVDb ID Found for TMDb ID: 15733
In the above scenario, the TMDB record for The Two Mrs. Grenvilles ID 15733 didn't contain a TVDB ID. This could be because the record just hasn't been updated, or because The Two Mrs. Grenvilles isn't listed on TVDB.
The fix is for someone like you, perhaps to go to the relevant site and fill in the missing data.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/#warning]
1 line(s) with Convert Warnings. Line number(s): 16303
I have no idea why its broken at this point at all.
The Hunger one shouldn't be broke cuz the IDs exist.
and have for a month.
And the returning overlays being broke I have no clue now
ive completely removed the what if show that started all this
from plex/etc and did a cache delete again, and those 2 things still happen
TMDB v TVDB but both exist and have for a month
**...... setting this up from scratch for assistance because of the ebbs and flows.... Disregard all above involving What If or the 500 error **
- deleted config.cache
- cleared plex trash, optimized db, cleaned bundles
- ran kometa
Error 1) No returning overlays are being added as it pops a 404 error
Error 2) No TMDB for TVDB even though TVDB has the proper ID and no updates in a month, and TMDB has the proper TVDB ID for show and no updates in a month
and heres the log based upon this
๐ If you want to review this again, keatingfish:
: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> ๐
the returning overlay error might be related to the TVDB/TMDB error as that one appears right before the script break
im running kometa on What if and what if only
I already deleted what if out totally @keen ember
everything is broke around This Hunger show
you deleted it after i started my run
even though its in both TMDB and TVDB properly
No clue how to solve returning overlays being broke now.
all the airing went through fine. all posters were added fine. Something is breaking returning and with my limited knowledge
| |
| Collection Filter tmdb_status: ['returning'] |
| |
| Builder: plex_all: show |
| |
| Processing Plex All Shows |
| Loading All Shows from Library: TV Shows |
| Loaded 318 Shows |
| |
| 318 IDs Found |
| |
| Convert Warning: No TMDb ID Found for TVDb ID: 76238 |
| Traceback (most recent call last): |
| File "/modules/overlays.py", line 569, in compile_overlays |
| builder.filter_and_save_items(builder.gather_ids(method, value)) |
all I can think of is its The Hunger for some reason?
cuz thats right in front of the python script dying
I have one of the simpler setups too. just run posters and do 2 overlays
For the Convert Warning - Here are screenshots showing that there are IDs unless that warning is a Plex specific one
going to sleep, but hopeful someone can provide some insight into this tomorrow as my educated guess is something with The Hunger is breaking returning overlays but not sure why or how, esp when its an ended show.
the issue isn't the hunger
ignore that it's the same poster, but it isn't What if either. and i didn't get a 404 error on my run with either of those shows
what would cause the convert error for The Hunger then
and what could be causing the 404
The only thing I have done is remove What If from my plex library completely. Other than that, Sonarr has just added a few episodes of other shows in
I haven't added any new shows, and it was working as intended a couple days ago.
its only on the returning shows piece too
all the airing stuff runs through and passes and gets added if it is airing
next, try to run with --log-requests
on it
ok still got the " No TMDb ID Found for TVDb ID: 76238" error. checking log to see where it died for the 404
477510 is the tmdb id right
so its after wandavision
but i cant figure out what the 477510 is for
warehouse 13 is the new show after wanda now and thats not its id. hmmm
let me check through some others
{"success":false,"status_code":34,"status_message":"The resource you requested could not be found."}
so for some reason its finding something that TMDB doesnt have but I have never had this error prior and it ran fine . hmmmm.
Just checked all my W tv shows and none have that ID
does Kometa track what show it is using to call themoviedb at all
Based on the log it goes alphabetical, so after Wanda for me is now Warehouse 13, but it doesn't have that ID, and then I checked the other 12 shows I have after Wanda and the same
based on how the log works, Warehouse 13 would hvae to be the issue
speaking of let me up that one
๐ If you want to review this again, keatingfish:
: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> ๐
Author of Linked Message: Keating
Person who Invoked the Command: Keating
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation โ
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - โ [ERROR]
Page 08: Rec 02 - โ ๏ธ CHECKFILES=1 DETECTED
Page 09: Rec 03 - ๐ฌ CONVERT WARNING
so even if in my config I put that 477510 in the ignore_ids field, it still errors out with a 404 for that id
hmmm
I have no clue at this point at all. Its right after Wandavision, only on returning overlay. When I check Warehouse 13 it all seems fine.
477510 is non existent on tmdb outside a dog days movie whatever that is.
this is what I dont get though
if I look at the Wandavision piece
it has a 477510 id or something shoved in there
then the wandavision stuff
then it requests 477510 and died
but that 477510 is not attached to wanda either hmm
where do you see the 477510 for wandavision?
in the meta log. let me pull that specific area
so for example this is right above Wandavision
Use this simple tool that performs copy and paste functions. Copy several texts or favorite items and share privately with others. Get started for free now.
that is Walking Dead World Beyond or whatever
now.. the next one is Wandavision and you'll see that 477510 inside before it gets to the req
Use this simple tool that performs copy and paste functions. Copy several texts or favorite items and share privately with others. Get started for free now.
unf that paste tool sucked. im sorry
but this is The Walking Dead
[2024-06-11 19:26:52,921] [api3.py:67] [DEBUG] | Request Params: {'api_key': '94d8dbd5cdbe02acb0181573229cbbc0', 'language': 'en', 'append_to_response': 'external_ids,keywords'} |
[2024-06-11 19:26:52,942] [connectionpool.py:549] [DEBUG] | https://api.themoviedb.org:443 "GET /3/tv/94305?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1" 200 None |
then it goes into finding the show info/etc
[2024-06-11 19:26:52,942] [api3.py:82] [DEBUG] | Response (200 [OK]) {'adult': False, 'backdrop_path': '/hS0IN656SbRe23TyH0PdaGytIuL.jpg', 'created_by': [{'id': 205379, 'credit_id': '5d98d2fcb04605002242d7d3', 'name': 'Scott M. Gimple', 'original_name': 'Scott M. Gimple', 'gender': 2, 'profile_path': '/3i8X7w3B38ZM1xqrFwjV7sIUkr3.jpg'}, {'id': 1215721, 'credit_id': '5e9474687a97ab00170f1bf9', 'name': 'Matthew Negrete', 'original_name': 'Matthew Negrete', 'gender': 2, 'profile_path': None}], 'episode_run_time': [43], 'first_air_date': '2020-10-04', 'genres': [{'id': 18, 'name': 'Drama'}, {'id': 10765, 'name': 'Sci-Fi & Fantasy'}, {'id': 9648, 'name': 'Mystery'}], 'homepage': 'https://www.amc.com/twdu/the-walking-dead-world-beyond', 'id': 94305, 'in_production': False, 'languages': ['en', 'es'], 'last_air_date': '2021-12-05', 'last_episode_to_air': {'id': 3240170, 'overview': 'The remaining members of the group fight back enemies, both living and dead, on their quest to save the future.', 'name': 'The Last Light', 'vote_average': 7.3, 'vote_count': 3, 'air_date': '2021-12-05', 'episode_number': 10, 'episode_type': 'finale', 'production_code': '', 'runtime': 53, 'season_number': 2, 'show_id': 94305, 'still_path': '/qN5QA6BHuRuUBGoyXIUmPIt026o.jpg'}, 'name': 'The Walking Dead:
doesnt seem like an issue
however here is wandavision
[2024-06-11 19:26:52,943] [api3.py:67] [DEBUG] | Request Params: {'api_key': '94d8dbd5cdbe02acb0181573229cbbc0', 'language': 'en', 'append_to_response': 'external_ids,keywords'} |
[2024-06-11 19:26:52,964] [connectionpool.py:549] [DEBUG] | https://api.themoviedb.org:443 "GET /3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1" 200 None |
and then this happens and thats where the 477510 comes in and the dog days shit
[2024-06-11 19:26:52,964] [api3.py:82] [DEBUG] | Response (200 [OK]) {'id': **477510**, 'results': [{'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': **'DOG DAYS | Official Trailer'**, 'key': 'fAfqqHwgI1U', 'published_at': '2018-06-13T12:59:58.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Trailer', 'official': False, 'id': '5b2e43e50e0a2657ea004c3b'}, {'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Teaser', 'key': 'zA_khn8cuq0', 'published_at': '2018-05-09T13:59:53.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Teaser', 'official': False, 'id': '5b2e43f6c3a368533b004e0d'}], 'keywords': {'adult': False, 'backdrop_path': '/1i1N0AVRb54H6ZFPDTwbo9MLxSF.jpg', 'created_by': [{'id': 123132, 'credit_id': '600b066223d278003d3720ef', 'name': 'Jac Schaeffer', 'original_name': 'Jac Schaeffer', 'gender': 1, 'profile_path': '/u5RGA1m3XGXlRdXzexYbqYZAKcP.jpg'}], 'episode_run_time': [], 'first_air_date': '2021-01-15', 'genres': [{'id': 10765, 'name': 'Sci-Fi & Fantasy'}, {'id': 9648, 'name': 'Mystery'}, {'id': 18, 'name': 'Drama'}], 'homepage': 'https://www.disneyplus.com/series/wandavision/4SrN28ZjDLwH', 'in_production': False, 'languages': ['en'], 'last_air_date': '2021-03-05', 'last_episode_to_air': {'id': 2724621, 'overview': 'The events of WandaVision come to a head, and the destinies of all who took part are determined.', 'name': 'The Series Finale', 'vote_average': 7.651, 'vote_count': 86, 'air_date': '2021-03-05', 'episode_number': 9, 'episode_type': 'finale', 'production_code': '', 'runtime': 51, 'season_number': 1, 'show_id': 85271, 'still_path':
i put stars where you can see it
then for some reason, kometa tries to request that 477510
no clue why
the logs for 477510 are talking about dog days
and 477510 is dog days the movie
on tmdb
but I have noc lue why thats attached in my logs
I don't even have that movie
or why its popping for wandavision
I also went through the plexdb looking for 477510
and didnt find it
so after the wanda stuff this is what happens in the log
[2024-06-11 19:26:52,964] [api3.py:67] [DEBUG] | Request Params: {'api_key': '94d8dbd5cdbe02acb0181573229cbbc0', 'language': 'en', 'append_to_response': 'account_states,aggregate_credits,alternative_titles,content_ratings,credits,episode_groups,external_ids,images,keywords,recommendations,similar,translations,videos,watch/providers'} |
and then it errors out with the 404 not found
i'm pretty sure this is a tmdb api issue and you may have to wait it out
Whew. At least that means I'm not going insane lol.
I even removed all overlays and re-ran it to doublecheck
i've tried to suggest an api issue all along
I know you did but I was trying to understand the why
Kometa wasn't explaining it to me at all
TMDB looked like it was fine
the webpage doesn't exist
and hadn't been modified recently
But why is it even looking for that webpage?
Thats my point
I have no clue why its even trying to find that
The webpage not existing doesn't answer that.
I have absolutely nothing on my end that would cause Kometa to call that ID
so why is it reaching out for it
But you aren't really listening to me then
because I stated that I checked my shows against Themoviedb
and they are all accounted for on that site
with proper IDs in plex and on tmdb
Literally the only thing I have done now
is delete What If
and then I killed kometa cache, removed all overlays
cleaned plex out
and tried to rerun
right but Kometa is giong through a listed give by tmdb
and this is the error I get
What list?
Oh........
oooooooh.
someone put the wrong thing on their list then
and thats erroring it out
the api
Wait, i dont know what you mean there.
The api is checking the show
and then checking the show field
so why would it be pulling some random id
that I do not have
basically why is Kometa calling the TMDB api with some random id
wouldn't it call the api with the id of the show in my plex library
if Kometa generated some rando list to call TMDB with based on my library, then wouldn't me wiping the cache/db out remove that list
and it would have to be generated again
it's checking a list of data returned by tmdb's api. the list contains shows that you may or may not have
Got ya. So then when it gets to like Wandavision
its all fried on the api right now for some reason
and is includng that Dog days thing and its breaking
wanda vision isn't returning the error
I mean, per my log, thats where the error comes in though
cuz the Wandavision part has the same ID and the Dog Days garbage
how can you run kometa for a single show
maybe i can try to run it for wanda and then for warehouse 13
those are the back to back shows
that will tell me which one breaks
you'd have to have a library with only one or both of those shows
got ya, let me go ahead and create one real quick and try one out
the error is 477510, which is actually a movie and not tv. but the api is trying to get the tv info, which returns a 404 error
and thats because the random TMDB list of things I may have asked for and things I didn't ask for has it in there right
its definitely associated with Wandavision
cuz I tried a test with just Wanda and same problem
I tried one with Walking Dead in front of Wanda, and it was fine
and i tried with Warehouse 13 after, and it was fine
so the api call with Wanda is fried then i guess
wanda works just fine for me
log file?
๐ If you want to review this again, keatingfish:
: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> ๐
โ ๏ธ [WARNING]
Warning messages found in your attached log.
This is a Kometa warning and usually does not require any immediate action. Most [WARNING] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[warning]#warning]
2 line(s) with [WARNING] messages. Line number(s): 452-453
can you try updating to develop, i just remembered there wer some recent fixes that may help
the no items found is warehouse 13
switch from latest to develop?
same issue with wandavision
yes switch from latest to develop
wandavision is not the issue. that log still is erroring with the api call for dog days
switched to develop
ran the test again
same error
only on returning
not on airing
and the show is ended on tmdb
so why would the api call for airing work fine
and the one for returning not work
and its only happening with Wandavision
btw
this right here
https://api.themoviedb.org:443 "GET /3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1" 200 None |
thats wandavision
and then it returns that junk
with dog days etc etc
so its definitely wandavision interacting with the api
Ok i just ran that same api call in a browser
and it worked fine, no issues
so how can I delete out whatever cached api kometa is using
no it isn't. that give a 200 response, which is an okay response
I just ran that same api command and no dog days stuff appeared
in my browser..so Kometa
has some weird cached api that was broke
how can I get Kometa to run a fresh one
but that isn't where the 404 is coming from
Antwan
The same exact api call that Kometa did
popped that dog days crap
I just ran that same exact api call in my browser
and no dog days crap
Kometa ---
[2024-06-11 20:47:55,388] [api3.py:82] [DEBUG] | Response (200 [OK]) {'id': 477510, 'results': [{'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Trailer', 'key': 'fAfqqHwgI1U', 'published_at': '2018-06-13T12:59:58.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Trailer', 'official': False, 'id': '5b2e43e50e0a2657ea004c3b'}, {'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Teaser', 'key': 'zA_khn8cuq0', 'published_at': '2018-05-09T13:59:53.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Teaser', 'official': False, 'id': '5b2e43f6c3a368533b004e0d'}], 'keywords': {'adult': False, 'backdrop_path': '/1i1N0AVRb54H6ZFPDTwbo9MLxSF.jpg', 'created_by': [{'id': 123132, 'credit_id': '600b066223d278003d3720ef', 'name': 'Jac Schaeffer', 'original_name': 'Jac Schaeffer', 'gender': 1, 'profile_path': '/u5RGA1m3XGXlRdXzexYbqYZAKcP.jpg'}], 'episode_run_time': [], 'first_air_date': '2021-01-15', 'genres': [{'id': 10765```
API call and dog days crap
here is my browser
{"adult":false,"backdrop_path":"/1i1N0AVRb54H6ZFPDTwbo9MLxSF.jpg","created_by":[{"id":123132,"credit_id":"600b066223d278003d3720ef","name":"Jac Schaeffer","original_name":"Jac Schaeffer","gender":1,"profile_path":"/u5RGA1m3XGXlRdXzexYbqYZAKcP.jpg"}],"episode_run_time":[],"first_air_date":"2021-01-15","genres":[{"id":10765,"name":"Sci-Fi & Fantasy"},{"id":9648,"name":"Mystery"},{"id":18,"name":"Drama"}],"homepage":"https://www.disneyplus.com/series/wandavision/4SrN28ZjDLwH","id":85271,"in_production":false,"languages":["en"],"last_air_date":"2021-03-05","last_episode_to_air":{"id":2724621,"overview":"The events of WandaVision come to a head, and the destinies of all who took part are determined.","name":"The Series Finale","vote_average":7.651,"vote_count":86,"air_date":"2021-03-05","episode_number":9,"episode_type":"finale","production_code":"","runtime":51,"season_number":1,"show_id":85271,"still_path":"/8OIqCs8UUiG1ifmrAcn29A7tL4T.jpg"},"name":"WandaVision","next_episode_to_air":null,"networks":```
same exact api call here
https://api.themoviedb.org/3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2%20Keywords
so either Kometa has a cached api that i can't clear out even after deleting my cache
or its borked
because I literally just ran the same thing outside Kometa and didn't get Dog Days
the 404 is coming from the 477510
You obviously aren't listening to me
where is the 477510 coming from then?
not from me
not from my database
not from my plex
not from kometa
if you put this command in https://api.themoviedb.org:443 "GET /3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1"
it doesnt give you any dog day crap
so im at square one again
cuz there's no explanation as to why some random ID is being sent to me
when or after Wandavision runs
and again I ran a test library with only Wandavision
i'm looking at the log file, the 477510 is dog days and that is what is returing the 404
and I get dog days
I literally ran it with just one tv show
]and I get the dog days shit
but if i run the same exact api call outside kometa
I don't get it
Thats not hard to understand
The only variable is Kometa
lol
85271 is not the call that is giving the 404
Reponse means a response answer
| https://api.themoviedb.org:443 "GET /3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1" 200 None | thats the call
[2024-06-11 20:47:55,388] [api3.py:82] [DEBUG] | Response (200 [OK]) {'id': 477510, 'results': [{'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Trailer', 'key': 'fAfqqHwgI1U', 'published_at': '2018-06-13T12:59:58.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Trailer', 'official': False, 'id': '5b2e43e50e0a2657ea004c3b'}, {'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Teaser', 'key': 'zA_khn8cuq0', 'published_at':
there is no API call here
If I pull a log of my library with multi shows
every single show goes like this
API call to the show
big list of all the metadata from that show
repeat repeat repeat
except for Wandavision
which goes API call tot he show
Dog Days shit
You are looking at the part afterwards
thats not the problem
Please listen to me
I setup a test library with only Wandavision
nothing else.
Just Wandavision
Therefore Kometa will only call Wandavision
So why is it making 2 API calls
if I have just 1 single show
in my library
its calling 85271
and then 477510
but I only have 1 show in my library
Why does the Wandavision API call have Dog Days info and Wandavision info
before the 477510 is called
?
if I do the same Wandavision API call outside Kometa
I get 0 dog days crap
[2024-06-11 20:47:55,365] [builder.py:2233] [DEBUG] | 1 IDs Found
[2024-06-11 20:47:55,365] [api3.py:66] [DEBUG] | Request URL: https://api.themoviedb.org/3/tv/85271
[2024-06-11 20:47:55,387] [connectionpool.py:549] [DEBUG] | https://api.themoviedb.org:443 "GET /3/tv/85271?api_key=94d8dbd5cdbe02acb0181573229cbbc0&language=en&append_to_response=external_ids%2Ckeywords HTTP/1.1" 200 None |
Its requesting Wanda
[2024-06-11 20:47:55,388] [api3.py:82] [DEBUG] | Response (200 [OK]) {'id': 477510, 'results': [{'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Trailer', 'key': 'fAfqqHwgI1U', 'published_at': '2018-06-13T12:59:58.000Z', 'site': 'YouTube', 'size': 1080, 'type': 'Trailer', 'official': False, 'id': '5b2e43e50e0a2657ea004c3b'}, {'iso_639_1': 'en', 'iso_3166_1': 'US', 'name': 'DOG DAYS | Official Teaser',
Dog Days response followed by Wanda response with info, all in the same debug
then it tries to call the 455710
and dies
But I only have 1 show
not 2
I stand by my point. I have a test library with only Wandavision in it. Nothing else. When I run Kometa and try to apply an overlay it goes through the airing with no issues. it gets to returning and thats where it dies. In the log it shows it making an API call for Wandavision, and returning Dog Days and Wandavision information. Then it tries to run an api call for 477510 the movie, no clue why except it came from inside the Wandavision data it provided. So it made 2 API calls for 1 show for the same overlay section.
When I run the same api call outside Kometa for Wandavision, I do not get the dog days stuff at all in the response. I only get the Wandavision stuff.
so not sure if the Kometa api call is cached somehow cuz of the key
and its pulling some old call that got fried out somehow
or if Wandavision is fried somehow.. but my question would be
how do kill a cached api call from Kometa if thats what its doing. Just generate a new TMDB key and plop it in?
and bingo
cached api call that was fried
cuz on my reset of my api key, no dog days stuff
It must have cached the api call I guess?
so when you would test all was ok cuz of your key
but when I tested I kept getting the same garbage out
Man without us going in circles I never would have figured that out lol
Definitely appreciate all the time you spent helping.
i was trying to understand in the same way you were
Let me become a sponsor now fully for ya.
Yeah... you telling me how to do the test thing helped a ton
cuz I was able to isolate it specifically to one show
and then compare the api call from Kometa to just a random one in a browser with no key
im running my full library now to see if i was correct
yep there we go
all the returning overlays are being added
๐
good stuff. Appreciate you a ton. Sorry, I was just bashing my head cuz I kept seeing the same thing no matter everything I did.
Let me throw some bones to you all real quick then snooze! ๐
done. $10 tossed. thanks again Antwan! Appreciate the 2nd brain to help out
let me close this thing