171.67.108.60 down?

[Breach]

Below:

Code: Select all

11:14:23:WU00:FS01:Connecting to assign3.stanford.edu:8080
11:14:23:WU00:FS01:News: Welcome to Folding@Home
11:14:23:WU00:FS01:Assigned to work server 171.67.108.60
11:14:23:WU00:FS01:Requesting new work unit for slot 01: RUNNING cpu:6 from 171.67.108.60
11:14:23:WU00:FS01:Connecting to 171.67.108.60:8080
11:14:25:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
11:14:25:WU00:FS01:Connecting to 171.67.108.60:80
11:14:26:WU02:FS00:0x15:Completed  31000000 out of 50000000 steps (62%).
11:14:26:ERROR:WU00:FS01:Exception: Failed to connect to 171.67.108.60:80: No connection could be made because the target machine actively refused it.
11:14:27:WU00:FS01:Connecting to assign3.stanford.edu:8080
11:14:27:WU00:FS01:News: Welcome to Folding@Home
11:14:27:WU00:FS01:Assigned to work server 171.67.108.60
11:14:27:WU00:FS01:Requesting new work unit for slot 01: RUNNING cpu:6 from 171.67.108.60
11:14:27:WU00:FS01:Connecting to 171.67.108.60:8080
11:14:29:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
11:14:29:WU00:FS01:Connecting to 171.67.108.60:80
11:14:30:ERROR:WU00:FS01:Exception: Failed to connect to 171.67.108.60:80: No connection could be made because the target machine actively refused it.
11:15:27:WU00:FS01:Connecting to assign3.stanford.edu:8080
11:15:27:WU00:FS01:News: Welcome to Folding@Home
11:15:27:WU00:FS01:Assigned to work server 171.67.108.60
11:15:27:WU00:FS01:Requesting new work unit for slot 01: RUNNING cpu:6 from 171.67.108.60
11:15:27:WU00:FS01:Connecting to 171.67.108.60:8080
11:15:29:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
11:15:29:WU00:FS01:Connecting to 171.67.108.60:80
11:15:30:ERROR:WU00:FS01:Exception: Failed to connect to 171.67.108.60:80: No connection could be made because the target machine actively refused it.
11:16:27:WU02:FS00:0x15:Completed  31500000 out of 50000000 steps (63%).

[Breach]

OK, back up again it seems.

[tlg]

Code: Select all

06:53:08:WU01:FS01:Connecting to assign3.stanford.edu:8080
06:53:08:WU01:FS01:News: Welcome to Folding@Home
06:53:08:WU01:FS01:Assigned to work server 171.67.108.60
06:53:08:WU01:FS01:Requesting new work unit for slot 01: RUNNING cpu:6 from 171.67.108.60
06:53:08:WU01:FS01:Connecting to 171.67.108.60:8080
06:53:10:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
06:53:10:WU01:FS01:Connecting to 171.67.108.60:80
06:53:11:ERROR:WU01:FS01:Exception: Failed to connect to 171.67.108.60:80: No connection could be made because the target machine actively refused it.

Tried 5 times so far before I noticed this.

//Edit: When I punch in the server address, it says it's up and running.

Windows firewall is disabled. No Internet Security is running. Just the router

//Edit2: no dice from 0650 to 0706 Zulu. At 0706 successfully downloaded a new WU. 5 failed attempts prior.

[PantherX]

When I checked it 7:52 AM GMT/UTC, the CPU Load was 1.46 and any value above 2 is considered as heavy. My guess would be it might have been under load for the duration that your Client tried to download a WU hence it refused until the load level came down to a more manageable level.

[tlg]

Thanks Panther. I guess there really isn't a fix to lower the load other than to standby and wait it out?

[PantherX]

Correct. Sometimes, there is a surge of Clients either uploading completed WUs or downloading WUs which may temporarily cause the CPU Load to increase. When that happens, any new connections may be denied until the pre-existing ones are dealt with. In your case, the down time lasted approximately 16 minutes. The FAHClient is automatically configured to keep trying (delay increases between each attempt to prevent overloading the server) so it works most of the time. Normally, if the CPU Load is high for more than a few hours, it might be time to inform the Project owner so any issue can be caught early on and resolved.