Folding Forum

two mchines failing to get work units

22:15:18:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:15:18:WU00:FS00:News: Welcome to Folding@Home
22:15:18:WU00:FS00:Assigned to work server 171.67.108.34
22:15:18:WU00:FS00:Requesting new work unit for slot 00: READY smp:8 from 171.67.108.34
22:15:18:WU00:FS00:Connecting to 171.67.108.34:8080
22:15:19:ERROR:WU00:FS00:Exception: Server did not assign work unit

[22:19:24] + Attempting to get work packet
[22:19:24] Passkey found
[22:19:24] - Will indicate memory of 4072 MB
[22:19:24] - Connecting to assignment server
[22:19:24] Connecting to http://assign.stanford.edu:8080/
[22:19:24] Posted data.
[22:19:24] Initial: 43AB; - Successful: assigned to (171.67.108.34).
[22:19:24] + News From Folding@Home: Welcome to Folding@Home
[22:19:24] Loaded queue successfully.
[22:19:24] Sent data
[22:19:24] Connecting to http://171.67.108.34:8080/
[22:19:25] Posted data.
[22:19:25] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:19:25] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

No, it is not down. Have you tried any of the troubleshooting steps listed in the first topic of this forum?

No WUs from 171.67.108.35 either. Just give it some time (and check the troubleshooting steps, as suggested).

My machines did eventually get units, just wanted to make sure nothing was wrong.

I can confirm I am not getting work units from this server.

I'm having this download problem on two of my machines too.

Trying the sever log page ( http://fah-web.stanford.edu/logs/171.67.108.35.log.html ) gives me a 404 error.

Trying the server directly gives me a blank page.

Here is my log where is started not getting a new unit:

Try: http://fah-web.stanford.edu/pybeta/logs ... 4.log.html

Well, I ultimately got a WU from 171.64.65.55...

rjbelans wrote:Trying the sever log page ( http://fah-web.stanford.edu/logs/171.67.108.35.log.html ) gives me a 404 error.

Trying the server directly gives me a blank page.

The links to the logs with pybeta as bollix47 posted have replaced the older links. As for the blank page, that or a page that gives just an OK indicates that you reached the server.

Several projects from 171.67.108.34-35 were moved from beta to advanced about the time this was first reported. So possibly the change in settings had not yet fully taken effect. Post here if this continues.

The servers are working fine now. It might have taken some time for the changes to take effect. Sorry for the inconvenience.

Joe_H wrote:

rjbelans wrote:Trying the sever log page ( http://fah-web.stanford.edu/logs/171.67.108.35.log.html ) gives me a 404 error.

Trying the server directly gives me a blank page.

The links to the logs with pybeta as bollix47 posted have replaced the older links. As for the blank page, that or a page that gives just an OK indicates that you reached the server.

Several projects from 171.67.108.34-35 were moved from beta to advanced about the time this was first reported. So possibly the change in settings had not yet fully taken effect. Post here if this continues.

Maybe something needs to be fixed in v7 then. The link I posted is what I got when I clicked on the Work Server link in the Work unit frame of the Status tab.

I wasn't aware that a blank page was the same as getting OK. I don't remember seeing that on the server troublshooting thread, maybe that could be updated too.

Thanks for the info.

A number of the F@H support servers were moved to new hardware a few weeks ago, and in the process some of the older links went away. The link from the FAHControl screen either needs to be updated, or alias links added on the servers. I will see if I can get that to the attention of the right persons. In the meantime, if you use the links to the logs from the Server Status page, that will get you the updated link.