Minimserver using 100% CPU on QNAP NAS

[schliden]

Hi,

I have been using minimserver for many years..

I have NOT made any changes (neither updated minimserver nor nas) but minimserver appears to be using 90-100% of NAS CPU all of a sudden.

I have rebooted the NAS and minimserver starts and runs, but continues to use CPU heavily.

top

11881 admin S 40M 11879 79.6 8.1 java

ps -ef | grep java | grep -v grep

11881 admin 41864 S /usr/local/jre/bin/java -Duser.timezone=Australia/Melbourne -jar ../lib/mserver.jar --launchrc --noconsole --nohup

When I stop minimserver, NAS CPU use falls to normal levels ~15-20%

Is there a way to determine what might be causing this ?

Thanks

[schliden]

(26-12-2025 01:50)schliden Wrote:  Hi,

I have been using minimserver for many years..

I have NOT made any changes (neither updated minimserver nor nas) but minimserver appears to be using 90-100% of NAS CPU all of a sudden.

I have rebooted the NAS and minimserver starts and runs, but continues to use CPU heavily.

top

11881 admin S 40M 11879 79.6 8.1 java

ps -ef | grep java | grep -v grep

11881 admin 41864 S /usr/local/jre/bin/java -Duser.timezone=Australia/Melbourne -jar ../lib/mserver.jar --launchrc --noconsole --nohup

When I stop minimserver, NAS CPU use falls to normal levels ~15-20%

Is there a way to determine what might be causing this ?

Thanks

After much testing, it appears that it was a large playlist causing the issue (I hope).

Admittedly, it was rather large, many 1000's of lines .m3u..

Is there a practical limit (and or suggested maximum) to the size of m3u playlists ?

* Also, after removing the loaded playlist from the UPnP Controller, I needed to stop and restart minimserver on the NAS to reduce the CPU use... (Would it recover naturally or is this stop/restart required ?
)

[schliden]

It appears I spoke to soon.. The java process has pegged the NAS CPU again, this time with a tiny playlist..

Any ideas how I can troubleshoot ?

[simoncn]

The first step for troubleshooting this and any other unexpected behaviour is to check the MinimServer log file for error or warning messages. To find the location of the log file on your NAS, see this section.

A high CPU load usually means MinimServer is rescanning your library. If MinimServer is doing a full rescan and the library is large, the high CPU load might continue for some time. If the status shown on the MinimServer configuration status page is Rescanning, this means a rescan is in progress. If you stop and restart MinimServer while a rescan is in progress, the rescan will start again from the beginning.