Page 2 of 2

Re: 171.64.65.55 sending bad packets

Posted: Tue Mar 15, 2011 3:55 pm
by dvanatta
Hi,

Thanks for the updates, still looking into this.

-Dan

Re: 171.64.65.55 sending bad packets

Posted: Tue Mar 15, 2011 7:43 pm
by dvanatta
OK, I think I figured it out. Keep me posted if it's still not working

Re: 171.64.65.55 sending bad packets

Posted: Thu Mar 17, 2011 2:08 am
by DavidMudkips
Still getting the error

Code: Select all

[02:00:40] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:00:40] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[02:00:59] + Attempting to get work packet
[02:00:59] Passkey found
[02:00:59] - Will indicate memory of 4087 MB
[02:00:59] - Connecting to assignment server
[02:00:59] Connecting to http://assign.stanford.edu:8080/
[02:01:00] Posted data.
[02:01:00] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[02:01:00] + News From Folding@Home: Welcome to Folding@Home
[02:01:00] Loaded queue successfully.
[02:01:00] Sent data
[02:01:00] Connecting to http://171.64.65.55:8080/
[02:01:00] Posted data.
[02:01:00] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:01:00] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[02:01:13] + Attempting to get work packet
[02:01:13] Passkey found
[02:01:13] - Will indicate memory of 4087 MB
[02:01:13] - Connecting to assignment server
[02:01:13] Connecting to http://assign.stanford.edu:8080/
[02:01:13] Posted data.
[02:01:13] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[02:01:13] + News From Folding@Home: Welcome to Folding@Home
[02:01:13] Loaded queue successfully.
[02:01:13] Sent data
[02:01:13] Connecting to http://171.64.65.55:8080/
[02:01:14] Posted data.
[02:01:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:01:14] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[02:01:37] + Attempting to get work packet
[02:01:37] Passkey found
[02:01:37] - Will indicate memory of 4087 MB
[02:01:37] - Connecting to assignment server
[02:01:37] Connecting to http://assign.stanford.edu:8080/
[02:01:38] Posted data.
[02:01:38] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[02:01:38] + News From Folding@Home: Welcome to Folding@Home
[02:01:38] Loaded queue successfully.
[02:01:38] Sent data
[02:01:38] Connecting to http://171.64.65.55:8080/
[02:01:38] Posted data.
[02:01:38] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:01:38] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[02:02:29] + Attempting to get work packet
[02:02:29] Passkey found
[02:02:29] - Will indicate memory of 4087 MB
[02:02:29] - Connecting to assignment server
[02:02:29] Connecting to http://assign.stanford.edu:8080/
[02:02:29] Posted data.
[02:02:29] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[02:02:29] + News From Folding@Home: Welcome to Folding@Home
[02:02:29] Loaded queue successfully.
[02:02:29] Sent data
[02:02:29] Connecting to http://171.64.65.55:8080/
[02:02:30] Posted data.
[02:02:30] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[02:02:30] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.

Re: 171.64.65.55 sending bad packets

Posted: Thu Mar 17, 2011 2:29 am
by dvanatta
Hm. Do you have the latest client?

Re: 171.64.65.55 sending bad packets

Posted: Thu Mar 17, 2011 5:37 pm
by dvanatta
Hi all,

This took me a while to track down because many people were getting jobs from my server. I think the issue is that there just weren't enough (even though it never actually ran out). There are plenty of jobs now, so let's see if it keeps happening.

-Dan

Re: 171.64.65.55 sending bad packets

Posted: Thu Mar 17, 2011 10:11 pm
by RETARD
ditto
tried deleting A3 core still cant find server to download the core let alone the WU
have tried on windows and linux VM
am running 6.34

Re: 171.64.65.55 sending bad packets

Posted: Thu Mar 17, 2011 10:15 pm
by 7im
As with any troubleshooting, show me the fahlog.txt. ;)