#jimmisavage

1 messages · Page 1 of 1 (latest)

fossil vapor
#

I changed my yaml to delete collections (which were duplicating) and then thought i'd changed everything back but not the overlays don't work. I also want to leave some collections off

lapis bridgeBOT
#

Welcome @fossil vapor!

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.

lapis bridgeBOT
wintry ether
#

If you have duplicate collections (as in, the names are IDENTICAL) then you have some form of database corruption - Plex does not allow two collections to exist with the same name.

If the above is true, I'd suggest looking into DBRepair

ruby oxideBOT
#
Plex DB Repair Tool

DBRepair provides database repair and maintenance for the most common Plex Media Server database problems. It is a simple menu-driven utility with a command line backend.

DBRepair is run from a command line (terminal or ssh/putty session) which has sufficient privilege to read/write the databases (minimum). If sufficient privleges exist (root), and supported by the environment, the options to start and stop PMS are presented as well. (Some envionments require DBRepair to run as the 'root' user.)

You can learn more about this tool and download/use it on ChuckPA's GitHub Repository https://github.com/ChuckPa/PlexDBRepair

Thanks for using Kometa
wintry ether
#

Regarding overlays "not working" we'd need to see a log file

#

and I don't believe there's a way to exclude specific collections from the delete_collections operation.

fossil vapor
#

okay - can i uplad my config here? Do i need to remove anything?

📎 meta.log
lapis bridgeBOT
#

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

wintry ether
#

The log contains a redacted version of your config file, so the log is all we need

lapis bridgeBOT
#
**User Info**

Author of Linked Message: jimmisavage
Person who Invoked the Command: Yozora
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: Rec 01 - 💥 [CRITICAL]
Page 06: Rec 02 - 💥 YAML ERROR
Page 07: Rec 03 - ❌🛠️ INCOMPLETE LOGS
Page 08: Rec 04 - ⚠️ LEGACY SCHEMA DETECTED

Page 1/8
wintry ether
#

Will review the log in a bit

fossil vapor
#

thanks pal.

wintry ether
# 
    operations:
    #  delete_collections:      ##### IF YOUR COLLECTIONS SHOW DUPLICATES OR YOU USED MY PREVIOUS CONFIGS RUN THIS ONCE AND THEN DISABLE FOR A FRESH COLLECTION START.
        #configured: false      ##### DO NOT MANUALLY DELETE THE COLLECTIONS BECAUSE THE "TAGS" Kometa ASSIGNS WILL STILL BE ATTACHED TO YOUR SHOWS
        managed: true
#

you didn't comment out managed: true

fossil vapor
#

Oh... is that the issue?

wintry ether
#

Seems like it

#

YAML is very finnicky, if one thing is wrong it can throw everything else off

fossil vapor
#

It seems to be running - i'll let you know if all goes well

wintry ether
#

Good stuff

fossil vapor
#

I can confirm it's working as expected now. Thanks for the help - it would have taken me months to find that error! 👍

ruby oxideBOT
#

antwanchild used !aenh

@fossil vapor, 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.

humble tide
ruby oxideBOT
#
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):

Thanks for using Kometa