#kometa.py fails with, [CRITICAL] | attribute name must be string, not 'Movie'

1 messages · Page 1 of 1 (latest)

manic oak
#

I have been trying and failing to get overlays to work on my Movies library in Plex. Attached are my logs and redacted config I most recently tried. I have also tried other variations of default overlays provided in the wiki. I have tried "python kometa.py --overlays-only -r" and "python kometa.py --operations-only -r" from the docker console and receive the same error each time.

I have scrapped the container and started from scratch. I have tried the develop, nightly, and default containers all with the same result. Very open to the idea I have done something wrong or have an issue with my plex container, but for the life of me I cannot figure it out.

Both containers are running on unraid and installed through community apps. Any help is appreciated.

📎 log.txt
spark trailBOT
#

📝 If you want to review this again, thirdgree:
: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 @manic oak!

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.

spark trailBOT
#
**User Info**

Author of Linked Message: ThirDegree
Person who Invoked the Command: Antwan
File Name: log.txt

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: Rec 01 - 💥 [CRITICAL]
Page 07: Rec 02 - ❌⏰ KOMETA SCHEDULED TIME CONFLICT
Page 08: Rec 03 - 💬💡️ PLEX DB CACHE ADVICE

Page 1/8
violet olive
#

That's not something I've ever seen.

Kometa is asking Plex for information about a movie. Plex is returning some information. Instead of the name "Star Wars" [a string] that attribute "name" contains a "Movie" object.

I might try refreshing the metadata on that library. OR try creating a small test library to see if the problem appears there.

manic oak
#

I’ve refreshed the metadata several times as well, but will do it once. Building a small test library now to see what happens. Will report back.

manic oak
#

Small test library of 10 movies does seem to work. Seems there is an entry or entries in my main plex movie library that is causing the failure. Just not sure how to identify and address it/them.

grand edgeBOT
#
Plex Dance

The purpose of this is to remove all cached metadata and xml data for an item that Plex usually keeps. This helps when you want to “start from scratch” for particular items.

Before doing the plex dance, it is strongly recommended to stop prowlarr, tdarr, lidarr, sonarr, and radarr.

:one: Move the folders/files for the media to a location not scanned by Plex.
:two: Click the three dots next to the server name, or library name for just one library, on the left sidebar and click the "Scan Library Files".
:three: Click the same three dots > "Manage Library" > "Empty Trash".
:four: If applicable, click "More > " at the bottom of the sidebar and click the three dots next to the server name > "Manage Server" > "Clean Bundles".
:five: Move the folders/files back to your media folder.
:six: Click the three dots on the server or library and click the "Scan Library Files" again.

Once finished all of your plex dancing, it is recommended to:
Optimize DB

NOTE When performing a full library plex dance, create a "fakedir" in the folder with 0 media in it. At the end of the plex dance, you can remove those "fakedir" directories.

If you stopped tdarr, sonarr, radarr, lidarr, and prowlarr before starting the plex dance, you can restart them now.

Thanks for using Kometa
violet olive
#

You could enable trace logging or request logging; that may put more in the log.

manic oak
#

--log-requests provided some additional info before the critical error. --trace did not provide anything additional. During one of the --log -request runs it got through about 400 movies and then errored out. Then went back to the same behavior.

📎 log2.txt
spark trailBOT
#

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

#
**User Info**

Author of Linked Message: ThirDegree
Person who Invoked the Command: ThirDegree
File Name: log2.txt

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: Rec 01 - 💥 [CRITICAL]
Page 07: Rec 02 - ❌⏰ KOMETA SCHEDULED TIME CONFLICT
Page 08: Rec 03 - 💬💡️ PLEX DB CACHE ADVICE

Page 1/8
violet olive
#

Presumably movie 400 or 401 is the issue, then.

#

This entire thing is happening down inside the PlexAPI library; there isn't anything Kometa can change here.

manic oak
#

Totally fair. Appreciate the help. I’ll try to ID movie 400 or 401 and see if removing them helps. Worst case sounds like I’m in for a full plex DB rebuild. Thanks again.