Kometa constantly running

[gloomy shoal]

Welcome @finite wraith!

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.

[gloomy shoal]

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

[gloomy shoal]

📝 If you want to review this again, coachbear12:
: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** - 🚀 **VERSION UPDATE AVAILABLE**

🚀 VERSION UPDATE AVAILABLE
Current Version: 2.3.0 (Docker: master)
Newest Version (at the time of this log): 2.3.1

Latest Kometa Versions (as of 2026-04-21 00:17:54)
Master branch: 2.3.1
Develop branch: 2.3.1
Nightly branch: 2.3.1-build7

In the Kometa discord thread, type !update for instructions on how to update.
For more information on updating, [https://kometa.wiki/en/latest/kometa/logs/#checking-kometa-version]
1 line(s) with New Version errors. Line number(s): 11

Page 7/15

**User Info**

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

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 - 🚀 VERSION UPDATE AVAILABLE
Page 06: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 03 - ⚠️ [WARNING]
Page 08: Rec 04 - ⚠️ NO ITEMS FOUND IN PLEX
Page 09: Rec 05 - 💬 CONVERT WARNING
Page 10: Rec 06 - Error: Plex scheduled time is missing.
Page 11: Rec 07 - Error: Memory value not found in content.

Page 1/11

[loud sapphire]

You have --run (KOMETA_RUN): True set, and I predict the restart policy on the container is set to either "always" or "unless-stopped".

--run (KOMETA_RUN): True means: "Hey Kometa, run right this second and then exit" It ignores the 3AM run time altogether.

This leads to:

Kometa: KOMETA_RUN is set! I'm running, I'm running, I'm done. Exiting!
Docker: Hey that container exited. Better restart it.
Kometa: KOMETA_RUN is set! I'm running, I'm running, I'm done. Exiting!
Docker: Hey that container exited. Better restart it.
repeat forever

[finite wraith]

So which of thos options do I disable to have it run when loaded and then only at 3am?

[loud sapphire]

have it run when loaded and then only at 3am

You can't do this.

You can tell it to run right when the container starts and then exit with "KOMETA_RUN: True"

OR

You can turn that off and Kometa will wake up at the times you specify in "KOMETA_TIMES"

You can't do both in a single container.

[finite wraith]

ok so i need to lose the KOMETA_RUN: True

[loud sapphire]

If what you want is for the container to sit and wait until 3AM, then run, then go back to waiting, yes.

A typical thing is to set up a second container with "KOMETA_RUN: True" ands a restart policy of never. When you want to run Kometa right this second start that container.

[finite wraith]

ahh ok, yeah I see how that would be useful

Thanks

[keen hedge]

chazlarson used !aenh

@finite wraith, 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.