Cannot connect to server with a refuse connection

General Discussions
1

I’ve got a refuse connection since last night, I tried to reboot the NAS and reinstall the package. With checking the process in NAS activity monitor, it is keep in sleep mode. Don’t know how to solve it.

2

Please manually ZIP the logs as they exist now.

If you’re not sure where/how to get them, here are the FAQ

3

Logs.zip (4.8 MB) Hi~ Chuck

Here you go, appreciated your help.

4

Sorry to ask this but because you turned off DEBUG logging, I can’t really see what’s happening / PMS is trying to do. As FYI, the logs are fixed size. Logging consumes the same space with DEBUG on or off. With it ON (the default), it’s infinitely easier to see what PMS was trying to do.

From what little I can see, it looks like the NAS CPU is overloaded with whatever you last gave it to do.

Jan 17, 2020 22:32:36.576 [0x71dc2450] ERROR - EventSource: Retrying in 30 seconds.
Jan 17, 2020 22:32:42.688 [0x6afff450] WARN - SLOW QUERY: It took 230.000000 ms to retrieve 1 items.
Jan 17, 2020 22:32:43.514 [0x5fc6d450] WARN - SLOW QUERY: It took 490.000000 ms to retrieve 1 items.
Jan 17, 2020 22:32:44.672 [0x6e423450] ERROR - Unable to find client profile for device; platform=osx, platformVersion=10.15, device=, model=standalone
Jan 17, 2020 22:32:44.717 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:32:48.956 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:32:53.196 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:32:57.446 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:01.261 [0x6f094450] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 17, 2020 22:33:15.266 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:15.928 [0x6f094450] ERROR - SSDP: Error parsing device schema for http://192.168.31.239:34108/upnp/dev/21065%2FA9PF05951/desc
Jan 17, 2020 22:33:17.220 [0x6e711450] ERROR - Error issuing curl_easy_perform(handle): 7
Jan 17, 2020 22:33:17.220 [0x6e711450] WARN - HTTP error requesting GET https://60-179-176-90.52c1f2f2141a4450b2b76814ed71c23e.plex.direct:27679/identity (0, No error) (Failed to connect to 60-179-176-90.52c1f2f2141a4450b2b76814ed71c23e.plex.direct port 27679: Connection refused)
Jan 17, 2020 22:33:17.225 [0x6f094450] ERROR - SSDP: Error parsing device schema for http://192.168.31.24:39774/upnp/dev/21065%2FA9NK75153/desc
Jan 17, 2020 22:33:19.805 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:24.034 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:26.346 [0x659ff450] WARN - Held transaction for too long (../Statistics/StatisticsManager.cpp:252): 2.610000 seconds
Jan 17, 2020 22:33:27.599 [0x6ffbb450] WARN - Took too long (1.750000 seconds) to start a transaction on ../Library/MetadataItem.cpp:10109
Jan 17, 2020 22:33:27.599 [0x6ffbb450] WARN - Transaction that was running was started on thread 0x659ff450 at ../Statistics/StatisticsManager.cpp:252
Jan 17, 2020 22:33:40.674 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:44.933 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:46.695 [0x6ffbb450] WARN - Held transaction for too long (../Library/MetadataItem.cpp:10143): 0.370000 seconds
Jan 17, 2020 22:33:50.313 [0x610c1450] WARN - Waited one whole second for a busy database.
Jan 17, 2020 22:33:54.543 [0x610c1450] WARN - Waited one whole second for a busy database.

In this segment above, I would normally see "DEBUG " followed by exactly what it was doing and I could provide more details but at this point, I can’t.

Since you have access to the Plex share, to turn DEBUG logging back on so we can diagnose further, I would like to ask you to:

  1. Install the Synology “Text Editor” app from Package Center.
  2. Stop Plex
  3. Using FileStation, navigate back into the Plex share and stop in “Plex Media Server”
  4. Right-click “Preferences.xml”
  5. “Open with Text Editor”
  6. Now go to the 2nd line, all the way to the right, stopping before />
  7. Manually enable DEBUG logging again with logDebug="1"
  8. It will look just as mine does below.
  9. Save the file and exit
  10. Start Plex again in Package Center.
  11. Let it run for 2 minutes then stop it
  12. manually collect the logs and we’ll see what it’s doing.

Syno-Editing-Preferences
Syno-Editing-Preferences822×467 28.1 KB

5

I only see one line in the file.

Also, I checked CPU which is around 35% only. But the Plex Media Server process is in sleep.

6

Yours might have only one line. I do so much manual work, I could have messed up mine.

What’s important is that you find the end marker />
Add the logDebug="1" in front of it.

That’s all that matters.

7

I’m trying but it looks not right… “0 b1 logDebug=“1” />”??

8

Does everything have the form Name="value" ?
If so, then don’t worry because it’s otherwise running.

9

I’m trying to completely remove Plex from NAS, uninstall it from package center and also remove the “Plex” files like Library and all.

But still not working (from external), will further check in LAN and let you know.

10

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