Server Version#: 1.22.0.4163-d8c4875dd (and others for past 3-4 months)
Player Version#: Latest Apple TV App Store version (and others for past 3-4 months)
Up until around Oct 2020 I’d had up to three remote users accessing my PMS on my QNAP TS-653B without any issues. Then my QNAP started suddenly rebooting randomly, up to twice a day. I initially thought it was the QNAP itself having issues, however after removing all 3rd party software, doing various hardware checks, then slowly re-adding software, I discovered that the issue only seemed to occur when Plex was streaming to a remote user (and this was consistent). Users were using Apple TV version of the app, not sure if that’s relevant or not.
I initially took this up with QNAP, as the NAS shouldn’t reboot, no matter how badly software behaves, but they’ve been unable to provide anything useful, they just keep asking for logs each time it happens. Each time it happened, it had a tendency to force the RAID to rebuild, so for a while I simply disabled remote access, however I’m now needing it again (hoping that recent updates might have fixed things), and hitting the same crash again.
Steps to reproduce:
1: Start PMS
2: Enable Remote Access
3: From remote location, launch Plex app and connect to my server
4: Start playing any video
Expected:
Normal playback
Actual:
After 10-15 minutes, QNAP server reboots
Would appreciate any help on this, it’s very frustrating!
Think the same thing is happening to me on my QNAP, its a TS-453B.
Remote Apple TV playback causes my QNAP to restart. 8gbs of ram from QNAP, ran ram test with no issues. Playback on Android Devices and Roku don’t cause the QNAP to restart.
Rolled back to 4.4.3, even redid the plex install, same thing. Same user with the Apple TV tried out running on his Fire Stick and didn’t run into issues.
I’ve also had this issue for going on a year now. 453Be 8GB of ram, various firmware versions. Only reboots when remote users are viewing. Not sure about player, might be older apple tv, will check. I read many qnap posts which alluded to a memory issue as well. Seemed like firmware updates from more than a year ago may have changed the way qnap handles some memory faults? I’ve rolled back to a firmware from 2019 and it seems to have “fixed” my issue, but not sure I’ll keep it that way, some other QNAP apps are out of date due to the older firmware, so I have to decide if I want to have remote access or up to date NAS
I have the same behavior occurring on QNAP TS-253B. Feels like it has been going on for about a year or so. I only have one remote user (Apple TV), and only play 1-2 hours per evening, but I get one consistent “unscheduled” reboot a week that requires a disk check every time. Hardware transcoding is definitely enabled.
Are there any other QNAP logs I can check for the panic or do I need to enable plex debug logging to check if it’s the same crash?
Would appreciate it if you could bring this up next meeting ChuckPA. Not a deal breaker on QNAP, but pretty annoying.
The QNAP QuLog Center app is the new portal for accessing the system logs.
( I prefer the old method but this will do , I guess ? )
If, upon booting, it doesn’t report that it crashed and why it crashed – red flag to qnap. It means they have a problem. All Linux kernels will generate a “panic” when it’s crashing. Those can be trapped as well as logged the post mortem evaluated after restart.
While not supported, think of when the firmware was stable and roll down to it if not crossing a major version boundry. (e.g. Don’t go from 4.5 to 4.3. ) Even crossing 4.5 to the last version of 4.4 is risky enough (app dependent)
It’d be too much to hope that anyone from QNAP attempted to get in touch with anyone from Plex to try and resolve this issue, right?
Any other suggestions on how to fix this? QNAP’s last response was basically “Get Plex to fix their crash”, which isn’t a lot of help.
QNAP TS-653B
All firmware versions since at least Oct 2020.
Just looking at the release history, 4.5.1 came out on the 15th of October, that’s suspiciously close to when I started seeing the issue (though I note that someone else here posted that it happened on 4.4.3 too).
I’ve been preventing remote access to avoid the crash, but will re-enable it and try to trigger it to get some logs for you, hang tight.
I did briefly try going up to 16GB before reading about that 8GB limitation, but dropped back to the original 4GB long ago. memtest doesn’t show any problems with it.
)
