Since 1 or 2 weeks, Plex keeps stopping almost daily on my Synology server. I can restart it pretty easily from the package center but I don’t understand what is going wrong now. It’s really only 1 time per day, that that happens.
Maybe also good to know, the Synology server goes to sleep a few hours each night.
Synology Server Version# DSM 6.2.1-23824
Plex Server Version#: 1.13.4.5271-200287a06
Player Version#:
make sure you are running with debug logging enabled
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
Restart the server and after next crash, get the logs and attach here with details of when the issue arose and what you get when you try to access the server
See
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
I’m having the same issues as OP.
I’ve tried:
Model: DS1511+
Current DSM version:DSM 6.2.1-23824
Plex Server Version#: 1.13.8.5395-10d48da0d
Your logs are in VERBOSE.
Please turn this OFF.
We lose ALL the important information when VERBOSE is on because it only logs 2 minutes of elapsed time.
Enable only DEBUG logging.
Please recreate / capture again and submit updated logs
I have removed your logs as you have enabled logging of security tokens. Make sure it is disabled before posting any logs in the forum. Probably wise to shutdown Plex Media Server, move the contents of the Logs directory out and then restart Plex Media Server. That way there would not be any old log files with tokens when you come to download the logs
See this article for location of the Plex Media Server data including the Logs directory
I can actually see problem similar to issue identified here Cannot find Plex Server after upgrade (last working version 1.13.4.5271) - #12 by audelair and here Plex update 1.13.9.5439- Server unreachable - #69 by sa2000 and a few other threads
Basically when remote access is enabled and if the router takes a while to respond to NAT/uPnP request to get the Public IP Address, the server gets locked out for the duration of this time - transient deadlocks for up to 2 minutes. This is clearly visible at 17:07
Oct 22, 2018 17:04:51.406 [0x7f487bfff700] DEBUG - Request: [192.168.1.13:57235 (Subnet)] GET / (10 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:04:51.411 [0x7f4864d59700] DEBUG - Request: [127.0.0.1:56864 (WAN)] GET / (10 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:05:30.217 [0x7f486d623700] DEBUG - Request: [192.168.1.13:51721 (Subnet)] GET / (10 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:05:32.837 [0x7f4879717700] DEBUG - Request: [127.0.0.1:56880 (WAN)] GET / (11 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:07:16.385 [0x7f486d335700] DEBUG - Request: [192.168.1.13:47850 (Subnet)] GET / (12 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:07:19.016 [0x7f486ad59700] DEBUG - Request: [127.0.0.1:56928 (WAN)] GET / (13 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:07:34.374 [0x7f486dbff700] DEBUG - Request: [192.168.1.13:50195 (Subnet)] GET / (14 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:08:04.923 [0x7f486a77d700] DEBUG - Request: [127.0.0.1:56961 (WAN)] GET / (15 live) TLS GZIP Signed-in Token (aramsuchit@gmail.com)
Oct 22, 2018 17:09:02.369 [0x7f486aa6b700] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Oct 22, 2018 17:09:02.621 [0x7f486aa6b700] WARN - NAT: PMP, got an error: Not Supported by gateway.
Oct 22, 2018 17:09:02.628 [0x7f487b511700] DEBUG - Completed after connection close: [192.168.1.13:57235] 200 GET / (15 live) TLS GZIP 251221ms 31 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.629 [0x7f487b511700] DEBUG - Completed after connection close: [192.168.1.13:38470] 200 GET / (15 live) TLS GZIP 281717ms 17 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.633 [0x7f487b7ff700] DEBUG - Completed after connection close: [192.168.1.13:51721] 200 GET / (15 live) TLS GZIP 212417ms 31 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.635 [0x7f487b7ff700] DEBUG - Completed: [127.0.0.1:56848] 200 GET / (15 live) TLS GZIP 279250ms 1727 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.638 [0x7f487b511700] DEBUG - Completed: [127.0.0.1:56864] 200 GET / (15 live) TLS GZIP 251226ms 1727 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.642 [0x7f487b511700] DEBUG - Completed after connection close: [192.168.1.13:44661] 200 GET / (15 live) TLS GZIP 281378ms 31 bytes (pipelined: 2)
Oct 22, 2018 17:09:02.652 [0x7f487b511700] DEBUG - Completed after connection close: [192.168.1.13:50195] 200 GET / (15 live) TLS GZIP 88278ms 29 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.652 [0x7f487b7ff700] DEBUG - Completed after connection close: [192.168.1.13:47850] 200 GET / (15 live) TLS GZIP 106267ms 29 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.657 [0x7f487b7ff700] DEBUG - Completed: [127.0.0.1:56928] 200 GET / (15 live) TLS GZIP 103641ms 1727 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.657 [0x7f487b511700] DEBUG - Completed: [127.0.0.1:56880] 200 GET / (15 live) TLS GZIP 209820ms 1727 bytes (pipelined: 1)
Oct 22, 2018 17:09:02.661 [0x7f487b7ff700] DEBUG - Completed: [127.0.0.1:56961] 200 GET / (15 live) TLS GZIP 57738ms 1727 bytes (pipelined: 1)
we have requests from plex client apps taking about 2 minutes to complete and they would have timed out before that and gave server unavailable response
this has already been referred to the development team
You could try and see if disabling uPnP in the router would help. You would need to switch to a port forward and manually specified port. If you have no need for remote access, you could disable it until the problem is fixed
Thank you! I disabled it and will report back.
Plex Media Server Logs_2018-10-23_13-32-24.zip (1.6 MB)
Upload from my side.
You have disabled debug logging !
Also if the server is crashing, would need you to have crash reporting enabled. You have it disabled.
In Plex Web See Settings / Server / General / Show Advanced
For debug logging - See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
Please restart the server after enabling it so we have startup sequence covered by the logging
Also please indicate the times when the issues arose
From what is in the logs - i can see you have a DNS configuration / operation issue on the NAS
This DNS Lookup failure was at 13:31 on 23 October 2018
Oct 23, 2018 13:31:19.189 [0x7f7e6d35f700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 23, 2018 13:31:19.189 [0x7f7e6d35f700] WARN - HTTP error requesting GET http://plex.tv/pms/:/ip (0, No error) (Couldn't resolve host 'plex.tv')
Oct 23, 2018 13:31:19.190 [0x7f7e6d35f700] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):
I can see the same DNS failures throughout
Oct 19, 2018 08:34:37.070 [0x7f1bc337d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 08:38:30.158 [0x7f1bc6bff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 08:38:40.184 [0x7f1bc6bff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 08:55:22.792 [0x7f1bc3c47700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 10:30:40.515 [0x7f1bc3f35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 11:02:51.625 [0x7f1bc1223700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 13:35:24.729 [0x7f1bc0c47700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 14:50:09.333 [0x7f1bb73ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 15:21:52.378 [0x7f1bc1223700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 15:22:02.458 [0x7f1bb73ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 16:04:55.776 [0x7f1bc1efb700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 17:40:42.924 [0x7f1bc5a05700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 17:51:24.797 [0x7f1bc1223700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 18:34:36.513 [0x7f1bc17ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 20:18:28.059 [0x7f1bc5a05700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 20:18:38.092 [0x7f1bc1223700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 20:51:20.698 [0x7f1bb9559700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 21:54:19.156 [0x7f1bb9559700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 22:04:13.991 [0x7f1bb5fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 22:14:18.215 [0x7f1bc1efb700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 22:58:43.179 [0x7f1bc5a05700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 23:05:29.247 [0x7f1bb9b35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 23:15:46.741 [0x7f1bc1223700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 19, 2018 23:55:53.873 [0x7f1bba111700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 00:21:26.365 [0x7f1bba111700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 00:46:10.256 [0x7f1bc1efb700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 00:56:26.210 [0x7f1bb9b35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 08:33:45.850 [0x7fef53bff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 08:34:37.070 [0x7fef53bff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 08:34:37.180 [0x7fef4bbff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 08:34:44.485 [0x7fef51fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 10:17:38.225 [0x7fef4b047700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 11:07:53.473 [0x7fef3f3ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 11:17:54.625 [0x7fef3b847700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 11:47:57.779 [0x7fef3f3ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 12:17:14.476 [0x7fef48511700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 14:28:51.224 [0x7fef3c3ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 14:29:01.663 [0x7fef3be23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 14:52:36.386 [0x7fef3be23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 15:44:04.199 [0x7fef3b26b700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 15:54:15.539 [0x7fef3bb35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 16:24:46.236 [0x7fef4ad59700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 16:34:57.843 [0x7fef4ad59700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 17:34:33.587 [0x7fef50911700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 19:06:57.640 [0x7fef43fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 19:33:51.887 [0x7fef43fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 21:50:15.496 [0x7fef4c7ef700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 22:02:36.603 [0x7fef453ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 23:16:07.914 [0x7fef3bb35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 20, 2018 23:16:17.950 [0x7fef4aa6b700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:14.219 [0x7f3104bff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:43.956 [0x7f3101be1700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:43.961 [0x7f30ff623700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:55.988 [0x7f3100623700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:57.528 [0x7f30ff623700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:57.667 [0x7f3102fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:04:58.249 [0x7f30fc623700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 09:05:09.877 [0x7f30fc335700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 12:04:40.055 [0x7f3101be1700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 16:57:06.943 [0x7f3100911700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 22:17:37.114 [0x7f30eea23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 23:04:50.612 [0x7f31027ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 21, 2018 23:53:54.151 [0x7f30ee735700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 00:04:40.128 [0x7f30fd8d7700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 08:34:39.682 [0x7fb972f35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 09:34:30.940 [0x7fb9723ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 10:34:29.043 [0x7fb973fff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 12:38:32.164 [0x7fb9677ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 12:38:52.327 [0x7fb95c40d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 14:02:08.466 [0x7fb96b111700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 14:05:55.163 [0x7fb95ea23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 14:08:35.601 [0x7fb95e735700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 14:12:13.589 [0x7fb96b111700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 14:28:08.652 [0x7fb96ae23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 15:13:11.476 [0x7fb9737ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 16:13:56.887 [0x7fb95de6b700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 16:35:02.836 [0x7fb95d5a1700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 17:37:12.985 [0x7fb9677ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 18:18:53.366 [0x7fb95ed11700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 18:34:30.869 [0x7fb95d5a1700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 18:44:49.012 [0x7fb95ea23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 19:12:13.186 [0x7fb95c40d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 19:12:30.612 [0x7fb9677ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 20:23:42.478 [0x7fb95c40d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 20:34:47.077 [0x7fb95c40d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 20:34:58.156 [0x7fb95ed11700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 20:50:46.042 [0x7fb974911700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 21:01:03.416 [0x7fb976b68700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 21:01:16.848 [0x7fb95d5a1700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:00:54.171 [0x7fb96f3ef700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:13:13.919 [0x7fb976b68700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:33:05.914 [0x7fb96eb25700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:34:14.810 [0x7fb96ae23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:34:31.504 [0x7fb96f3ef700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:34:35.149 [0x7fb96ae23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 22:47:18.807 [0x7fb9723ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:11:58.042 [0x7fb972f35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:12:33.165 [0x7fb95c40d700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:12:41.693 [0x7fb972f35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:12:52.900 [0x7fb96f3ef700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:12:58.633 [0x7fb96b111700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:13:38.446 [0x7fb954b35700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:13:40.684 [0x7fb9553ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:13:58.263 [0x7fb954e23700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:14:10.256 [0x7fb9553ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:14:40.357 [0x7fb9737ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 22, 2018 23:33:00.568 [0x7fb9553ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 23, 2018 01:07:08.974 [0x7fb9737ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 23, 2018 13:31:19.189 [0x7f7e6d35f700] ERROR - Error issuing curl_easy_perform(handle): 6
Ensure first you resolve the network setup issue and DNS functionality on the NAS. Ensure both debug logging and crash reporting are enabled.
Restart the server
If you get any failures, note down the time and what the issue is and then capture the logs
and attach here together with the details of the problem
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
I think the latest DSM update solved it, it’s now stable for 2 days already.
Disabling the remote access resolved my issue. I always made the recommended changes to my logging.
I am having this same issue and have been for quite some time. Attaching log files.
Server Version#: 1.13.9.5456
Player Version#: N/A
DSM Version#: DSM 6.2.1-23824 Update 1
NAS Model#: DS1515+
I previously reported this issue under Plex Media Server. I am still having issues. My NAS is hardwired directly to my router, two NIC ports (LAN 1 & 2, bonded). My router connects directly to AT&T U-Verse. Since the initial post, the router has been replaced. So, at this point, I’m honestly at a loss. Plex worked flawlessly for the longest. Now, I am having to reboot the NAS on a almost a daily basis, sometimes twice a day.
Please advise.
The issue has already been referred to the development team. I can see a 2 minute hang whilst waiting for the router to respond
Nov 01, 2018 11:12:21.539 [0x7f5df1f35700] DEBUG - PublicAddressManager: Obtaining public IP.
Nov 01, 2018 11:12:21.859 [0x7f5df1f35700] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: xxx.xxx.xxx.xxx
Nov 01, 2018 11:13:40.811 [0x7f5df2511700] DEBUG - Request: [192.168.1.83:57200 (Subnet)] GET / (7 live) GZIP Signed-in
Nov 01, 2018 11:13:40.811 [0x7f5df2511700] DEBUG - Completed: [192.168.1.83:57200] 401 GET / (7 live) GZIP 0ms 416 bytes (pipelined: 3)
Nov 01, 2018 11:13:40.850 [0x7f5de4bff700] DEBUG - Request: [192.168.1.83:57209 (Subnet)] GET / (8 live) TLS GZIP Signed-in Token (amurphy)
Nov 01, 2018 11:13:41.291 [0x7f5dea159700] DEBUG - Request: [192.168.1.83:57200 (Subnet)] GET / (8 live) GZIP Signed-in Token (amurphy)
Nov 01, 2018 11:13:54.700 [0x7f5dea735700] DEBUG - Request: [127.0.0.1:51041 (WAN)] GET / (9 live) TLS GZIP Signed-in Token (amurphy)
Nov 01, 2018 11:14:43.602 [0x7f5e0103b800] DEBUG - Ordered to stop server.
I have escalated the issue and developers are looking into it.
We are trying to establish when this regression came in. We do have proof of the problem being there in 1.13.8 and in 1.13.9
Would you be prepared to try earlier versions if i send you them to try to see when it broke - so trying going back sequentially until the problem resolves itself?
I would have absolutely no problem in assisting you with regression testing to track the issue down. As I posted the issue previously, I can help pinpoint that the issue started with a revision somewhere prior to 20 AUG 2018, as that was the date that I first posted. At that time, I was running Server Version#: 1.13.5.5291-6fa5e50a8 and DSM Version#: DSM 6.2-23739 Update 2. I hope that helps.
Aaron
OK thanks. I will check out your original logs
Yup - can see the issue there
Aug 20, 2018 09:02:03.652 [0x7ff8bdb1c700] DEBUG - Request: [192.168.1.254:32400 (Subnet)] GET / (10 live) TLS GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:03.677 [0x7ff8bebc5700] DEBUG - Request: [192.168.1.92:59732 (Subnet)] GET / (12 live) TLS GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:03.678 [0x7ff8c31a1700] DEBUG - Request: [192.168.1.92:59731 (Subnet)] GET / (12 live) TLS GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:03.773 [0x7ff8be5e9700] DEBUG - Request: [192.168.1.92:59733 (Subnet)] GET / (13 live) TLS GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:13.586 [0x7ff8b1bff700] DEBUG - Request: [192.168.1.92:59755 (Subnet)] GET / (15 live) GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:13.586 [0x7ff8bcf64700] DEBUG - Request: [192.168.1.92:59756 (Subnet)] GET / (15 live) GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:13.599 [0x7ff8c4047700] DEBUG - Request: [192.168.1.92:59757 (Subnet)] GET / (16 live) GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:02:13.603 [0x7ff8c63e1700] DEBUG - Request: [192.168.1.92:59758 (Subnet)] GET / (17 live) GZIP Signed-in Token (amurphy)
Aug 20, 2018 09:06:19.683 [0x7ff8b73ff700] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Aug 20, 2018 09:06:19.934 [0x7ff8b73ff700] WARN - NAT: PMP, got an error: Not Supported by gateway.
Aug 20, 2018 09:06:19.940 [0x7ff8c7bff700] DEBUG - Completed: [192.168.1.92:59755] 200 GET / (17 live) GZIP 246354ms 2418 bytes (pipelined: 1)
Aug 20, 2018 09:06:19.941 [0x7ff8c7bff700] DEBUG - Completed: [192.168.1.92:59756] 200 GET / (17 live) GZIP 246354ms 2418 bytes (pipelined: 1)
Aug 20, 2018 09:06:19.946 [0x7ff8c7bff700] DEBUG - Request: [192.168.1.92:59723 (Subnet)] GET / (17 live) GZIP Signed-in
Aug 20, 2018 09:06:19.951 [0x7ff8c7bff700] DEBUG - Completed: [192.168.1.92:59757] 200 GET / (18 live) GZIP 246353ms 2418 bytes (pipelined: 1)
Aug 20, 2018 09:06:19.953 [0x7ff8c7bff700] DEBUG - Completed: [192.168.1.92:59758] 200 GET / (18 live) GZIP 246350ms 2418 bytes (pipelined: 1)
Aug 20, 2018 09:06:19.954 [0x7ff8c7bff700] DEBUG - Completed: [192.168.1.92:59723] 401 GET / (18 live) GZIP 6ms 416 bytes (pipelined: 3)
Aug 20, 2018 09:06:19.955 [0x7ff8c7911700] DEBUG - Completed after connection close: [192.168.1.254:32400] 200 GET / (19 live) TLS GZIP 256302ms 29 bytes (pipelined: 1)
We do know that 1.13.4 is ok
The cause of the problem has now been identified - thanks for the extra info about the original reporting of the issue
You’re welcome. I’m glad I could help. So, is this something that I need to roll back to 1.13.4 to resolve for now or is this an easy fix that we should see a patch out soon to resolve?
Aaron
I am hopeful I would have a development build for you to try within the next week and confirm the fix working ok
1.13.4 does not have the bug
