Download Bug Happening Again (*.220)

[bruce]

Campus network support has been having trouble figuring out what is going on with *.220. Adding a new server is a step in the right direction. It also will reduce the traffic on *.220.

[vvoelz]

We've been scrambling to get our new servers up amidst all the new traffic. snapshot et al. have you seen further problems since 9 AM GMT Mon Mar 9?

[wdanwatts]

I still block that port, so all I can say is it was attempted today,

[b-morgan]

Another server is failing now:

Code: Select all

22:57:54:Enabled folding slot 01: READY gpu:0:GP104 [GeForce GTX 1070 Ti] 8186
22:57:55:WU00:FS01:Connecting to 65.254.110.245:8080
22:57:55:WU00:FS01:Connecting to 65.254.110.245:8080
22:57:56:WU00:FS01:Assigned to work server 140.163.4.241
22:57:56:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104 [GeForce GTX 1070 Ti] 8186 from 140.163.4.241
22:57:56:WU00:FS01:Connecting to 140.163.4.241:8080
22:58:17:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
22:58:17:WU00:FS01:Connecting to 140.163.4.241:80

[bruce]

A failure of port 8080 is not a failure when the WU is successfully uploaded to port 80. They both end up at exactly the same place.

Sorry about the wasted 21 seconds.

[Sn0wy23]

Have been able to connect and get WU from it, all clients running, have not had to restart them at all since Monday evening GMT.

[b-morgan]

A failure of port 8080 is not a failure when the WU is successfully uploaded to port 80. They both end up at exactly the same place.
Sorry about the wasted 21 seconds.

I'm sorry that the next line in the log was still pending when I extracted that portion of the log. I am smart enough to recognize a port 8080 failure followed immediately by a port 80 success.

[b-morgan]

For the *.220 server, I removed my firewall rule that dropped TCP packets to that address and I did have one attempt to *.220 which failed. The difference this time was that the client was not hung and proceeded to find a WU on a different server. Logs should be available on request.

[snapshot]

We've been scrambling to get our new servers up amidst all the new traffic. snapshot et al. have you seen further problems since 9 AM GMT Mon Mar 9?

No, no further problems here.

[bruce]

Logs should be available on request.

The failure was not found in the logs.

[HaloJones]

two failures today on two different machines. both on 220. had to reboot to clear and have put my firewall rule back in

[rwh202]

Still broken:

Code: Select all

04:19:47:WU00:FS01:Connecting to 65.254.110.245:8080
04:19:47:WU00:FS01:Assigned to work server 155.247.166.220
04:19:47:WU00:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:TU116 [GeForce GTX 1660] from 155.247.166.220
04:19:47:WU00:FS01:Connecting to 155.247.166.220:8080
04:19:48:WU00:FS01:Downloading 5.81MiB
04:19:54:WU00:FS01:Download 5.38%
04:20:01:WU00:FS01:Download 6.45%
04:20:07:WU00:FS01:Download 7.53%
04:20:15:WU00:FS01:Download 10.76%
04:20:38:WU00:FS01:Download 11.83%
04:20:44:WU00:FS01:Download 12.91%
04:20:56:WU00:FS01:Download 13.98%
04:21:04:WU00:FS01:Download 16.13%
04:21:10:WU00:FS01:Download 17.21%
04:21:18:WU00:FS01:Download 19.36%
04:21:58:WU00:FS01:Download 20.44%
04:22:38:WU00:FS01:Download 21.51%
04:22:45:WU00:FS01:Download 23.66%
04:23:10:WU00:FS01:Download 25.82%
04:23:19:WU00:FS01:Download 26.89%
04:23:27:WU00:FS01:Download 30.12%
04:23:44:WU00:FS01:Download 32.27%
04:23:51:WU00:FS01:Download 35.50%
04:23:57:WU00:FS01:Download 39.80%
04:24:07:WU00:FS01:Download 43.03%
04:24:15:WU00:FS01:Download 45.18%
04:24:22:WU00:FS01:Download 49.48%
04:24:28:WU00:FS01:Download 52.71%
04:24:34:WU00:FS01:Download 60.24%
04:24:40:WU00:FS01:Download 64.54%
04:24:46:WU00:FS01:Download 68.84%
04:24:54:WU00:FS01:Download 70.99%

Stuck for 8 hours

[Michigeezer]

Started my Folding back up yesterday (3/11) and have not had to restart because of hang-ups although my logs show numerous instances where an attempt resulted in "transfer failure". At least the system just goes ahead and retries until it's successful.

[snapshot]

We've been scrambling to get our new servers up amidst all the new traffic. snapshot et al. have you seen further problems since 9 AM GMT Mon Mar 9?

No, no further problems here.

I spoke too soon as it's still happening and one client required several restarts before it picked up a WU.

[Sn0wy23]

Spoke to soon myself, having issues again. However, not with the IP here, my system isn't even trying to connect to this anymore despite no blockage in place. I have had both machines down with WU failing to dowload.
Rebboots not helped, oddly the second GPU in one machine connected to another server and carried on, just this other GPU not connecting.

Code: Select all

14:27:24:WU00:FS02:Connecting to 65.254.110.245:8080
14:27:25:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
14:27:25:WU00:FS02:Connecting to 18.218.241.186:80
14:27:25:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
14:27:25:ERROR:WU00:FS02:Exception: Could not get an assignment
14:27:26:WU00:FS02:Connecting to 65.254.110.245:8080
14:27:26:WARNING:WU00:FS02:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
14:27:26:WU00:FS02:Connecting to 18.218.241.186:80
14:27:26:WARNING:WU00:FS02:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
14:27:26:ERROR:WU00:FS02:Exception: Could not get an assignment