Kometa Stuck in a loop | Kometa | Page 1

tawdry mist Apr 27, 2024, 10:53 PM

#

I have just configured kometa, with some default items and have not configured any runtime schedules. Upon verifying the container logs, I can observe that it has been running in a loop, going over the same step for ever 3 time.

Config: https://pastebin.com/S8rtbHvb
Logs: https://pastebin.com/k8cNueYU

jolly frostBOT Apr 27, 2024, 10:53 PM

#

Welcome @tawdry mist!

It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.

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.

jolly frostBOT Apr 27, 2024, 10:53 PM

#

jolly frost You can press the "Close Post" button above or type `/close` at any time to clos...

rigid shadow Apr 27, 2024, 10:54 PM

#

can you just drag and drop the meta.log into this thread please and then answer yes (green check) to both prompts?

#

we can get the redacted config from the meta.log

#

pastebin for logs is incomplete... hence the drag and drop into discord please

tawdry mist Apr 27, 2024, 10:56 PM

#

📎 meta.log

jolly frostBOT Apr 27, 2024, 10:56 PM

#

📝 If you want to review this again, monologu:
: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 09** - 💬💡️ **PLEX DB CACHE ADVICE**

💬💡️ PLEX DB CACHE ADVICE
Consider updating the Plex DB cache setting from 0.04 GB, to a value greater than 1 GB based on the total memory of 16.00 GB.
Setting db_cache: 1024 within the plex settings in your config.yml is effectively 1024MB which is 1GB. For more info on this setting: https://kometa.wiki/en/latest/config/plex#plex-attributes
NOTE:The number you choose can vary wildly based on a number of factors (such as the size and number of libraries, and the amount of files/operations/overlays that are being utilized).

#

📎 parsed_meta.log_config_MonoLoGu.yml

rigid shadow Apr 27, 2024, 10:58 PM

#

ok. so it looks like you have some things going on in your setup as per the luma bot

#

are you running this via docker compose?

tawdry mist Apr 27, 2024, 10:58 PM

#

yes, compose

rigid shadow Apr 27, 2024, 10:58 PM

#

can you share that please

tawdry mist Apr 27, 2024, 10:58 PM

#

one moment

rigid shadow Apr 27, 2024, 10:59 PM

#

i think you might be using a restart line in that and this is causing the loop

#

sorry.. I am tired... so I would also like to know how you are running kometa... was this a manual run that you did? Or was this from a scheduled run

tawdry mist Apr 27, 2024, 11:00 PM

#

  kometa:
    image: kometateam/kometa:latest
    container_name: kometa
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - KOMETA_CONFIG=/config/config.yml
      - KOMETA_TIME=03:00
      - KOMETA_RUN=True
      - KOMETA_TEST=False
      - KOMETA_NO_MISSING=False 
    volumes:
      - ${DOCKERCONFDIR}/kometa:/config

#

I just launched the container with Kometa_run as true

#

and that was about it, besides the config

rigid shadow Apr 27, 2024, 11:02 PM

#

ok. so the kometa_time is best to be set OUTSIDE of the plex maintenance peried whcih is 3-5am

#

I would not use the -KOMETA_RUN=True here

#

i suspect that the container stops and then there is a restart if stopped and the container loops endlessly

#

  kometa:
    image: kometateam/kometa:latest
    container_name: kometa
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - KOMETA_CONFIG=/config/config.yml
      - KOMETA_TIME=05:00
      - KOMETA_TEST=False
      - KOMETA_NO_MISSING=False 
    volumes:
      - ${DOCKERCONFDIR}/kometa:/config

tawdry mist Apr 27, 2024, 11:04 PM

#

Ok, one moment to reconfigure it

#

Also, is there a way to configure kometa overlays to run every time media is being added ?

rigid shadow Apr 27, 2024, 11:05 PM

#

also a path issue to fonts and a tautulli issue to resolve. So if you flip through the pages from luma above, you can see how to resolve those issues.

rigid shadow Apr 27, 2024, 11:05 PM

#

tawdry mist Also, is there a way to configure kometa overlays to run every time media is bei...

this is currently technically not possible

#

there are reasons for it and I can explain if you'd like....

tawdry mist Apr 27, 2024, 11:06 PM

#

at lest a short version, if it is not a big issue

tawdry mist Apr 27, 2024, 11:07 PM

#

rigid shadow also a path issue to fonts and a tautulli issue to resolve. So if you flip throu...

ok, will check it out, but tautulli is already in the config file

rigid shadow Apr 27, 2024, 11:08 PM

#

so short version.... taking an overlay like imdb top 250, we don't know where it falls into the whole scheme of things without running a full overlay run agains the whole library. if something falls off the list, we would not know and if something just made the list we dont know...

#

tautulli url is in there, but as the bot is showing... not working

#

maybe a bad url or bad apikey?

#

or maybe a docker network issue where the kometa and tautulliu containers cannot "see" each other?

tawdry mist Apr 27, 2024, 11:10 PM

#

does it care about base URLs ?

rigid shadow Apr 27, 2024, 11:11 PM

#

mine looks like this:

tautulli:                                           # Can be individually specified per library as well
  url: http://192.168.2.242:8181
  apikey: 635(redacted)af789

tawdry mist Apr 27, 2024, 11:12 PM

#

tautulli:
  url: http://10.1.10.254:8181
  apikey: ea451c5(redacted)d05abc3b7

Same as here 😐

rigid shadow Apr 27, 2024, 11:12 PM

#

seems like then you'd want to exec into the kometa container and try to ping that IP

#

i suspect that your container is not able to reach the tautulli container from Kometa container

#

alternatively, as the logs show, go to the lines reported and see what it says there?

tawdry mist Apr 27, 2024, 11:13 PM

#

Ok, will do so, would it be an option to also use the docker internal netowork with container hostnames ?

rigid shadow Apr 27, 2024, 11:14 PM

#

i have seen people do that... yes

#

again... this is outside of the scope of kometa itself, but people around here are better versed than me in docker

obsidian temple Apr 27, 2024, 11:15 PM

#

I use docker and I assigned tautulli to the same network

#

In my compose file

tawdry mist Apr 27, 2024, 11:16 PM

#

all my *arr + plex are on the same "backend" network so I beleve that should be fine, I will implement the luma recommended fixes, rerun kometa and then see if I have any more issues.

rigid shadow Apr 27, 2024, 11:18 PM

#

fair enough. we are here to assist

tawdry mist Apr 27, 2024, 11:26 PM

#

By default, the the scripts do not execute at container startup ?

obsidian temple Apr 27, 2024, 11:31 PM

#

by default, Kometa runs at 5am

tawdry mist Apr 27, 2024, 11:31 PM

#

Is there a way to manually force an execution ?

obsidian temple Apr 27, 2024, 11:32 PM

#

are you running with docker compose?

tawdry mist Apr 27, 2024, 11:32 PM

#

yes

obsidian temple Apr 27, 2024, 11:33 PM

#

KOMETA_RUN=true as an env variable

tawdry mist Apr 27, 2024, 11:34 PM

#

if I add meta log agin, will I trigger luma ?

#

📎 meta.log

jolly frostBOT Apr 27, 2024, 11:35 PM

#

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

tawdry mist Apr 27, 2024, 11:37 PM

#

Ok, so container hostnames did not work... bummer

tawdry mist Apr 27, 2024, 11:44 PM

#

obsidian temple `KOMETA_RUN=true` as an env variable

ok, now I am back to the looping issue

#

📎 meta.log

jolly frostBOT Apr 27, 2024, 11:54 PM

#

📝 If you want to review this again, monologu:
: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 06** - 💬 **CONVERT WARNING**

💬 CONVERT WARNING
Convert Warning: No * ID Found for * ID.
These sorts of errors indicate that the thing can't be cross-referenced between sites. For example:

Convert Warning: No TVDb ID Found for TMDb ID: 15733

In the above scenario, the TMDB record for The Two Mrs. Grenvilles ID 15733 didn't contain a TVDB ID. This could be because the record just hasn't been updated, or because The Two Mrs. Grenvilles isn't listed on TVDB.

The fix is for someone like you, perhaps to go to the relevant site and fill in the missing data.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/#warning]
136 line(s) with Convert Warnings. Line number(s): 1068, 2009-2014, 14288-14303, 14918-14923, 15045-15060, 15104-15139, 15183-15184, 15228, 15808-15843, 16111-16126

tawdry mist Apr 28, 2024, 12:01 AM

#

tawdry mist ok, now I am back to the looping issue

Not sure what I am doing wrong here, is is because of KOMETA_RUN=true ?

obsidian temple Apr 28, 2024, 12:01 AM

#

tawdry mist ok, now I am back to the looping issue

sounds like you have a restart policy

tawdry mist Apr 28, 2024, 12:01 AM

#

in compose nope

tawdry mist Apr 28, 2024, 12:01 AM

#

tawdry mist ``` kometa: image: kometateam/kometa:latest container_name: kometa ...

this is my compose

obsidian temple Apr 28, 2024, 12:02 AM

#

but in my kometa config, i have this ```yaml
tautulli: # Can be individually specified per library as well
url: http://tautulli:8181
apikey: 8qPp-i3{redacted}N9TCx

tawdry mist Apr 28, 2024, 12:03 AM

#

obsidian temple but in my kometa config, i have this ```yaml tautulli: ...

I have fixed that part, I changed to http://10.1.10.254:8181/tautulli for the URL

obsidian temple Apr 28, 2024, 12:05 AM

#

i don't use the time and run at the same time

tawdry mist Apr 28, 2024, 12:07 AM

#

Hmm, that might be an issue I suppose then. But hey, this means that I am getting updates non stop 😉

obsidian temple Apr 28, 2024, 12:09 AM

#

so do you want it to loop or not?

tawdry mist Apr 28, 2024, 12:10 AM

#

That is not how it's suppoed to work so, to skip any potential further issues I will revert to one time per day

obsidian temple Apr 28, 2024, 12:12 AM

#

or you could add a restart policy and say never. and then comment out the time and just use the kometa_run=true

tawdry mist Apr 28, 2024, 12:15 AM

#

And if I only specify kometa_run then the execution time will still be 5am ?

obsidian temple Apr 28, 2024, 12:20 AM

#

no, run makes it run as in run now

#

is the loop a portainer issue?

tawdry mist Apr 28, 2024, 12:26 AM

#

now that I have commented out the time and set restart to no in compose nope, looks like it executed once and stopped

#

📎 meta.log

jolly frostBOT Apr 28, 2024, 12:26 AM

#

📝 If you want to review this again, monologu:
: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** - ❌ **[ERROR]**

❌ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that Kometa did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[error]#error]
64 line(s) with [ERROR] messages. Line number(s): 4252, 4340, 4428, 4516, 4604, 4692, 4780, 4868, 4956, 5044, 5132, 5220, 5308, 5396, 5484, 5572, 5660, 5748, 8993, 9078, 9163, 9248, 9333, 9418, 9503, 9588, 9673, 9758, 9843, 9928, 10013, 10098, 10183, 10268, 10353, 10438, 14314, 20288, 20373, 20458, 20543, 20628, 20713, 20798, 20883, 20968, 21053, 21138, 21223, 21308, 21393, 21478, 21563, 21648, 21733, 24567, 24613, 24659, 24705, 24751, 24797, 24843, 24889, 24935

#

📎 parsed_meta.log_config_MonoLoGu.yml

obsidian temple Apr 28, 2024, 12:27 AM

#

don't need a log for that

tawdry mist Apr 28, 2024, 12:27 AM

#

That was for myself 🙂 To see if there are other issues I should fix

obsidian temple Apr 28, 2024, 12:27 AM

#

if you want it to run at a specified time, then remove the run and add the specified time, but you can't do both from the same container

#

and in that case you would do the time and then set your restart to unless_stopped

tawdry mist Apr 28, 2024, 12:45 AM

#

I also see that I have some collections which are empty, how can I avoid them to be created ?

obsidian temple Apr 28, 2024, 12:47 AM

#

minimum_items: 1 or whatever you want it to be in your config settings

tawdry mist Apr 28, 2024, 12:50 AM

#

  minimum_items: 1
  delete_below_minimum: true

Already have this in the settings

obsidian temple Apr 28, 2024, 12:51 AM

#

were those collections created by plex and not Kometa?

tawdry mist Apr 28, 2024, 12:52 AM

#

That is a good question to be honest, I have no idea as I never looked into collections before using kometa, I will manually delete them, run kometa and see if they appear back

#

Also, is there a way to supress errors for quality types the script is unabel to find as my media is only 1080p or 4k ?

obsidian temple Apr 28, 2024, 12:55 AM

#

no

#

you could turn off those resolutions

rigid shadow Apr 28, 2024, 12:56 AM

#

yes but not in the way you think

#

exactly what antwan said

#

by avoiding resolutions that are not in your library, you avoid the errors

#

but if ever you add a resolution that is not 4k or 1080p, the overlay wont show either

obsidian temple Apr 28, 2024, 12:57 AM

#

but that means, if you do have something with that resolution, it won't be caught because kometa isn't looking for it

tawdry mist Apr 28, 2024, 12:59 AM

#

So I basically configure it to not look at all for those resolutions, ok, sounds good, how ?

wanton junco Apr 28, 2024, 1:00 AM

#

libraries:
  Movies:
    overlay_files:
      - default: resolution
        template_variables:
          use_720p: false

etc.

tawdry mist Apr 28, 2024, 1:00 AM

#

is there a list of all possible resolutions kometa scans for ?

wanton junco Apr 28, 2024, 1:01 AM

#

The wiki page for each default file shows specifically what it does.

tawdry mist Apr 28, 2024, 1:01 AM

#

ok, thanks

obsidian temple Apr 28, 2024, 1:01 AM

#

recommend taking a look at the wiki

wanton junco Apr 28, 2024, 1:01 AM

#

Some don't have a fixed list, like genres

tawdry mist Apr 28, 2024, 1:02 AM

#

obsidian temple recommend taking a look at the wiki

I am but there are so many bits and pieces... damn

obsidian temple Apr 28, 2024, 1:03 AM

#

that's how we learn

wanton junco Apr 28, 2024, 1:03 AM

#

If you have constructive suggestions on ways it could be made more accessible, bring them on.

obsidian temple Apr 28, 2024, 3:28 PM

#

tawdry mist I am but there are so many bits and pieces... damn

!afnh

umbral kindleBOT Apr 28, 2024, 3:28 PM

#

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.

#Kometa Stuck in a loop