So I am brand new to the Synology NAS world and just recently purchased a DS718+. I have used Plex for about a year and was running my server for me and a few friends to use remotely from my Nvidia Shield TV which worked well for what we used it for. I just setup the plex server on my NAS unit and seem to have trouble with it staying visible on my server list. At first I thought it was due to the non-static IP so I adjusted that and set up the conditions in my router along with providing port forwarding which seemed to solve the problem of it not being able to be accessed remotely. However, now the server will randomly not show up in my list of options after a while yet the package is still shown up as running on my DS718+ and is using a decent amount of RAM even when no one is connected and streaming anything. The only way to solve this is to stop the process and start it back up again. Am I missing something in the setup process to allow for longer use without crashing and not having the DLNA server using 1GB+ of RAM when no one is connected? I provided some of my logs as well so any help is appreciated. I am still learning a lot about the Network world and getting more into the uses of Plex and NAS
It doesn’t seemed to have crashed on my home network yet but is there a reason the Synology NAS RAM usage stays so high even when no one is streaming/currently using the Plex Media Server? The DLNA Server seems to be what is constantly in use. Plex Media Server Logs_2018-08-04_11-47-22.zip (5.6 MB)
From your logs, something is making a lot of queries of the database.
Aug 04, 2018 05:27:22.283 [0x7f8071b68700] INFO - /var/packages/Plex Media Server/target/Plex Media Server
Aug 04, 2018 05:27:22.283 [0x7f8067e23700] DEBUG - Streaming Resource: Usage: 0kbps of WAN bandwidth, 0 streaming transcode slots, and 0 static transcode slots across 0 sessions
Aug 04, 2018 05:27:22.292 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 141 items.
Aug 04, 2018 05:27:22.301 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 102 items.
Aug 04, 2018 05:27:22.318 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 141 items.
Aug 04, 2018 05:27:22.327 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 115 items.
Aug 04, 2018 05:27:22.337 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 123 items.
Aug 04, 2018 05:27:22.347 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 131 items.
Aug 04, 2018 05:27:22.368 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 179 items.
Aug 04, 2018 05:27:22.387 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 155 items.
Aug 04, 2018 05:27:22.397 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 120 items.
Aug 04, 2018 05:27:22.409 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 170 items.
Aug 04, 2018 05:27:22.427 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 135 items.
Aug 04, 2018 05:27:22.436 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 127 items.
Aug 04, 2018 05:27:22.445 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 111 items.
Aug 04, 2018 05:27:22.458 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 161 items.
Aug 04, 2018 05:27:22.474 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 107 items.
Aug 04, 2018 05:27:22.484 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 130 items.
Aug 04, 2018 05:27:22.500 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 126 items.
Aug 04, 2018 05:27:22.525 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 141 items.
Aug 04, 2018 05:27:22.541 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 105 items.
Aug 04, 2018 05:27:22.572 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 101 items.
Aug 04, 2018 05:27:22.586 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 198 items.
Aug 04, 2018 05:27:22.596 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 131 items.
Aug 04, 2018 05:27:22.619 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 221 items.
Aug 04, 2018 05:27:22.629 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 125 items.
Aug 04, 2018 05:27:22.641 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 153 items.
Aug 04, 2018 05:27:22.651 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 128 items.
Aug 04, 2018 05:27:22.660 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 101 items.
Aug 04, 2018 05:27:22.670 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 131 items.
Aug 04, 2018 05:27:22.685 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 211 items.
Aug 04, 2018 05:27:22.695 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 132 items.
Aug 04, 2018 05:27:22.706 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 134 items.
Aug 04, 2018 05:27:22.717 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 144 items.
Aug 04, 2018 05:27:22.731 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 206 items.
Aug 04, 2018 05:27:22.747 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 225 items.
Aug 04, 2018 05:27:22.759 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 172 items.
Aug 04, 2018 05:27:22.771 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 155 items.
Aug 04, 2018 05:27:22.783 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 140 items.
Aug 04, 2018 05:27:22.795 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 153 items.
Aug 04, 2018 05:27:22.805 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 136 items.
Aug 04, 2018 05:27:22.821 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 102 items.
Aug 04, 2018 05:27:22.832 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 139 items.
Aug 04, 2018 05:27:22.845 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 185 items.
Aug 04, 2018 05:27:22.862 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 110 items.
Aug 04, 2018 05:27:22.872 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 133 items.
Aug 04, 2018 05:27:22.882 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 122 items.
Aug 04, 2018 05:27:22.899 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 104 items.
Aug 04, 2018 05:27:22.909 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 134 items.
Aug 04, 2018 05:27:22.919 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 121 items.
Aug 04, 2018 05:27:22.930 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 152 items.
Aug 04, 2018 05:27:22.942 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 155 items.
Aug 04, 2018 05:27:22.953 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 164 items.
Aug 04, 2018 05:27:22.966 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 165 items.
Aug 04, 2018 05:27:22.978 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 150 items.
Aug 04, 2018 05:27:22.989 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 143 items.
Aug 04, 2018 05:27:22.999 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 125 items.
Aug 04, 2018 05:27:23.010 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 159 items.
Aug 04, 2018 05:27:23.021 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 160 items.
Aug 04, 2018 05:27:23.031 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 127 items.
Aug 04, 2018 05:27:23.043 [0x7f806726b700] DEBUG - It took 0.000000 ms to retrieve 157 items.
Aug 04, 2018 05:27:23.053 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 132 items.
Aug 04, 2018 05:27:23.063 [0x7f806726b700] DEBUG - It took 20.000000 ms to retrieve 130 items.
Aug 04, 2018 05:27:23.075 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 177 items.
Aug 04, 2018 05:27:23.093 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 120 items.
Aug 04, 2018 05:27:23.119 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 116 items.
Aug 04, 2018 05:27:23.128 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 112 items.
Aug 04, 2018 05:27:23.138 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 120 items.
Aug 04, 2018 05:27:23.165 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 146 items.
Aug 04, 2018 05:27:23.174 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 104 items.
Aug 04, 2018 05:27:23.184 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 126 items.
Aug 04, 2018 05:27:23.193 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 109 items.
Aug 04, 2018 05:27:23.210 [0x7f806726b700] DEBUG - It took 10.000000 ms to retrieve 111 items.
Aug 04, 2018 05:27:23.621 [0x7f8070111700] DEBUG - Completed: [127.0.0.1:34414] 200 GET /library/metadata/132,133,359,137,325,141,184,18,147,146,144,352,152,256,55,40,283,252,371,202,103,307,109,73,50,193,306,308,309,310,311,313,312,24,25,243,346,37,248,126,204,52,53,93,315,304,354,327,56,316,170,250,241,59,77,28,269,337,105,3,4,62,118,189,112,63,353,257,242,8,92,255,357,125,15,104,169,16,17,201,228,217,215,212,214,213,3448,344,272,271,203,351,321,263,33,99,324,34,107,247,121,190,30,246,127,251,101,87,36,102 (4 live) GZIP 1640ms 329279 bytes
This goes on and on.
Do you have any DLNA-enabled devices?
If it’s the DLNA server and you don’t need or want it, you can turn it off. Settings - Server - DLNA
I don’t believe I do. I know I don’t and I do not believe any of my friends do so I will try this and see if that fixes the issue. Thanks for the quick response.
Even if I did, should it be making that many queries while not running?
Do you have any Plug-ins which monitor / scan / otherwise perform automated tasks for you?
I’ve done more looking through your logs.
There appears to be two devices which advertise on your LAN. A DLNA -enabled receiver (my Onkyo is)
The IP’s of interest: 192.168.1.9 (port 8060) and 192.168.1.10 (port 9080)
Aug 04, 2018 04:34:27.367 [0x7f80583c5700] DEBUG - HTTP requesting GET http://192.168.1.9:8060/
Aug 04, 2018 04:34:27.373 [0x7f80583c5700] DEBUG - HTTP 200 response from GET http://192.168.1.9:8060/
Aug 04, 2018 04:39:19.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 29.128120 seconds: 192.168.1.10
Aug 04, 2018 04:43:09.314 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.10 (http://192.168.1.10:9080)
Aug 04, 2018 04:43:09.314 [0x7f8067b35700] DEBUG - HTTP requesting GET http://192.168.1.10:9080
Aug 04, 2018 04:43:09.318 [0x7f8067b35700] DEBUG - HTTP 200 response from GET http://192.168.1.10:9080
Aug 04, 2018 04:43:09.318 [0x7f8067b35700] ERROR - XML: Entity: line 1:\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - XML: parser\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - XML: error :\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - XML: Start tag expected, '<' not found\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - XML: status=ok\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - XML: ^\00
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - Error parsing content.
Aug 04, 2018 04:43:09.319 [0x7f8067b35700] ERROR - SSDP: Error parsing device schema for http://192.168.1.10:9080
Aug 04, 2018 04:45:19.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 27.303337 seconds: 192.168.1.9
Aug 04, 2018 04:47:00.126 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.9 (http://192.168.1.9:8060/)
Aug 04, 2018 04:47:00.127 [0x7f8067b35700] DEBUG - HTTP requesting GET http://192.168.1.9:8060/
Aug 04, 2018 04:47:00.133 [0x7f8067b35700] DEBUG - HTTP 200 response from GET http://192.168.1.9:8060/
Aug 04, 2018 04:51:39.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 29.117113 seconds: 192.168.1.9
Aug 04, 2018 04:53:22.127 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.9 (http://192.168.1.9:8060/)
Aug 04, 2018 04:53:22.128 [0x7f80583c5700] DEBUG - HTTP requesting GET http://192.168.1.9:8060/
Aug 04, 2018 04:53:22.134 [0x7f80583c5700] DEBUG - HTTP 200 response from GET http://192.168.1.9:8060/
Aug 04, 2018 04:53:29.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 27.700330 seconds: 192.168.1.10
Aug 04, 2018 04:53:37.302 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.10 (http://192.168.1.10:9080)
Aug 04, 2018 04:53:37.302 [0x7f80583c5700] DEBUG - HTTP requesting GET http://192.168.1.10:9080
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] DEBUG - HTTP 200 response from GET http://192.168.1.10:9080
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: Entity: line 1:\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: parser\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: error :\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: Start tag expected, '<' not found\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: status=ok\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - XML: ^\00
Aug 04, 2018 04:53:37.306 [0x7f80583c5700] ERROR - Error parsing content.
Aug 04, 2018 04:53:37.307 [0x7f80583c5700] ERROR - SSDP: Error parsing device schema for http://192.168.1.10:9080
Aug 04, 2018 04:55:49.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 28.945168 seconds: 192.168.1.10
Aug 04, 2018 05:00:42.518 [0x7f80583c5700] DEBUG - Sync: uploadStatus
Aug 04, 2018 05:00:48.111 [0x7f80583c5700] DEBUG - Butler: we're outside the window, stopping.
Aug 04, 2018 05:06:07.286 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.10 (http://192.168.1.10:32469/DeviceDescription.xml)
Aug 04, 2018 05:06:07.287 [0x7f8067b35700] DEBUG - HTTP requesting GET http://192.168.1.10:32469/DeviceDescription.xml
Aug 04, 2018 05:06:07.291 [0x7f8067b35700] DEBUG - HTTP 200 response from GET http://192.168.1.10:32469/DeviceDescription.xml
Aug 04, 2018 05:08:09.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 28.022282 seconds: 192.168.1.10
Aug 04, 2018 05:12:07.336 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.10 (http://192.168.1.10:32469/DeviceDescription.xml)
Aug 04, 2018 05:12:07.337 [0x7f80583c5700] DEBUG - HTTP requesting GET http://192.168.1.10:32469/DeviceDescription.xml
Aug 04, 2018 05:12:07.343 [0x7f80583c5700] DEBUG - HTTP 200 response from GET http://192.168.1.10:32469/DeviceDescription.xml
Aug 04, 2018 05:14:39.274 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 29.033878 seconds: 192.168.1.10
Aug 04, 2018 05:14:47.373 [0x7f806bfff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.10 (http://192.168.1.10:9080)
Aug 04, 2018 05:14:47.374 [0x7f8070bff700] DEBUG - HTTP requesting GET http://192.168.1.10:9080
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] DEBUG - HTTP 200 response from GET http://192.168.1.10:9080
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: Entity: line 1:\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: parser\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: error :\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: Start tag expected, '<' not found\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: status=ok\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - XML: ^\00
Aug 04, 2018 05:14:47.377 [0x7f8070bff700] ERROR - Error parsing content.
I don’t. Yeah those devices seem to be my Roku and an Nvidia Shield.
Ok… Then, just to experiment, (yes, I have a hunch). Please stop and restart PMS.
IF it’s still holding at 50-ish %, then it’s DSM’s reporting so restart it.
Yeah I thought the same thing before. Unfortunately when I stop the PMS, the RAM usage drops back to normal until someone plays from it again and then it loads, which I expect, but stays at that level even after stopping the stream.
Since you’re running 1.13.4,
If you have the 1.13.4 SPK handy,
Would you mind giving 1.13.5 a try?
Also, how much RAM is in the machine. If you only have 2GB then 50% is actually reporting correctly. PMS does about 1GB when fully loaded and firing on all cylinders but I’m not ruling out a memory leak just yet. Anything is possible but I’'m concerned why you’re the only one I’ve seen report it so far… and on Synology? I would think I’d have heard a lot of screaming before now, true?
Sorry for the late response. Do you mean try running 1.13.4? I currently am on 1.13.5.
The machine only has 2 GB ram for now and I do see it go up to 1gb during use which is normal. My main concern is why it stays up when Plex is supposed to not be in use, aka when no one is watching anything from it. I turned off the DLNA server usage for now and it seems to be keeping things normal with no crashes
Your logs were reporting 1.13.4
With regard to running in 2GB? Not advised.
2 GB is fine for a basic NAS.
4 GB for basic Plex.
8 GB for Plex with HW transcoding (2 x 4GB matched sticks) is the sweet spot for performance. It’s also the maximum the processor can address.
Sorry about the delay, I have been out of town.
I agree and I intend on installing more RAM to the machine. However turning off the DLNA seems to have worked and it is no longer getting stuck at a high processing rate even when not in use.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
