Server Version#: 1.20.3.3483
Premium User.
I installed PLEX on my QNAP NAS only with a lot of music on it
I get repeating errors and don’t know the reason.
see screendumps
I can’t find the answer in other topics.
How do I get rid of these errors piling up in the PLEX console
I’m also getting Error issuing curl_easy_perform(handle): 7 errors.
Oct 30, 2020 19:47:32.207 [0x7fe02b7fe700] DEBUG - HTTP requesting GET https://???-??-???-132.003fff277d5a42e8b19570298bd5e142.plex.direct:25379/identity
Oct 30, 2020 19:47:32.208 [0x7fe02b7fe700] ERROR - Error issuing curl_easy_perform(handle): 7
Oct 30, 2020 19:47:32.208 [0x7fe02b7fe700] WARN - HTTP error requesting GET https://???-??-???-132.003fff277d5a42e8b19570298bd5e142.plex.direct:25379/identity (7, Couldn't connect to server) (Failed to connect to ???-??-???-132.003fff277d5a42e8b19570298bd5e142.plex.direct port 25379: Connection refused)
(Question marks added for privacy, but happy to DM addresses to people)
It says connection refused in there, but this is sporadic, and sometimes works, and sometimes doesn’t.
I’m not sure if I’ve changed something in the past week or so, but it’s pretty frustrating suddenly not being able to connect reliably to the server from elsewhere…
STILL NOT SOLVED !
IS THERE A SOLUTION?
Where are the PLEX specialists?
This is a PMP issue. I’m not a player guy per se and do not use PMP but ----
Most importantly, we cannot debug from screenshots unless those screenshots show grievous errors. These are more involved and do require a full set of DEBUG logs ZIP file which captures them.
(File removed)
additional information:
no DLNA
no scheduled tasks
Please restart PMS,
Allow to sit completely idle for 5 minutes
Download the Logs ZIP file
Post that ZIP file here.
Show , using Resource Monitor → Processes, the memory used by each of the PMS-related processes. (screenshot)
I’ll do this tomorrow. My RAID is synchronising because I restarted the NAS. takes several hours…
When I created this new topic about high memory usage I was unaware that the other topic was being blocked!
I have a lot of problems with PMS running only for my music database …
I have a feeling that they are all linked but I can’t see what is causing these problems like XML errors, a lot of memory usage and so on.
So I hoped that opening a new topic with a relevant new title like Excessive Memory usage could indicate someone to help me finding a solution.
Sorry for the used language, but I’m a bit desperate having to restart several times a day PLEX just to listen to my music, adding music or correcting the multimediadata.
I thought there would be some kind of PLEX support and not only a forum. I read a lot of topics, all ending with “closed after 3 months” and without a solution. Perhaps a PLEX support could bring a solution?
I hope the PLEX problems will disappear, and so will I.
Have a nice day/evening!
That indicates that your QNAP was not shut down in a proper way, and could lead to database corruptions
In fact I didn’t restart the NAS myself, but the NAS restarted after a crash caused by PLEX.
I was adapting some of the metadata of the music (mostly uploads of covers and merging files)) and then all slowed down, PLEX blocked (no access) and NAS RAM exceeded 12Gb and NAS processor >80% occupied by PMS. Then the NAS crashed…
Using PLEX for playback of the music doesn’t give so much problems. Playback is ok on all audio systems (phone, tablet, laptop, TV, Alexa, …) and everywhere.
have you installed memory in it?
yes, years ago → 16Gb usable
Well…
You’ve exceeded it and it, like all other J-series CPUs, no longer tolerates it.
This is a recent trend with QNAP. Apparently their kernels have become very strict and unforgiving.
Other cases like this (TS-453Be is one) where the machine stopped rebooting daily immediately after installing the proper 2x 4GB DIMM configuration.
OK!
at that moment I’ve read that I could try to put in 2x8Gb
and it worked without a problem
could this now cause this misery?
I’ll put in the old RAM and we’ll see if this cures the problem
thanks for letting me know!
As long as you have : 2x 4GB at maximum then you’re good. It won’t crash.
What’s going on is the kernel doesn’t know there aren’t any address lines on the motherboard for the extra gigabytes
What ends up happening is the kernel assigns those higher addresses but, when the CPU goes to write, it goes to the wrong addresses ( at the 2 GB block instead of the 6 GB block – as example) and 
I removed one of the two 8Gb Ram.
Now I’m working with an NAS having only 8Gb, but still the same problems with PLEX.
I have a large music database. All music is recognised and appears on PLEX, but some metadata is faulty and some albums appear twice (because they were kept on two locations) and some albums need merging because the disc’s are shown separately.
Correcting these faults step by step, and lookig at the NAS CPU load and Memory usage shows that especially the updates of the wrong metadata augment the memory used by PLEX. And this quantity doesn’t drop but increases till PLEX tells me “There was an unexpected error loading this library” and PLEX is unaccessible. Even the PMS settings are unavailable, no trouble shooting then. The NAS tells me that the PLEX CPU usage is low, but PLEX Memory usage > 6Gb!
For the moment I still have access to the NAS, but at times PLEX and the NAS are blocked. Then I restart the PLEX server or NAS+PLEX.
So, this is not the solution I hoped for, snif…
Not saying it’s a RAM issue or not, but do say, that 2 * 4Gb is NOT the same as 1 * 8Gb, when it comes to supported RAM configuration
OK, I’ll try the 2x4Gb ram configuration. I’ll get these RAM’s by tuesday.
FYI: the original configuration when I bought this NAS was 1X2GB .
If you do the math in powers of 2 ( 2^n )
4 GB = 2^32
QNAP created the motherboard with 32 address lines.
To support an 8GB module, we need 33 address lines.
The board doesn’t have that many.
The OS doesn’t know that so that’s why it crashed / overwrote part of itself when it tried to use more than what it could uniquely address.
Same problem with 2x4Gb …
PLEX memory usage piles up to 6,3Gb when I use PLEX or adapt metadata or delete albums.
Even when I stop PLEX in the NAS, the 6,3Gb is still there. CPU usage declines to 0.
Only when I restart the NAS after stopping PLEX, the memory gets normal again.
