171.65.103.162 - no new work

[d-con]

My client was assigned to 171.65.103.162 at least a day or two ago, and hasn't gotten any work.

The "18" is misleading, as I tried several times to remove queue.dat and the work directory and finally installed the latest windows up client cleanly. My client is still being assigned to a server that won't serve up a WU. How so I get out of this? Is it just me? I know I can get to that IP address as ping responded.

Folding@Home Client Version 6.23
...

[19:06:38] - Attempt #17 to get work failed, and no other work to do.
Waiting before retry.
[19:54:44] + Attempting to get work packet
[19:54:44] - Connecting to assignment server
[19:54:45] - Successful: assigned to (171.65.103.162).
[19:54:45] + News From Folding@Home: Welcome to Folding@Home
[19:54:45] Loaded queue successfully.
[19:54:45] + Could not connect to Work Server
[19:54:45] - Attempt #18 to get work failed, and no other work to do.
Waiting before retry.

{dmk@d4600:107} ping 171.65.103.162

Pinging 171.65.103.162 with 32 bytes of data:

Reply from 171.65.103.162: bytes=32 time=102ms TTL=51
Reply from 171.65.103.162: bytes=32 time=103ms TTL=51
Reply from 171.65.103.162: bytes=32 time=102ms TTL=51
Reply from 171.65.103.162: bytes=32 time=102ms TTL=51

Ping statistics for 171.65.103.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 103ms, Average = 102ms

[d-con]

help?

Hello Mr assignment server. I need some work.
Hello Mr. client, please contact 171.65.103.162 for some work.
Hello 171.65.103.162, I would like a work packet please. I have nothing to do right now.
no answer
no answer
....
wait a while and repeat and repeat and repeat and repeat ....



[02:20:07] - Attempt #26 to get work failed, and no other work to do.
Waiting before retry.
[03:08:18] + Attempting to get work packet
[03:08:18] - Connecting to assignment server
[03:08:19] - Successful: assigned to (171.65.103.162).
[03:08:19] + News From Folding@Home: Welcome to Folding@Home
[03:08:19] Loaded queue successfully.
[03:08:20] + Could not connect to Work Server
[03:08:20] - Attempt #27 to get work failed, and no other work to do.
Waiting before retry.

[7im]

It would help if you posted the first 35 lines of your fahlog.txt file. That way we can see which client type of v6.23 you are running, and what, if any, client switches are being used, and a few other things.

I turned in my crystal ball a while back, but if I had to guess, it's a CPU client, and no switches. Add the -advmethods switch (or remove it if already in use), or reconfigure the client to change the machine id. One or both may get you assigned to a different server.

The Project Summary page doesn't show anything wrong with that server, so if the next server doesn't work either, it's probably at your end and not at Stanford. And vice versa.

[d-con]

Windows CPU Console Edition. -svcstart with a directory specified.

Somebody fixed something because the 29th attempt (plus the various cleanings I did, so it's some number much greater than 29) was the winner.

Thanks for your reply. I checked the machine when I saw the topic reply notification.

I did check the server stats page yesterday. When I looked at that page, the only thing I noticed was it said "full" in one of the columns, but I really have no idea what any of that means.

My other 3 machines are all getting WUs just fine, and they fold much faster than this one so they tend to get a new WU every day. This one tends to get one every 5 days or so. The rest of them are all running either the linux or windows MP CPU clients, and there's a PS3 client also, and I was able to ping that server from that machine. Not sure what else could have been wrong on my end. It's a fairly stable machine running XP.

Nonetheless, I appreciated your reply.

-David

[brityank]

For the past month or so this server has had fits and starts; both my WinXP and WinVista will both fail to upload results or get a new WU without several knocks on the door. On the upload, it always kicks at the Collection server, and always uploads, and always gets it Rejected as it has no record of the WU.

How's the realignment/rebuild of the network coming? I recall seeing a couple of references that Stanford is having several issues that are in for resolution with the IT group - is that still a concern?

Thanks for your support, 7im