#Not working after making changes yesterday

1 messages ยท Page 1 of 1 (latest)

cloud etherBOT
#

๐Ÿ“ If you want to review this again, early.jubal.stonewall.cuyler:
: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 @white badger!

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.

cloud etherBOT
#

I opened a case yesterday to update my Christmas collection and made some recommended updates to my config file. It looks Kometa is not running now for some reason.

#
**Rec 08** - โš ๏ธ **LEGACY SCHEMA DETECTED**

โš ๏ธ LEGACY SCHEMA DETECTED
overlay_level: is no longer used and should be replaced by builder_level:.
For more information on handling these, [https://kometa.wiki/en/latest/files/settings/?h=builder_level]
9 line(s) with overlay_level errors. Line number(s): 126, 129, 133, 136, 140, 143, 147, 150, 159

tribal pawn
#

No need to attach your config,

white badger
#

Sorry wasn't sure if that was necessary or not

tribal pawn
#

wasn't necessary last night, still not necessary. LOL

white badger
#

Lol seems like it was requested when I started doing this several years ago

inland hazel
#

We have evolved. ๐Ÿ™‚

tribal pawn
#

where did you get this? yaml default:: # Library mappings must have a colon (:) placed after them Movies:

#

that isn't valid kometa yaml, so nothing is being processed

white badger
#

I have no idea. I assume its always been that way. It ran up until we made those recommended changes last night.

tribal pawn
#

it's never ran that way

#

last night i told you to change pmm to default, which you did, but then you changed ```yaml
libraries:

Movies:``` to what you have

white badger
#

I have no idea how that part got changed. I didn't intentionally edit it.

tribal pawn
#

changing it to what it should be, should fix the "not running"

white badger
#

Thanks. I downloaded the old file and compared it. Seems like I have it correct now. I'll try running it manually to see if it'll run.

tribal pawn
#

downloaded the old file and compared it
where do you have the old file vs the one you are using?

white badger
#

I put it in my Windows download folder and added the date to the file name. The config.yml file is safe on my Unraid server.

#

I'm running it manually and seems to have gotten through the beginning part so I think its good.

tribal pawn
#

the bot still has some other good recommendations

white badger
#

I think some of the recommendations are stuff I don't use (ANIDB and MY ANIME). I haven't looked into the others though and seen what it would take to clean those up.

tribal pawn
#

Right but you can still comment that portion out to quiet the error

white badger
#

Is that where the blank API key is coming from too?

#

Commented the 5 anidb lines out so that should go away next time

tribal pawn
white badger
#

I changed all overlay_level to builder_level per the recommendation too

#

It says lines 320 and 388. Notepad++ says my config file is only 260 lines.

tribal pawn
#

that's the line number in the logfile

#

would recommend using vscode and not notepad

orchid nimbusBOT
#
Recommended Text Editors

We highly recommend to use a decent editor software to manage Kometa's .yml files.

Standard text editors (such as Notepad and TextEdit) often save text in a rich-text format which can result in text formatted in a way that Kometa cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
Kometa requires indents to always be multiples of 2 spaces, and not TAB stops. If you have one space too much, or too few, it is very hard to notice that with a editor like Notepad.
An editor that is more focused on editing code instead of text will automatically detect the .YML fileformat and adjust things to make it easier to work. They can also try to detect possible errors even before you actually run the .yml in Kometa.

This can save a lot of time and headaches.

Preferred:
Visual Studio Code (Windows/Mac/Linux, Opensource & Free) Website
Additionally, install the indent-rainbow by oderwat extension and the YAML by Red Hat extension and leverage our schema.json file by adding this to the top of your config.yml file: # yaml-language-server: $schema=https://raw.githubusercontent.com/Kometa-Team/Kometa/nightly/json-schema/config-schema.json

Other options:
Notepad++ (Windows only, Opensource & Free)
Website

Sublime Text (Windows/Mac/Linux, Paid)
Website

For further details and a short list of highly recommended extensions, you can also take a look here.

Here is an example of how Visual Studio Code works with indent-rainbow plugin and using our Kometa schema (Click on image to get a better view):

white badger
#

I guess that's different than the line number in config file then? I have the software but forgot because I haven't had to open this config file in a while. I can only find one blank API key and its for notifarr. Should I comment out the two notifarr lines since I don't use it?

tribal pawn
#

Yes. Those line numbers refer to the line numbers in the log

#

The same log you posted, that queued the bot

white badger
#

I see. I thought it was reading the config file. Looks like it was referring to notifarr on both lines.

#

What are the mal lines for at the end?

#

All of mine are empty so I'm assuming its safe to comment those out too?

tribal pawn
#

Mal is anime

white badger
#

I commented those lines out too then.

#

Hopefully the bot will like my config file the next time I post a log

orchid nimbusBOT
#

antwanchild used !afnh

@white badger, anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.

warped shell
white badger
#

It looks like it ran successfully. Thank you again for your help.