#What am i doing wrong

1 messages · Page 1 of 1 (latest)

honest portalBOT
#

📝 If you want to review this again, cinnamonbunss:
: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 @hardy holly!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

lament shuttle
#

Click the green check

honest portalBOT
#
**User Info**

Author of Linked Message: CinnamonBuns
Person who Invoked the Command: CinnamonBuns
File Name: message.txt

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM 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 - Error: PMM scheduled time is missing.
Page 09: Rec 05 - Error: Memory value not found in content.

lament shuttle
#

somewhere between line 4 and 7 of your config has a spacing error

#

probably a tab instead of a space

#

but the log tells you where the issue is

hardy holly
#

ok thanks looking now

lament shuttle
#

But without actually seeing a meta.log file, have no clue

hardy holly
honest portalBOT
#

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

#
**PMM Config.yml YAML Validation** ❌

The config.yml was not detected within your log file. Is it a complete log file?

lament shuttle
#

Meta.log

burnt ravineBOT
#

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

hardy holly
honest portalBOT
#

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

#
**Rec 01** - 💥 **[CRITICAL]**

💥 [CRITICAL]
Critical messages found in your attached log.
There is a very strong likelihood that PMM aborted the run or part of the run early thus not all of what you wanted was applied.
For more information on handling these, [https://www.metamanager.wiki/en/latest/pmm/logs/?h=[critical]#critical]
1 line(s) with [CRITICAL] messages. Line number(s): 409

lament shuttle
#

What editor do you use?

hardy holly
#

note++

lament shuttle
#

I pulled the parse file up in vs code and I see an editor right away at line 7

burnt ravineBOT
#

We highly recommend to use a decent editor software to manage PMM'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 PMM cannot read. But not only that, they also make it very hard to visually distinguish the formatting, such as indentation.
PMM 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 PMM.

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/meisnate12/Plex-Meta-Manager/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 PMM schema (Click on image to get a better view):

lament shuttle
#

Recommend vscode with indent rainbow

hardy holly
#

ok

lament shuttle
#

But the issue is spacing on line 7

hardy holly
#

thank you

lament shuttle
#

and this yaml - file: config/overlays_movies.yml template_variables: # Which overlay(s) should be used? # Posters 4K_banner: false 4K: false operations:

honest portalBOT
#

YAML checked and is NOT valid. Error message:

while parsing a block collection
in "<unicode string>", line 2, column 5:
- file: config/overlays_movies.yml
^
expected <block end>, but found '?'
in "<unicode string>", line 8, column 5:
operations:
^

lament shuttle
#

the 4k_banner and 4k?

#

and just assigning false, don't do anything

#

and everywhere you have the schedule, look at the spacing

burnt ravineBOT
#

When using Plex Meta Manager release 1.20 or later, metadata_path and overlay_path are legacy attributes, and using them will cause the YAML Error: metadata attribute is required to appear in your log files.

Whilst the error can be ignored safely, we recommend you migrate to the new attributes.

An example of the new setup is shown here:

libraries:
  Movies:
    collection_files:   # was metadata_path
      - file: config/Movies.yml
      - pmm: imdb
    metadata_files:   # was metadata_path
      - file: config/MetadataEdits.yml
    overlay_files:   # was overlay_path
      - file: config/Overlays.yml
      - pmm: audio_codec

Follow the below guidance to migrate to the new attributes.

Migrating to `_files` attributes:

:one: If your YAML file creates collections or is a PMM Defaults Collection File then it belongs under collection_files.

:two: If your YAML file creates overlays or is a PMM Defaults Overlay File then it belongs under overlay_files

:three: If your YAML file edits item metadata (see this example) then it belongs under metadata_files

If your file creates collections AND edits item metadata, then it should go in both `collection_files` and `metadata_files`

If you are unsure on the above, the majority of `metadata_path` files  will now fall under `collection_files`, and all `overlay_path` files will now fall under `overlay_files`.

See the wiki for more examples of this.

hardy holly
#

dude at this point i am all eff up ... All i want is this and all i want to do is add the logo where it is streaming from. do you have the code for that

lament shuttle
#

You can do that from the defaults.

#

Do not sure why you have so many file references in your config

hardy holly
#

ok thanks

lament shuttle
#

What’s in your files that’s not in the defaults?

#

And you have everything set at 11 o’clock. So that means that those things are only going to happen if pmm is running AND it’s 11 o’clock. That will not cause pmm to run at 11 if it’s not already running

small ember
# hardy holly dude at this point i am all eff up ... All i want is this and all i want to do ...

Your existing config contains so much more than that.

If you actually only want those three things:

libraries:                                      # This is called out once within the config.yml file
  Movies:
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  Movies (4K):
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  Movies (4K-DV):
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  Movies (4K-Remux):
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  TV:
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  TV (4K):
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming
  TV (4K-DV):
    overlay_files:
    - pmm: resolution
    - pmm: audio_codec
    - pmm: streaming

... rest of config
small ember
#

@hardy holly Anything further needed here? If not, please type /close and hit enter.