having problem acquire new wu from 171.67.108.33

[hisui]

My os is win2003 server,client is 5.0.3.0
having probelm with 171.67.108.33 server,usually unable to acquire new wu and need hours of retrying to get a new wu
ping and trace indicate no problem.Tried to access 171.67.108.33 via browser at 80 and 8080 get an empty page
This problem have persisted for almost a week


error logs see below
[21:22:50] Folding@home Core Shutdown: FINISHED_UNIT
[21:22:54] CoreStatus = 64 (100)
[21:22:54] Sending work to server


[21:22:54] + Attempting to send results
[21:23:22] + Results successfully sent
[21:23:22] Thank you for your contribution to Folding@Home.
[21:23:22] + Number of Units Completed: 1962

[21:23:26] - Preparing to get new work unit...
[21:23:26] + Attempting to get work packet
[21:23:26] - Connecting to assignment server
[21:23:26] - Successful: assigned to (171.67.108.33).
[21:23:26] + News From Folding@Home: Welcome to Folding@Home
[21:23:27] Loaded queue successfully.
[21:23:27] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[21:23:35] + Attempting to get work packet
[21:23:35] - Connecting to assignment server
[21:23:36] - Successful: assigned to (171.67.108.33).
[21:23:36] + News From Folding@Home: Welcome to Folding@Home
[21:23:36] Loaded queue successfully.
[21:23:36] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[21:23:57] + Attempting to get work packet
[21:23:57] - Connecting to assignment server
[21:23:58] - Successful: assigned to (171.67.108.33).
[21:23:58] + News From Folding@Home: Welcome to Folding@Home
[21:23:58] Loaded queue successfully.
[21:23:58] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[21:24:25] + Attempting to get work packet
[21:24:25] - Connecting to assignment server
[21:24:26] - Successful: assigned to (171.67.108.33).
[21:24:26] + News From Folding@Home: Welcome to Folding@Home
[21:24:26] Loaded queue successfully.
[21:24:26] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[21:25:12] + Attempting to get work packet
[21:25:12] - Connecting to assignment server
[21:25:13] - Successful: assigned to (171.67.108.33).
[21:25:13] + News From Folding@Home: Welcome to Folding@Home
[21:25:13] Loaded queue successfully.
[21:25:14] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[21:26:40] + Attempting to get work packet
[21:26:40] - Connecting to assignment server
[21:26:40] - Successful: assigned to (171.67.108.33).
[21:26:40] + News From Folding@Home: Welcome to Folding@Home
[21:26:40] Loaded queue successfully.
[21:26:41] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[21:29:21] + Attempting to get work packet
[21:29:21] - Connecting to assignment server
[21:29:22] - Successful: assigned to (171.67.108.33).
[21:29:22] + News From Folding@Home: Welcome to Folding@Home
[21:29:22] Loaded queue successfully.
[21:29:23] - Error: Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[21:34:48] + Attempting to get work packet
[21:34:48] - Connecting to assignment server
[21:34:48] - Successful: assigned to (171.67.108.33).
[21:34:48] + News From Folding@Home: Welcome to Folding@Home
[21:34:48] Loaded queue successfully.
[21:34:49] - Error: Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

[7im]

Run a version 6.xx fah client. Client Download link is at the top of the page.

[hisui]

I don't think this has too much to do with client version

[7im]

Easy way to test that thought. Download and run a v6 client to see if it gets work. Let us know how it turns out.

[hisui]

Actually I have a copy of v6 client running on another computer,last night same problem occurred
as far as it's assign to 171.67.108.33 server,this problem is bond to occurre

[7im]

The server status page shows that server is up and running.

Anything like a proxy or firewall that might be blocking that IP address?


Another quick test. Reconfigure the v5 client with a new Machine ID number. Did it go to the same server for work? If different, did it get work?

[bruce]

This server was exceptionally busy. I've alerted the Pande Group and suggested that the uniprocessor assignment process needs to be re-balanced to distribute processing across more servers. I can already see evidence this has been improved.

There's never a guarantee that you'll get a new assignment on the first try, but the old rule-of-thumb was to report it if it took more that 10 minutes. [The log (above) shows more than 11 minutes so obviously it needed something to be changed.] We've grown accustomed to getting new assignments on the first or second try. I'd be very happy if that always happened, but there will always be exceptions where it takes somewhat longer.