#PMM Abruptly Stops without Error
1 messages Β· Page 1 of 1 (latest)
I see you attached a file πmeta.logπ. Would you like Luma to parse that for you and make some recommendations? Default value of No/Red X will be selected after 180 seconds.
Welcome Back @dapper locust!
Thanks for being a PMM Sponsor, we greatly appreciate it! Your ticket will now be diverted to <@&1097919568334311495> and <@&938443185347244033>.
Please provide any logs if you think they're relevant to your post.
You can press the "Close Post" button above or type /close at any time to close this post.
β° PMM SCHEDULED TIME RECOMMENDATION:
PMM Scheduled start time: 5:00
Plex Scheduled Maintenance start time: 6:00
Plex Scheduled Maintenance end time: 9:00
Change PMM start time to 9:00, a time outside of Plex maintenance times. Currently, there is a 60 minute buffer before the next Plex maintenance at: 6:00. By changing PMM start time to 9:00, you will have a 21 hours buffer until the next Plex maintenance.
One possibility is that your run time for PMM is hitting the Plex maintenance period and then things go wrong as the db and Plex are being hammered
Typically Plex maintenance is 2-5am
Changing that would also work as per recommendation
And you only have 4GB of RAMβ¦. And not sure how large your libraries are
Ive messed around scheduled tasks timing thinking that was the cause. However this problem hits whether i run in the early hours or afternoon. However i don't run into this issue when i run libraries separately.
Memory then
If it ends abruptly like that, it's typically being killed by an external force, and the most common is an out-of-memory condition.
Can you allocate more ram?
If it was a RAM issue would i expect to see an error or this . This runs on a VPS i can scale up the RAM if it might help.
You won't see such an error in the PMM log, since it just gets killed, not asked to stop.
Memory may not be the specific cause, but it's a common one. If PMM were seeing a critical error and exiting, that would be in the log.
Agh makes sense. Ill scale up and run again see if it cures it. If not ill report back. Thanks guys really appreciate it.
Move to 8GB if possible
@dapper locust any luck or update for us?
I upgraded to 8GB; Ive ran twice both ended successfully. So seems to be all good now. Thanks again.