#Help setting up Kometa (containe; more in comment)

1 messages · Page 1 of 1 (latest)

scenic yew
#

I like the idea of having Kometa updating automatically my movies poster using TMDB vs Gracenote w/ the new Plex agent. Though I don't need the overlays or collection, I really just want the poster.

I find it difficult to navigate the wiki, probably not looking at the right place. I created the container and it generated a default template config file. that's where I'm lost, so many things to edits... I was also reading Notifiarr integration?

Thanks, appreciate any help!

outer pewterBOT
#

Welcome @scenic yew!

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.

outer pewterBOT
north goblet
#

What OS are you using?

torpid comet
north goblet
#

Nope 😂

torpid comet
#

Sounds like a good Quickstart candidate here in this thread

north goblet
#

It does indeed

#

Feel free to suggest it etc

#

I'm on my phone so difficult

torpid comet
#

There is a local (python install), container (master,develop), and also a single file installer for each of these: MacOS, Windows, and Ubuntu

scenic yew
scenic yew
torpid comet
#

Thats the idea... if you plan on running kometa as a container, then you run Quickstart as a container.

#

It would help rule out some infra stuff....

north goblet
#

It will give you a Web UI to walk through setting up your config.yml

scenic yew
#

Thanks both! Off to bed now, but will update the post if I run into any issue tomorrow. Appreciate the quick response

torpid comet
#

We'd appreciate any and all feedback when you can. 🙂

torpid comet
thorny ferryBOT
#

antwanchild used !aenh

@scenic yew, 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.

scenic yew
#

So I installed a test library, ran the quickstart and move the config to kometa folder. I updated my container environment to KOMETA_RUN=true. How do I know it<s properly running?

#

I<ll provide some feedback once I gather everything, but great tool so far. Really helpful!

#

Also in the settings section "asset directory" confuses me. Do I need to set the metadata folder from Plex there?

#

And to I need to switch Plex scan to « local asset »

grand viper
grand viper
glossy adder
#

How do I know it<s properly running?

You can look at the docker log or tail the log file.

scenic yew
glossy adder
#

I don't understand the question. "Mapped"? As in a docker volume map? No. Or do you mean something else?

scenic yew
#

Apology for the confusion, asset directory ask for a path, I don’t need to have anything there?

glossy adder
#

You don't need to use the asset directory. If you do, the paths you specify there are arbitrary and up to you. They just have to be visible to Kometa. Typically they are located inside /config, which is already mapped into the container. They don't have to be, You can use some other directories and map them into the container if you want.

If you are not planning to use assets, just leave the default value as-is. If you want to silence the single line in the log saying that directory doesn't exist, create it and then forget about it.

scenic yew
#

Perfect, thanks for the explanation and the link above.

scenic yew
#

Can I share my log for potential error? It ran, but didn't update any of the poster

glossy adder
#

of course

scenic yew
#

I have bunch of logs, let me know if this is sufficient.

📎 meta.log
outer pewterBOT
#

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

outer pewterBOT
# outer pewter
**User Info**

Author of Linked Message: JLC4LIFE
Person who Invoked the Command: Antwan
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 - 💥 INTERNAL SERVER ERROR
Page 08: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 09: Rec 03 - ⚠️ [WARNING]
Page 10: Rec 04 - 💬💡️ PLEX DB CACHE ADVICE

Page 1/10
outer pewterBOT
glossy adder
#

didn't update any of the poster

Which were you expecting to update?

scenic yew
#

All using tmdb? I have mass poster update on my config to use it

glossy adder
#

This log is incomplete, and it appears that Plex is failing with an internal error on every request to set a poster:

| plexapi.exceptions.BadRequest: (500) internal_server_error; http://plex:32400/library/metadata/19563/posters?url=https%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2FaBvOleQMesFd7XYLC6Bj3rnYmmG.jpg <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |
#

That URL is fine, and the image is reasonably sized, but apparently something inside Plex is exploding.

scenic yew
#

Should I try making a new config with only Plex and Mass Poster Update?

thorny ferryBOT
#
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
glossy adder
#

This is not a Kometa config issue. Kometa is making a very boring request to Plex and something inside Plex is exploding in response.

scenic yew
#

Perfect, thanks for the help. I’ll try again later maybe

glossy adder
#

It's effectively the same thing as if you did this in the UI:

image.png
scenic yew
#

And that’s kinda where it explode in my xase?

glossy adder
#

Here's the URL that clicking upload went to:

http://192.168.1.11:32400/library/metadata/1342/posters?url=https%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2FaBvOleQMesFd7XYLC6Bj3rnYmmG.jpg&..

Note that it matches the URL in your error. [mine had a bunch of junk at the end about client version and whatnot]

image.png
glossy adder
scenic yew
#

I’ll use my internal IP address for Plex instead of my container. Maybe this is going to help

#

That IP address in your example above, which is it? Because it’s none of mine whether container or local

glossy adder
#

That's the local IP address for my test plex server downstairs.