#Plex Server dies after Kometa run

1 messages · Page 1 of 1 (latest)

silk solstice
#

Hi!

I run Kometa manually because 2 month ago it startet that every time kometa was running after a time plex died. Server (Synology NAS) is showing plex as running but no device can connect.

The Kometa run ends normal, so no issue in the log. And yes it is defenitly due to kometa, because if i not run kometa for weeks (what i did) nothing happend - but yesterday, again plex died.

Any ideas?

lone daggerBOT
#

Welcome @silk solstice!

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.

lone daggerBOT
sullen mulch
#

Kometa is simply making API calls which Plex fully supports

#

Do you have Kometa set to optimize db after the run? Maybe try enabling/disabling that, potentially look at DBRepair as well to check for any corruption

You can type !dbrepair to learn more about that

silk solstice
#

Yes it is active:
plex:
url:
timeout: 60
clean_bundles: true
empty_trash: true
optimize: true
db_cache: 1024
verify_ssl: true

#

maybe thats the reason for:
Jan 17, 2025 21:41:35.454 [140320279329592] DEBUG - 54 threads are waiting on db connections held by threads: 140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560
Jan 17, 2025 21:41:35.455 [140320264563512] DEBUG - 54 threads are waiting on db connections held by threads: 140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560,140320654453560

tiny jayBOT
#
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
lilac mist
#

Are you running Kometa oustide of the Plex maintenance window? Post a log.

tiny jayBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯_(ツ)_/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Kometa
silk solstice
lone daggerBOT
#

📝 If you want to review this again, killaspongechris:
: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 02** - ❌⏰ **KOMETA SCHEDULED TIME CONFLICT**

❌⏰ KOMETA SCHEDULED TIME CONFLICT
This Run took: 1:47:59
Time between Kometa Scheduled time and Plex Maintenance start: 18:00:00
Kometa scheduled start time: 5:00
Plex Scheduled Maintenance start time: 3:00
Plex Scheduled Maintenance end time: 9:00
You are within the maintenance window between Plex maintenance start time: 3:00 and end time: 9:00. Adjust the Kometa Scheduled start time to 9:00 or adjust the Plex Scheduled Maintenance times to end prior to the Kometa Scheduled run time.
For more information on Plex Maintenance, see https://support.plex.tv/articles/202197488-scheduled-server-maintenance/

Page 8/13
sullen mulch
#

optimizing the db will seem like Plex is down

#

If you run an Optimize Database in the Plex UI you'll find that it becomes unresponsive until it is done

#

You could try disabling that to see if that has any impact

silk solstice
#

ohhh i didnt know that!
And regarding:
Jan 17, 2025 21:41:35.454 [140320279329592] DEBUG - 54 threads are waiting on db connections held by threads:

Is this normal?

idle crane
#

It's not a routine thing that happens when Kometa runs, but it may well be if you enable DB optimization with every run.

silk solstice
#

it happend after die kometa run, so i think it might be due to the optimisation

silk solstice
#

Thanks!