Help! PMS is down multiple times per day!

Plex Media Server Desktops & Laptops
1

Server Version#: 1.29.1.6276-4a96dd5b1 (the current version?)
Player Version#: n/a
Plex Media Server Logs_2022-10-16_22-27-36.zip (4.9 MB)

I’m running Windows 11 Pro (ver. 22H2 OS Build 22621.674). I’m also running Sonarr, Radarr, and Prowlarr in conjunction with PMS. These last are a relatively recent addition to my collection building tools, but the issue I’m having started before the addition of these into my work flow.

I’ve attached my log files because I am most definitely not a programmer. All I know is that I can’t seem to keep my PMS up and running for more than a few hours at a time. The family members I’ve shared it with will message me letting me know its down, but if I’m at work, it’ll just be down until I can get back home to restart the app on my Windows machine. Once I restart it, everything is fine right up until the next time that it is not.

From a user perspective, I constantly see the PMS icon in my system tray letting me know it’s up and running. When I get one of the notices from my family, I log into the machine and it appears to be working fine. However, when I move my mouse over the PMS icon in the system tray, it just disappears the instant my mouse hits it. I relaunch the app and I’m back up and running.

Can anyone help me out with what might be causing this?

Immediately after sending this message I’m going to Optimize my Database and Clean my Bundles. That’s the only thing I can think of that might be causing some of this.

Also, I don’t know if it can be identified from the Server Version #, but I am running the 64 bit version of PMS. I don’t know if that has something to do with it or not. Is the 64 bit version a stable release? I assumed it was since it was available for “upgrade” via the Plex website…

Anyway, thanks in advance for any help you might be able to offer!
Tee

1 Like
2

I have almost the same issue. The difference is that the PMS software does not crash, but the server and libraries are shown as offline. After a restart of the server, things are back to normal. Logs are attached.
Plex Media Server Logs_2022-10-17_19-36-07.zip (2.9 MB)

3

UPDATE: Unfortunately, the issue is still happening, but I have narrowed it down to the “Scan Library Automatically” setting and/or “Run a partial scan when changes are detected” setting.

I originally thought this was connected to a trigger coming from Radarr, but after doing a little trial and error, I realized that it was not. Radarr is currently not triggering anything regarding PMS. This evening, I tried to change the settings to “Scan library periodically (Every 2 Hours)” and I’m currently waiting to see if that’s going to trigger the freeze-up again.

Is anyone else having this issue with the 64bit version of PMS (btw, I updated the version this morning, too) and Windows 11?

4

Could you get me a copy of your Plex Media Server database
The logs show a syntax error in a database query the server did

Oct 16, 2022 19:00:55.455 [6032] DEBUG - Push: There are 3 new top level things for filter 'contentRating!=XXX%2Cxxx&label!=NSFK' (movie.addedAt>>=1650483277&sort=movie.addedAt:desc&type=1).
Oct 16, 2022 19:00:55.456 [6032] DEBUG - Push: There are 3 new top level things for filter 'contentRating!=xxx%2CXXX%2CX&label!=NSFK' (movie.addedAt>>=1650483277&sort=movie.addedAt:desc&type=1).
Oct 16, 2022 19:00:55.457 [6032] DEBUG - Push: There are 3 new top level things for filter 'label!=NFJ%2CNSFK' (movie.addedAt>>=1650483277&sort=movie.addedAt:desc&type=1).
Oct 16, 2022 19:00:55.458 [6032] DEBUG - Push: There are 3 new top level things for filter 'contentRating!=NFJ%2Cxxx%2CX&label!=NSFK%2CNFJ' (movie.addedAt>>=1650483277&sort=movie.addedAt:desc&type=1).
Oct 16, 2022 19:00:55.459 [6032] DEBUG - Push: There are 1 new top level things for filter 'contentRating!=X%2Cxxx%2CNot%20Rated%2CNR&label!=NSFK' (movie.addedAt>>=1650483277&sort=movie.addedAt:desc&type=1).
Oct 16, 2022 19:00:55.459 [6032] ERROR - SQLITE3:0x7ff6e7b0c4e0, 1, near ")": syntax error in "select distinct metadata_items.id from metadata_items  where metadata_items.library_section_id in (14) and ((metadata_items.added_at>1650483277 and metadata_items.metadata_type=1) an

To download the database use the same plex web interface as downloading the logs

Please upload the database zip on dropbox / google drive etc and send me a link by private message

thanks

5

You have a database corruption

There is evidence of running multiple instances of Plex Media Server at the same time - this could lead to corruptions and other indeterminate outcomes

Do you run Plex Media Server as a scheduled task or windows service ? May be it is running in this mode but you also have auto start on login enabled and end up with two sessions running

Logs show
One session started at

Oct 17, 2022 17:35:19.549 [6600] INFO - Plex Media Server v1.29.0.6244-819d3678c - Microsoft PC x64 - build: windows-x86 windows - GMT 02:00
Oct 17, 2022 17:35:19.551 [6600] INFO - Windows version: 10.0 (Build 19043), language da-DK
Oct 17, 2022 17:35:19.551 [6600] INFO - 4 3500 MHz processor(s): Architecture=0, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
Oct 17, 2022 17:35:19.551 [6600] INFO - Compiler is - MSVC 1929
Oct 17, 2022 17:35:19.551 [6600] DEBUG - "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe"

and running all the way to

Oct 17, 2022 19:36:06.413 [7692] DEBUG - [Req#ca5] Diagnostics: Building logfile zip

and in parallel to this you had another session starting at

Oct 17, 2022 17:35:28.311 [10564] INFO - Plex Media Server v1.29.0.6244-819d3678c - Microsoft PC x64 - build: windows-x86 windows - GMT 02:00
Oct 17, 2022 17:35:28.311 [10564] INFO - Windows version: 10.0 (Build 19043), language da-DK
Oct 17, 2022 17:35:28.311 [10564] INFO - 4 3500 MHz processor(s): Architecture=0, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
Oct 17, 2022 17:35:28.311 [10564] INFO - Compiler is - MSVC 1929
Oct 17, 2022 17:35:28.311 [10564] DEBUG - "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe"

and running in parallel to

Oct 17, 2022 19:35:45.606 [10832] DEBUG - MyPlex: Last published value didn't change, we're done.

If you do run it as a service / scheduled task, I would recommend using the solution offered here PMS as a service - General Discussions / Tips, Tricks & How-Tos - Plex Forum and when you do run it as a service - make sure the auto start on login is disabled - you can check the registry setting for it - see this post in that topic PMS as a service - #4 by sa2000

Once you resolve the multiple instances issue - then you can look into repairing the database / restoring from a backup - see Repair a Corrupted Database | Plex Support

1 Like
6

The latest beta - PMS version 1.30.1 has a fix for the crashes - but we still have not identified the cause the of the SQLITE3 syntax error that was leading to your crashes

See release note for the crashes fix

  • (Database) Server might quit unexpectedly after SQLite3 syntax errors (#13942)
7

Hey guys,

I’d like to chime in on this one, as I’m seeing a lot of server crashes a day on PMS version 1.30.1.6497, but only if I’m adding music, e.g. if sonic analysis and loudness analysis are running. If those tasks are running, PMS crashes without any sign between 3-6 times in a few hours, which is pretty frustrating.

In case you need any logs or something from me I’ll be happy to provide

8

There is an issue relating to loudness analysis for albums leading to crashes if there is some abnormalities in the database - I can check this out if you get me debug server logs after a crash and also zipped download of the database - this issue is being progressed here Plex Media Server Crashes Overnight Since Update: 1.30.1.6483 - Plex Media Server / NAS & Devices - Plex Forum

9

Hey there @sa2000,

Thank you very much for guiding me to the main topic. I’m currently at work, so I cannot send you logs and my db right now, but I would highly appreciate if you could provide me with PMS version 1.30.2 later or so, as I have a bunch of albums to be added to the server but I refrained as I already suspected loudness analysis to be the culprit for this.

Would be great if I could get the new server version too to not have those daily crashes.

Best wishes and a great day

10

I am only making 1.30.2 available for cases where I have seen the database and logs - as I try and gather examples of the database issues and when they arose

11

Yeah sure, completely understandable and I will provide you with logs and db as soon as I’m back home. Do I send those in a pm? Or here?

12

Okay I just read through the thread you linked to this thread. You need the zipped databases and the Plex server logs right after a crash, correct?

Also noticed that you want those via pm. Will provide this evening :slight_smile:

14

I got your database. It does not show the issue that I referred to - the one that leads to crashes when scheduled tasks run music loudness analysis

Your issue is different from the one relating to music loudness analysis. I would need the debug server logs to start an investigation and identify which dmp files to look for

15

As I said in the private message, I’m not a 100% sure if it’s the same issue, but it pretty much sounds like the exact same thing the others are reporting. Please bear with me, as I currently can’t add music too quickly as there’s other stuff going on.

Is there a way to manually re-trigger loudness generation for an item that does have loudness analysis data already?

Because I’ve run a media analysis task for my entire music library, but I think all my music already has loudness data (After like 25 crashes though, but I’ve been stubborn :smiley: )

So without adding music to the server, which might take a few mintues, I don’t know how to reproduce the crash

EDIT: I’m dumb. I’ll simply place some already scanned folders outside of the paths scanned by Plex. Brb

16

There you go, it crashed upon sonic analysis/loudness generation. Will provide db and logs now :blush:

17

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.