collections and libraries

[half marsh]

I have a file that is structured like this example:
https://metamanager.wiki/en/latest/config/libraries/#example

I am seeing YAML error regarding missing collections or dynamic_collections in my log.
https://metamanager.wiki/en/latest/kometa/logs/#other-troubleshooting-examples

The first example has not been updated to show how these 2 keys co-exist. Could someone tell me if this is a top-level or child in the tree of the first example?

[fluid holly]

Welcome @half marsh!

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.

[jaunty ridge]

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

[fluid holly]

📝 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> 📝

[fluid holly]

**User Info**

Author of Linked Message: Nokternol
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: Rec 01 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 02 - ⚠️ [WARNING]
Page 08: Rec 03 - 💬💡️ PLEX DB CACHE ADVICE

Page 1/8

[loud rapids]

Can you provide your custom YAML files?

That error does not appear to be in that log.

the collections or dynamic_collections keys are peers and would both be at the top level of a collections file.

Neither of them go directly in the config.yml which is shown in your first link.

The various types of YAML files and what goes in them are discussed here:
https://kometa.wiki/en/latest/kometa/install/files/

[half marsh]

Ah okay, so it needs to be a root key in the custom_collections.yml... okay thank you

[loud rapids]

The first example has not been updated to show how these 2 keys co-exist

There is nothing to update here since those 2 keys do not belong in that file at all.

[half marsh]

Sorry I have a docker log which just outputs the error and then I have to try and piece together what is wrong from hunting through the docs and I am not very good at finding what I need.

[loud rapids]

I would suggest going through one of the walkthroughs, which introduces these concepts step by step

[half marsh]

I have the collections key as the root of my only external file so I still don't know where this error is coming from...

Thank you for your time and effort I'll have to tap out now

[loud rapids]

Also review that link I provided above which gives examples of what goes into the various yaml files and how you use them.

[loud rapids]

We would need a log showing the error happening.

I'm sure it's something simple.

[half marsh]

I wrote this setup years ago and only touch it when it breaks. Maybe I need to start again with a new file at some stage

[loud rapids]

Shouldn't be any need for that. This is a simple straightforward issue once we see a log.

[half marsh]

I would need to find said log but the docker log shows it in the last run and meta.log disagrees. Unforunately I'm a career dev with 2 small children so my time to investigate is severely limited.
Thank you again for taking the time.