#Trying to download one particular poster causes crash

1 messages · Page 1 of 1 (latest)

proud stream
#

I update poster for my movie connection using metadata yml. Have this particular Movie, The First Omen
relevant code

...
  437342: # TMDB id for The First Omen (2024) Poster
    url_poster: https://theposterdb.com/api/assets/266642
...

When I run using docker, I get's stuck on this one movie poster and then crashes that section, out of 180 movies this is the only one with such an issue. If I comment out the section in the meta yml, everything works fine

jaunty lavaBOT
#

Welcome @proud stream!

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.

jaunty lavaBOT
proud stream
jaunty lavaBOT
#

📝 If you want to review this again, 0utlawactual:
: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> 📝

#
**Rec 05** - ❌ **PLEX DB CACHE ISSUE**

❌ PLEX DB CACHE ISSUE
The Plex DB cache setting (4.00 GB) is equal to or greater than the total memory (4.00 GB). Consider adjusting the Plex DB cache setting to a value below the total memory.
For more info on this setting: https://kometa.wiki/en/latest/config/plex#plex-attributes
NOTE:The number you choose can vary wildly based on a number of factors (such as the size and number of libraries, and the amount of files/operations/overlays that are being utilized).

Page 11/14
vocal sphinx
#

looking further, the critical summary doesn't show the 500 error, but the 500 error is what caused the crash

eternal graniteBOT
#
500 Internal Server Error

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)

Thanks for using Kometa
fervent temple
#

That image is 12M, and Plex has problems with images larger than 10M.

curl -o foo.jpg https://theposterdb.com/api/assets/266642
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 12.0M  100 12.0M    0     0  9851k      0  0:00:01  0:00:01 --:--:-- 9851k
proud stream
#

ok yes, the log debugger helped me see that was the issue, found another source of same image, smaller size, running kometa again, seems fine now. Thank you. We can close this ticket now