After music scan completes, RAM usage spikes and NAS becomes unresponsive

Plex Media Server NAS & Devices
41

Yeah to be clear, the scan time itself is no longer the issue I’m concerned about. When I wrote this post originally there were a few issues I was experiencing. I believe the scan time issue is covered by this post.

The remaining issue, which is more concerning, is RAM usage leading to server lockup after the scan completes. Currently I cannot add music to my library without either a) a well-timed PMS restart to avoid the problem or b) a full Synology reboot, if I miss the window.

I updated the post title to reflect this.

42

Thanks.

How much RAM is in the Syno? Knowing a bit about the unit and what else it might be doing helps. While it’s not a solution to memory utilization, we might be able to mitigate the lockup a bit better until we get to the root cause.

43

Even now, with it all done scanning, My memory usage is very normal.

[~] # ps -ef | grep -i plex
13756 admin       952 S   grep -i plex
28901 admin    820120 S   ./Plex Media Server
28921 admin    426948 S N Plex Plug-in [com.plexapp.system] /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-ac2afe5f8/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.18.4.2171-ac2afe5f8 /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-ac2afe5f8/System.bundle
29081 admin      6188 S   /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Plex Tuner Service /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Tuner/Private /share/CACHEDEV2_DATA/.qpkg/PlexMediaServer/Resources/Tuner/Shared 1.18.4.2171-ac2afe5f8 32600 /waitmutex
[~] # free -m                                                                                                                                                                            
             total       used       free     shared    buffers     cached
Mem:         32099      31459        640        334       5029      21782
-/+ buffers/cache:       4646      27452
Swap:        32056        380      31676
[~] #

Linux will use free memory for disk buffering so don’t let the 640 scare you. Notice that only 380 MB of swap has been allocated.

44

I find that after adding new content the lyricfind agent runs for hours with a very high cpu usage. If I add a new album all my music content is scanned for lyrics. Which I don’t want, did you find a way to stop it?

Thanks

45

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