128.143.231.201 appears to need a kick start

[Grandpa_01]

the server stats has not updated since Fri Oct 31 02:20:18 PDT 2014 and it appears it was down for a while before that update on this server.

Code: Select all

Thu Oct 30 22:10:11 PDT 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.11	0	0		16294	3278	1935	307	307	307	-	-	-	-	-	0	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Oct 31 02:20:18 PDT 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.07	0	0		16294	3274	1936	302	302	302	-	-	-	-	-	3	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	

Code: Select all

[11:13:05] + Attempting to get work packet
[11:13:05] Passkey found
[11:13:05] - Will indicate memory of 16009 MB
[11:13:05] - Connecting to assignment server
[11:13:05] Connecting to http://assign.stanford.edu:8080/
[11:13:05] Posted data.
[11:13:05] Initial: 8F80; - Successful: assigned to (128.143.231.201).
[11:13:05] + News From Folding@Home: 
[11:13:06] Loaded queue successfully.
[11:13:06] Sent data
[11:13:06] Connecting to http://128.143.231.201:8080/
[11:13:36] - Couldn't send HTTP request to server
[11:13:36] + Could not connect to Work Server
[11:13:36] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.

[bollix47]

Not sure if it was a kick but I think something happened to fix the 'problem' because mine just uploaded and the client downloaded another from that same bigadv server. I did Pause the slot and restart the client ... it wasn't as smooth as usual due to the client trying to quit while the upload and download communications were timing out at the same time but it did work. Since you're using v6 your experience would probably be different.