Project: 11292 (Run 3, Clone 1, Gen 32) does not send

[McMaster]

Unfortunately, still nothing. I restarted the client, and it's still stuck at Send.

Though, it did make some kind of log. Here it is:

Code: Select all

21:42:01:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
21:42:01:WU01:FS00:Connecting to 171.67.108.44:80
21:42:02:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:42:02:WU02:FS00:Connecting to 171.67.108.44:80
21:42:25:WU02:FS00:News: Welcome to Folding@Home
21:42:25:WU02:FS00:Assigned to work server 171.67.108.44
21:42:25:WU02:FS00:Requesting new work unit for slot 00: READY gpu:0:Juniper [Radeon HD 5700 Series] from 171.67.108.44
21:42:25:WU02:FS00:Connecting to 171.67.108.44:8080
21:42:46:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:42:46:WU02:FS00:Connecting to 171.67.108.44:80
21:44:43:WU01:FS00:Upload 2.21%
21:44:43:WARNING:WU01:FS00:Exception: Failed to send results to work server: Transfer failed
21:44:44:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:11292 run:3 clone:1 gen:32 core:0x16 unit:0x000007ff6652edbc4caa47bc0000001a
21:44:44:WU01:FS00:Uploading 2.82MiB to 171.67.108.44
21:44:44:WU01:FS00:Connecting to 171.67.108.44:8080

[bollix47]

Okay I can't connect to it either so I'm going to notify the person responsible for this server ... no guarantees.

[McMaster]

Great, I hope that whatever problem exists gets fixed soon.

[schwancr]

We're looking into this. It seems to be a network issue on the WS side.

[McMaster]

We're looking into this. It seems to be a network issue on the WS side.

Great! This means the problem is not on my end.

[bruce]

The status of "full" is in contrast to "accept" (only) where a server is not actively assigning new work to anyone or "standby" where it is neither assigning new work or accepting completed work. Full is a good thing.

[McMaster]

I had gone to sleep and just woke up, so I don't know when the problem was fixed, but the work unit was sent successfully and I received a new work unit. Thanks for the fix!

[wallapatrick]

I'm still having the same problem for the last couple of days. Today in the log I see "20:30:43:WARNING:WU03:FS00:Exception: Failed to send results to work server: Failed to connect to 171.67.108.44:80: No connection could be made because the target machine actively refused it." I saw the same server yesterday (171.67.108.44) repeatedly. I had similar problems yesterday on project 11293, but that has apparently resolved

I'm not sure that my computers are being used efficiently anymore. I've been doing F@H for a couple of years now and currently have 18 cores working on it on 3 computers, 24hours/day, every day. I don't usually pay much attention to F@H, other than to verify it is running and check to make sure my performance numbers aren't deteriorating. I do sometimes switch it off for an hour or two on one single computer to play a game, never on the other two; but all 3 computers show the errors.

I'm also failing to get work assigned (from the log):
21:10:50:WARNING:WU01:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
21:10:50:WU01:FS00:Connecting to assign-GPU.stanford.edu:8080
21:10:50:WU01:FS00:News: Welcome to Folding@Home
21:10:50:WARNING:WU01:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
21:10:50:ERROR:WU01:FS00:Exception: Could not get an assignment.

[bollix47]

Welcome to the folding@home support forum wallapatrick.

Thank you for your report ... the server you're trying to send the results to is in Reject status ... I will let PG know.

Please post the System Info and Config sections of your log as explained here and we may be able to make some suggestions re the clients inability to get new work although it may be related to the Reject status if that server is the only one where your GPU can get work.

[schwancr]

The server should be back again. Sorry for the trouble.

-Christian