#Errors I cannot figure out

1 messages · Page 1 of 1 (latest)

lone jacinth
#

i cannot figure out how to fix these errors. i see clean_bundles in my config file, it is set to false.

i didnt have this issue last time but i havent touched kometa in like 3 weeks and now i get these errors

📎 Kometa_errors.txt
hasty quailBOT
#

Welcome @lone jacinth!

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.

hasty quailBOT
heady hound
#

Please provide the full log

heady hound
#

@lone jacinth Almost certainly this is going to be a config.yml formatting issue, but without a log all anyone can do is guess.

lone jacinth
#

Okay let me figure out how to post the log. Apologies.

burnt turretBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Kometa
lone jacinth
hasty quailBOT
#

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

#

Message "1" not found.

#

Message "3" not found.

heady hound
#

I don't see any obvious problems in that config on first pass.

The first thing I'd try would be to switch off this custom branch back to master or nightly or one of the standard branches to narrow down whether some change on that branch is implicated:

|     Version: 2.1.0 (Python 3.12.7) (Git: added-overlay-items)
heady hound
hasty quailBOT
#

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

hasty quailBOT
# hasty quail
**User Info**

Author of Linked Message: Yiddish Gambino
Person who Invoked the Command: Mr. Carrot
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: Rec 01 - 💥 [CRITICAL]
Page 07: Rec 02 - ❌ ANIDB AUTH ERRORS
Page 08: Rec 03 - ❌🔒 BLANK API KEY ERROR
Page 09: Rec 04 - ❌ MY ANIME LIST CONNECTION ERROR
Page 10: Rec 05 - ⚠️ [WARNING]

Page 1/10
lone jacinth
heady hound
#

never mind I can repro it so when I get home later I'll take a look.

No idea why you would have had to fork the repo for that. The config is not controlled by git.

lone jacinth
#

yo no se, but i see what you mean by the branch. I have moved back to master, and let me see if it runs. appreciate the eyes!

how do i "start over" if i wasnt supposed to fork? i can of course copy my config files out and just delete the whole forked repo and re-clone?

#

getting the same errors on master.

heady hound
heady hound
#

Oh, here's the problem. LIne 7 doesn't belong here:

image.png
#

You have a library named "Movies", which is empty, which is causing the error.

Then you have a library named "operations", which would cause an error later if Kometa ever got that far.

Remove that line and try again.

burnt turretBOT
#

chazlarson used !aenh

@lone jacinth, 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.