Plex diabled nightly by Qnap Memory issue

General Discussions
1

Happens around 4AM every nightPlex Media Server Logs_2021-11-02_14-24-22.zip (4.1 MB)

Message: [System Message] PlexMediaServer has been automatically disabled by QTS to free up system memory.

App Name: Hardware Status
Category: Kernel
Message: [Hardware Status] NAS out of memory. Started kill process: 27117 “Plex Media Serv”. Disable some applications to free up memory, or expand the system memory.

Have to go in and restart Plex

Qnap has 16 gigs of memory been working fine for years.
Qnap TS-453A QTS 5.0.0.1828
Plex Version 1.24.5.5173

2

QTS 5.0 is the new variable here.

I’ve not seen out of memory errors but with QTS 5.0 being new – anything is possible.

Do you have the logs from when it was terminated ?

3

I attached the plex logs previously here is the qnap log I did not turn Plex back on yesterday but it happened all of the previous nights. Q15BI09038.zip (3.4 MB)

4

@nestmg1

We can’t read QNAP logs

You probably should

  1. Create a shared folder named PlexData (exactly as typed) anywhere you want

  2. Restart Plex

  3. Let it run a minute

  4. Stop it

  5. Open FileStation

  6. Navigate : PlexData / Plex Media Server

  7. Right-click Logs → Compress

  8. Download the ZIP file

  9. Attach here

5

I tried several times and the folder is empty. Here is the log files I attached origionally.Plex Media Server Logs_2021-11-02_14-24-22.zip (4.1 MB)

6

@nestmg1

  1. Please make certain the shared folder capitalization is as I show PlexData. My scripting tools are dependent on capitalization.

  2. Once you get that solved, Please stop plex and add this to Preferences.xml (Preserve spacing with other options)

LogMemoryUse="1"

  1. It will allow us to track what PMS is seeing for memory usage as part of your logs.

  2. We are closing in on the memory issue. It’s starting to look like it occurs when “Refresh All Metadata” occurs (which happens in maintenance) and the database contents satisfy a specific type of records…

7

Sorry took a little bit to figure outlogs.zip (5.6 MB)

8

@nestmg1

Thank you for the logs.

If I may recommend,

  • You are updating from version 0.9.15.3
    Aug 27, 2016 17:26:36 [0xf2911b90] INFO - Plex Media Server v0.9.15.3.1674-f46e7e6 - debian PC i686 - build: linux-debian-i686 qnap

  • to 1.24.5
    Nov 05, 2021 09:42:43.823 [0x7f1887cd7b38] INFO - Plex Media Server v1.24.5.5173-8dcc73a59 - QNAP TS-453A x86_64 - build: linux-x86_64 qnap - GMT -05:00

  • That’s a HUGE jump.

PLEASE be patient with it. I see you were stopping and starting it while it was trying to complete working on the database upgrades.

I don’t know what this might have done to it.

What status is the machine in now?

Did you add the preference? I don’t see it in your logs yet.

9

I hopefully have this right now. I attached the logs and also included the preferences file hopefully I added the linne correctly. Also attaching a image if the qnap upgrade packages that I have ran. Generally I only stop and start the server if it is unresponsive.logs (2).zip (5.8 MB)

qnap upgrades
qnap upgrades890×177 7.49 KB

10

If you look here –

Nov 05, 2021 09:43:06.281 [0x7f1884950b38] DEBUG - [Notify] Now watching "/share/CACHEDEV1_DATA/Multimedia/HDHomeRunDVR/Best of Feast TV (2019)/Season 2020"
Nov 05, 2021 09:43:06.294 [0x7f1884950b38] DEBUG - [Notify] Now watching "/share/CACHEDEV1_DATA/Multimedia/HDHomeRunDVR/Best of Feast TV (2019)/Season 2019"
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Completed forward migration 20190528190600.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Running forward migration 20190520131301.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Captured session 0.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Captured session 1.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Captured session 2.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Captured session 3.
Nov 05, 2021 09:43:06.300 [0x7f1884f34b38] DEBUG - Captured session 4.
Nov 05, 2021 09:43:06.307 [0x7f1886090b38] DEBUG - HTTP/1.1 (0.2s) 200 response from PUT https://plex.tv/api/servers/c2e47ed4083398f600ca11f7335ef1e7c882cb13/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=34dd14f6-c064-40a9-950d-3bd911f4150f (reused)

Forward migrations from 2019. It’s still catching up.

How vested are you with the server data (watch history) you have ?

11

Chuck the TS-453a is also another model that technically only supports 8 gig of ram and I see he has 16, something to consider.

As I am sure you recall several firmware upgrades had caused ram issues even after years of working because of ram compatibility with the firmware.

12

@skwor01

Thank you for catching that. (it’s been a long week and I missed it)

@nestmg1

You can’t put more memory in a QNAP than it supports. They blow up (crash).

The motherboard does not support all the addressing pins required.

13

Not invested at all in watch history. I have the origional 8 gigs of ram and can put that back in?

14

Please do put the original 8GB back in.

Let’s confirm the machine is stable and behaving as it should.

You can repurpose the 16 GB for something else since the QNAP can’t use it.

15

I put the RAM back in and everything seems to be working fine. Guess will see if there are any errors in the morning.

16

After replacing the RAM on Sunday there has been no issues with Plex or the NAS.

1 Like
17

Just a follow-up and future reference. The changing of your ram back to the vendor specs, using approved QNAP ram fixed this issue? No more problems since your last post?

1 Like
18

Plex has been working fine since replacing the ram.

19

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