#Unraid PMM Crashing My Plex Instance

1 messages · Page 1 of 1 (latest)

analog walrusBOT
#

📝 If you want to review this again, dodgeinmedia:
: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 @grand summit!

It looks like you have not yet completed #938455615741775902, this will allow us to help you quicker.

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.

analog walrusBOT
#

So I have been using PMM for a while now. But now i have shifted to using Unraid instead of linux. For the most part I think I have set it up right, but after running PMM, my Plex always crashes during the operation. I tried different configs from other users but it still causes issues. Any advice is appreciated. Here are my config and my PMM logs.

noble grove
#

You're applying episode-level overlays, which involve a lot of communication with Plex. What this log shows is that Plex just stops responding in a timely manner at some point, and eventually PMM gives up. There's not really anything PMM can do to stop Plex from timing out.

First step is probably to extend the plex timeout.
Next is probably to split up the runs so you're not doing as much at a time.

grand summit
#

How would I increase plex timeout limit?

noble grove
#

It's in the config.yml.

grand summit
#

For Plex I assume? Or do you mean PMM?

noble grove
#

"extend the plex timeout"

#

Yours is currently set to the default of 60 seconds.

grand summit
#

Ahh I see it now.

#

What is a recommended amount? 5 min?

noble grove
#

Mine is set to 360

grand summit
#

Lastly, for splitting up runs, is the best method to do that by simply removing half of the config or is there an actual method to split it in the settings?

noble grove
#

you can use runtime flags to tell PMM to run a single library or whatever

#

only overlays, etc

grand summit
#

Thank you! I will see if either of these changes fixes my issue!

charred shadow
#

You may want to consider the following as well

fallow voidBOT
#
PMM Performance Tips

Use PMM caching where possible: https://metamanager.wiki/en/latest/config/settings/?h=cache#cache

Run PMM after PLEX scheduled tasks so 5am is a good time for that since PLEX runs scheduled tasks between 3-5am

Consider Database Cache Size (MB) settings in PLEX under Settings, Library, Database Cache Size (MB). 2GB = 2048MB or set it in PMM config.yml file: https://metamanager.wiki/en/latest/config/plex/?h=db_cache#plex-attributes

Look into using the ChuckPA dbrepair tool to deal with plex db issues/fixes(He is an employee of Plex)

:one: - remove video thumbnail creation on your libraries (Plex Web UI settings for the Library under Advanced)
:two: - remove credit detection on your libraries (Plex Web UI settings for the Library under Advanced)
:three: - remove intro detection on your libraries (Plex Web UI settings for the Library under Advanced)
:four: - Ensure that other apps that touch Plex do not coincide with each other. Think of TCM, Plex Autoscan, Refresh Metadata, Plex Maintenance

At the end of the day, everyone's system will have different performance characteristics. Some have to implement all of these before MOST of the Busy DB Sleeping 200ms issues go away.

Thanks for using Plex Meta Manager!
charred shadow
#

A full meta.log here where you let luma logscan give you recommendations can be insightful as well

#

Drop the log in here and click green box both times.

analog walrusBOT
#

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

#
**PMM Summary Info**

PMM Section Run Times: Top 10 sections sorted by duration (excluding run times of 0 seconds).

Finished at:23:05:20 2024-02-01 Run Time: 0:16:27 - 0:16:27

Page 3/13
grand summit
#

So i changed my config to remove episode ratings as suggested. Now when I run it, PMM crashes within three minutes each time. It shows this as critical:

#

| 3 | Item: Trakt Popular Labels failed to load |
| 1 | (500) internal_server_error; (redacted)/library/sections/1/all?includeGuids=1&type=1 <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |
| 1 | (500) internal_server_error; (redacted)/library/sections/4/emptyTrash <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |

analog walrusBOT
#

(500) internal_server_error detected in message, would you like to learn more about this error?

#
500 Internal Server Error

A 500 Internal Server Error happens when the server has an unexpected error when responding to an API request.

There could be any number of reasons why this happens and it depends on what server PMM is talking to although its most likely coming from your Plex Server.

Most of the time these errors need to be resolved by changing something specific to your set up but some do come up that can be fixed (i.e. Plex throws one if you upload a photo larger then 10 MB)

Many Appbox Setups will throw this error when too many requests are sent

Take a look at the following logs:

:one: Settings | Manage | Console -> then filter on Error and Warning to see what might be going on
:two: Check the plex logs (container or other) for the "Busy DB Sleeping for 200ms)

Thanks for using Plex Meta Manager!
grand summit
#

So this is now fixed I believe. There was in fact a corrupt DB in Plex so I repaired it and all is good.

#

Thank you for the help!