171.67.108.22:8080 => Error: Bad packet type from server...

[Magic Michael]

Hi guys,

I can't get any WUs from this server:

Code: Select all

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

Code: Select all

links http://171.67.108.22:8080
links http://171.67.108.22

work, I get my "ok". I restartet the client and even the computer, nothing helps. Maybe that's why I got the same WU again and again ...
Replacing "-bigadv" with "-advmethods" works, I can receive normal A3-WUs.
Any ideas ?

Thanks
Michael

[bruce]

Server 171.67.108.22 does, in fact, have very few WUs. Your client should be redirected to another sever which does have work that can be assigned to you in a few minutes. Either that or someone will complete an existing WU and a new one will be generated.

[Magic Michael]

Hmm, instead of being redirected it's sitting there, trying to get work from 171.67.108.22 and doing nothing else. Faulty algorithms on Stanford's side or do I have to reconfigure the client ?

[7im]

Yes, and yes.

Reconfigure the client with a different machine ID. It may cause the client to bump over to a different server, but maybe not.

[bruce]

You can also try adding/removing the optional flags which frequently redirects you to a different server.

[Magic Michael]

Giving the client a different machine id did the trick. I don't understand why, but now it's folding bigadv (a2). Thank you guys !

[DocJonz]

I've had some similar problems on -bigadv WU's - the last one this morning (see below). The first time it happened, I was away and it carried on for 123 attempts before I returned home to fix it .... !!

Code: Select all

[10:08:14] Verifying core Core_a3.fah...
[10:08:14] Signature is VALID
[10:08:14] 
[10:08:14] Trying to unzip core FahCore_a3.exe
[10:08:14] Decompressed FahCore_a3.exe (4375728 bytes) successfully
[10:08:14] + Core successfully engaged
[10:08:14] Deleting current work unit & continuing...
[10:08:27] Trying to send all finished work units
[10:08:27] + No unsent completed units remaining.
[10:08:27] - Preparing to get new work unit...
[10:08:27] Cleaning up work directory
[10:08:27] + Attempting to get work packet
[10:08:27] Passkey found
[10:08:27] - Will indicate memory of 5550 MB
[10:08:27] - Connecting to assignment server
[10:08:27] Connecting to http://assign.stanford.edu:8080/
[10:08:29] Posted data.
[10:08:29] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[10:08:29] + News From Folding@Home: Welcome to Folding@Home
[10:08:29] Loaded queue successfully.
[10:08:29] Connecting to http://171.67.108.22:8080/
[10:08:29] Posted data.
[10:08:29] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:08:30] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[10:08:47] + Attempting to get work packet
[10:08:47] Passkey found
[10:08:47] - Will indicate memory of 5550 MB
[10:08:47] - Connecting to assignment server
[10:08:47] Connecting to http://assign.stanford.edu:8080/
[10:08:48] Posted data.
[10:08:48] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[10:08:48] + News From Folding@Home: Welcome to Folding@Home
[10:08:48] Loaded queue successfully.
[10:08:48] Connecting to http://171.67.108.22:8080/
[10:08:49] Posted data.
[10:08:49] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:08:50] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[10:09:09] + Attempting to get work packet
[10:09:09] Passkey found
[10:09:09] - Will indicate memory of 5550 MB
[10:09:09] - Connecting to assignment server
[10:09:09] Connecting to http://assign.stanford.edu:8080/
[10:09:10] Posted data.
[10:09:10] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[10:09:10] + News From Folding@Home: Welcome to Folding@Home
[10:09:10] Loaded queue successfully.
[10:09:10] Connecting to http://171.67.108.22:8080/
[10:09:11] Posted data.
[10:09:11] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:09:12] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.

[chriskwarren]

Should typing in 171.67.108.22:8080 get the response message "OK"? When I do it my browser downloads a 'part' file instead.

[bruce]

Firefox downloads all files as a "part" and then renames them to whatever they're supposed to be once the download is complete. Then it decides whether it knows how to open the file or not.

When it starts to download a file and then there is zero content, it stops while it's still called a "part" so that's an indication of a problem. Under the same conditions, IE says "The webpage cannot be displayed"