Crashing every day on QNAP

Over the last month possibly more, most days the server is not running when I wake up in the morning and I need to manually restart it on the QNAP management UI. Running QNAP 4.4.3.1421 latest with latest PMS. Have looked through these logs but I don’t see the actual crashes so not sure how these work. I assume it’s related to DVR stuff. Attached.

Server Version#: 1.20.1.3252
Player Version#: Not Applicable, server crashPlex Media Server Logs_2020-09-25_21-19-00.zip (4.4 MB)

This still happens every day at least once. I thought this was the way to submit issues, but I guess it may take a long time? Meanwhile, is there some way to watchdog the server and just restart it automatically? This seems like a really basic issue that you’d always want to keep the server running.

I’m sorry, This is the place to come.

I have been swamped with other issues. I do the best I can but it takes time.

Thanks for providing your logs with your OP.

I will review now and reply.

Which QNAP NAS do you use?

@cyphersoft

Thanks again for providing the logs.

I am not seeing any direct crash but I see DVR activity and then I see a restart.
Do you know if you are missing any DVR recordings?

I did find something in your logs which shouldn’t happen with this CPU.

Sep 25, 2020 21:18:37.381 [0x7f24518e2700] DEBUG - Completed: [192.168.7.226:60128] 200 GET /web/js/chunk-5-3ee08078895dfbdf0b07-plex-4.34.4-7d609a3.js (9 live) GZIP 40ms 998957 bytes (pipelined: 1)
Sep 25, 2020 21:18:37.384 [0x7f2439fc5700] WARN - SLOW QUERY: It took 250.000000 ms to retrieve 10 items.
Sep 25, 2020 21:18:37.399 [0x7f2451ebe700] DEBUG - Destroying metadata item 15651 (More in Common)

Please go to Settings - Server - Scheduled Tasks - Show Advanced.

Make certain to allow Database Optimization (enable it) during maintenance.

For now, please go to the main “Library” pane (Left side)
Hover over it to expose the ellipsis where you would add a section.
Click into it and “Optimize Database”.

This will make it optimize now and speed things back up a bit.

I’ll try to grab logs later but I’ve also been seeing lots of crashes in the last month, and it never crashed for me before.

TS-453Be
4.4.3.1381 Firmware 20200729

Just updated Plex today to latest.

FYI this seemed to start after updating to the version that requires the PlexData share

Unfortunately, this morning the server was dead again. I did perform the Optimize Database step on 9/30 as you recommended. I also upgraded the server this week to 1.20.2.3402 so the crashing may have been reduced as I’ve only now had 1 incident during that time, but it is definitely still there. I’ve attached the current crash logs here.
Plex Media Server Logs_2020-10-10_08-05-42.zip (4.9 MB)

I see where it crashed twice during DVR recording.

From what little bit I understand of DVR ( I can’t use DVR because I don’t have cable or OTA television ), it’s trying to arbitrate for the scheduled recordings and not succeeding. (over commitment of tuners).

Granted it shouldn’t crash but does this make any sense to you?
e.g Time of crash -vs- schedule recordings which conflict ?

I deleted one of the scheduled recordings last night, but then the server was dead this morning again. I’m not sure how I would be able to figure out which recording is causing a problem – without just turning off DVR altogether. As far as the schedule viewable in the DVR section, there are no overlapping recordings.

would you mind going into your qnap (ssh into it).

At the command line, run dmesg (which will dump the system log)

After it’s dumped to the terminal window, scroll backwards through it.

I don’t even use DVR and found this – which is a problem

[975311.832254] Plex Tuner Serv[22206]: segfault at 58 ip 00007f54ed70e8a4 sp 00007f54e7cef1f0 error 4 in libpthread.so.0[7f54ed705000+18000]

Yes, I have a ton of those. Here are 4, but I have like 30 or so.

[1781061.522097] Plex Media Serv[32608]: segfault at 120 ip 000000000124c88f sp 00007f54e688e610 error 4 in Plex Media Server[99c000+e5c000]
[1781061.539486] Plex Media Serv[8205]: segfault at 158 ip 00000000009daf5e sp 00007f54e4e2fed0 error 4 in Plex Media Server[99c000+e5c000]
[1975461.354600] Plex Media Serv[31852]: segfault at 158 ip 00000000009daf5e sp 00007fa2790cf230 error 4 in Plex Media Server[99c000+e5c000]
[2040261.309163] Plex Media Serv[9272]: segfault at 158 ip 00000000009daf5e sp 00007f6bee2b2230 error 4 in Plex Media Server[99c000+e5c000]

Excellent. That’s the start.

Please make sure Crash Upload is turned off.

When it next crashes, there will be a DMP file in the Crash Reports directory.

If you would please attach that file (in a ZIP)
with the logs,
I can look and find out exactly where it’s crashing.

whatever’s happening , it’s predictable.
If it’s unique to you, I hope seeing where it’s crashing points us at the problem AND allows me to file a bug report

Any updates on this I am having the same issue, it crashes regularly I have to go in stop/start Plex for things to start working again. My error messages in dmesg are virtually identical to the ones posted by @cyphersoft . Also on a Qnap NAS TS-877 with everything up to date.

@kingfriday

Please also follow my instructions to capture and upload a DMP file from a crash so I can see where the error is occurring.

Sure I did most of the earlier steps before posting message, will upload DMP file next time is stops being accessible. I did not see an option to turn off “Crash Upload” but will just ssh into machine and look for the file.

@kingfriday

Settings - Server - General - Show Advanced.

Disable Crash Report uploading.

I attached the Plex logs zip file and the second zip contains the most recently modified file in the “Crash Reports” directory. (File removed) (File removed)

@kingfriday

I will look at this over the weekend.

In the interim: PLEASE TURN OFF VERBOSE loggging.

Debug logging = YES
Verbose logging = NO
:slight_smile:

You’re only making my job tougher. Verbose logging is only needed in the most extreme of cases. Too much data is lost otherwise because it logs EVERY packet exchange in mind-numbing detail.

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