#PMM run doesn't finish and causes Plex to become unhealthy (need to reinstall image to fix)

1 messages · Page 1 of 1 (latest)

tall ploverBOT
#

Welcome @cobalt peak!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

tall ploverBOT
cobalt peak
tall ploverBOT
#

📝 Great! Let's start to review and make recommendations, alia0623... 📝

#

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

#
**User Info**

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

Table of Contents

Page 01: User Info
Page 02: PMM Info
Page 03: PMM Config.yml YAML Validation ✅
Page 04: WIP - PMM Config.yml Schema Validation ❌
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - 💬 CONVERT ERROR
Page 08: Rec 02 - 💬 LEGACY SCHEMA DETECTED
Page 09: Rec 03 - 💡️PLEX DB CACHE ADVICE
Page 10: Rec 04 - ⏱️ TIMEOUT ERROR

Page 1/10
cobalt peak
#

I started PMM manually using the command screen docker run --rm -it --network=saltbox -u '1000:1001' -e 'TZ=America/Chicago' -v /opt/plex-meta-manager:/config meisnate12/plex-meta-manager:latest --run

olive urchin
#

you could increase your timeout per the Luma recommendation

warm cloak
#

pmm can 100% cause plex to become unhealthly

#

its due to the #announcements though

#

were currently in talks with plex to improve the api stuff on 1.29 and greater

#

your plex logs are probably full of locked db messages

cobalt peak
#

hmm let me look

warm cloak
#

usually when that happens plex becomes super unresponsive

#

for the best performance with pmm, 1.29 is the best version to be on.

cobalt peak
#

I tried rolling back to that version but it wouldn't run afterit was installed. Kept throwing a 503 error

warm cloak
#

did you wait for the database migration to finish?

#

going from 1.32 to 1.29 will cause a db migration

cobalt peak
#

No I did not, I will let it sit for a while

#

yeah a ton of

Oct 25, 2023 17:24:03.950 [139870888205112] WARN - [Req#4052] SLOW QUERY: It took 330.000000 ms to retrieve 22 items.
Oct 25, 2023 17:24:03.951 [139870883986232] WARN - [Req#4047] SLOW QUERY: It took 430.000000 ms to retrieve 36 items.
Oct 25, 2023 17:24:03.956 [139870879767352] WARN - [Req#4048] SLOW QUERY: It took 410.000000 ms to retrieve 22 items.```
warm cloak
#

yea my docker logs for plex are always filled with

Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.```
when it gets unresponsive
ashen yoke
#

The above message makes me want to eat broken glass whenever I see it...

cobalt peak
#

I can see it doing the DB migration now, it's been about 40 minutes. I'll let it run over night and then if it's back up I'll try another run and report back.