#Kometa stopping every time on Batman Begins

1 messages · Page 1 of 1 (latest)

hollow root
#

No matter how hard I try, Kometa keeps stopping on Batman Begins. My config was working for the longest time, but I feel like something might be improperly configured.

📎 meta.log
vivid pawnBOT
#

📝 If you want to review this again, phtmraven:
: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 @hollow root!

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.

vivid pawnBOT
#
**Rec 03** - ⚠️ **[WARNING]**

⚠️ [WARNING]
Warning messages found in your attached log.
This is a Kometa warning and usually does not require any immediate action. Most [WARNING] lines can be ignored.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[warning]#warning]
5 line(s) with [WARNING] messages. Line number(s): 6653, 6662, 8273, 9012, 11102

Page 9/9
hollow root
#

Just want to note that since Kometa keeps stopping, I can not get a complete log.

viral thistle
#

If Kometa exits without an error like this, typically it's something external killing it, and a common cause is memory.

hollow root
#

Any chance it's related to Crowdstrike?

#

Memory on my device seems to be ok.

swift lance
#

Doubt it

viral thistle
#

I have no idea what crowdstrike is. Oh, that. No, probably not.

#

Even it it were I would expect an error not a silent exit of a python script on some random machine.

hollow root
#

Fair enough, just thought I'd ask. Not sure what's going wrong then. I'll dig more into the system monitor and see if I can find anything

#

I stand corrected, seems like it was a memory issue specifically with Prowlarr hogging resources. I temporarily killed the prowlarr container to see if this has any improvement. I may need to just upgrade the RAM on my server PC.

light lodgeBOT
#

antwanchild used !afnh

@hollow root, 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.