Komerta keeps stopping randomly

[misty portal]

So I can run the same configuration file on a Windows setup with no issue but when I run it on my Ubuntu Docker set-up it always stops.

It only occurs when sorting audio overlays. Only when doing TV shows, movies are fine.

I checked the logs but it shows nothing of use that I can see.

How do I begin tracing what is causing this? Or what can I provide so someone smarter than me can see what's going on?

[bronze hornet]

Welcome @misty portal!

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.

[strange flint]

Start with the log

[misty portal]

Here's the last two that failed/stopped

[bronze hornet]

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

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

[bronze hornet]

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

[bronze hornet]

**Rec 05** - ⚠️ **MEMORY RECOMMENDATION**

⚠️ MEMORY RECOMMENDATION
The memory value is 4.00 GB, which is less than 8 GB. We advise having at least 8GB of RAM when running Kometa with overlays (we have detected overlays) for optimal performance.

These numbers are purely estimates and 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).

Page 10/12

[dusk flax]

@misty portal looks like your running during plex maintenance. So that’s one factor

Also a memory recommendation

[misty portal]

It does it even when maintenance is not occurring but valid point. I force ran it before bed after messing with it to see if it would complete. It's scheduled for the default time.

Not familiar with the memory recommendation issue, haven't seen that before. How is that resolved? I assume allowing more RAM to the process?

[dusk flax]

Both of those affect what you asked

[misty portal]

I am pretty new at Docker, have been on a Windows forever so forgive my ignorance.

I got Posterizarr running ATM. I will let Kotema run at the scheduled time after maintenance to see if it completes and report back.

[dusk flax]

Or any other process trying to run while Kometa is running

[misty portal]

The only thing that could possibly run would be if someone is streaming but highly doubtful at that time of morning. So 🤞

[dusk flax]

I talking about posterizarr ANYTHING else

[misty portal]

That PC has 16GB, not sure why it's only saying 4GB

[strange flint]

Docker does not have access to the entire host.

Docker on Windows adds extra complication. You may want to try it outside docker as a test.

Both of those are something outside Kometa killing either the script or the whole container; if Kometa was seeing some orderly failure or specific error that would be in the log. As it is the log just ends, which typically means that something external to Kometa killed it. A fairly common cause of that is an out-of-memory condition.

[tulip hill]

antwanchild used !aenh

@misty portal, 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.