#RetryError[<Future at 0x7f9da9389490 state=finished raised Failed>]

1 messages · Page 1 of 1 (latest)

sage parrot
warm flumeBOT
#

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

#

Welcome @sage parrot!

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.

warm flumeBOT
verbal pumice
#

An attempt to upload a poster to Plex made something inside Plex explode.

| plexapi.exceptions.BadRequest: (500) internal_server_error; (redacted)/library/metadata/4502/posters <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |

[the retryerror is the final report in this event]

A typical cause is that the image is too big [>10Mb], but ultimately Kometa can't do anything directly about this since it's making a boring request to Plex to set a poster, and Plex is exploding in response.

sage parrot
#

Any reason it would do this to a server on an nvidia shield and not to the server running on a PC?

main frost
#

Has nothing to do with the server. If the image is bigger than 10m plex will explode every time

sage parrot
#

i guess what im trying to say is that if i point kometa to my other plex server running on my PC i dont get the same errors when its setting the same posters. I also checked the size and i dont have any that are over 10mb.

verbal pumice
#

The image size is just one possible cause of a 500 that we've seen regularly, and I only mentioned it because the error is happening when an image is being uploaded.

A 500 error means that something went wrong inside the server that no developer foresaw and no tester ever hit. If either of those had happened then at least there would be a sensible error.

The Shield is presumably hardware-constrained compared to the PC, might be a different version, different platform, etc. There are any number of reasons why the two servers may react differently. Kometa will be making exactly the same request in either case.

You could take a look at the plex logs to see if there's a clue in there.

sage parrot
#

looks like it might have been an issue with the hard drive. After reformating its running without errors.