#Hanging while processing movies

1 messages · Page 1 of 1 (latest)

little grove
#

I've been having an issue lately where Kometa just hangs while processing movies. It seems to hang on random films and does not seem to be consistent.

📎 meta.log
heady plumeBOT
#

📝 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 @little grove!

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.

heady plumeBOT
#
**User Info**

Author of Linked Message: PhtmRaven
Person who Invoked the Command: PhtmRaven
File Name: meta.log

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: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - ❌ [ERROR]
Page 08: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 09: Rec 03 - ⚠️ [WARNING]

Page 1/9
frail mirage
#

You might try a run with --log-requests and --trace to see if that provides some visibility into what's going on at that moment.

heady plumeBOT
#

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

heady plumeBOT
# heady plume
**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]
7 line(s) with [WARNING] messages. Line number(s): 6985, 6994, 8627, 8863, 9291, 9405, 9433

Page 9/9
heady plumeBOT
flat warren
#

When this happens, is Plex still responsive or do you see the dreaded db busy sleeping 200ms repeatedly?

#

You can try a db repair to see if that helps

nocturne matrixBOT
#
Plex DB Repair Tool

DBRepair provides database repair and maintenance for the most common Plex Media Server database problems. It is a simple menu-driven utility with a command line backend.

DBRepair is run from a command line (terminal or ssh/putty session) which has sufficient privilege to read/write the databases (minimum). If sufficient privleges exist (root), and supported by the environment, the options to start and stop PMS are presented as well. (Some envionments require DBRepair to run as the 'root' user.)

You can learn more about this tool and download/use it on ChuckPA's GitHub Repository https://github.com/ChuckPa/PlexDBRepair

Thanks for using Kometa
little grove
little grove
nocturne matrixBOT
#

antwanchild used !aenh

@little grove, 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.