Server 171.64.65.75
Moderators: Site Moderators, FAHC Science Team
Server 171.64.65.75
I d'nt see this server on the server status page which run smp core A3 2.27 project 10113, 10114 and 10115.
-
- Posts: 126
- Joined: Sat Aug 02, 2008 3:08 am
Server 171.64.65.75 Bad Packet Type from server
I am getting a bad packet type error from this server.
I updated the client to 6.34 from 6.30 and it is still getting this error. Help????
Thanks,
BW
I updated the client to 6.34 from 6.30 and it is still getting this error. Help????
Thanks,
BW
Code: Select all
[18:04:03]
[18:04:04] Loaded queue successfully.
[18:04:04] - Preparing to get new work unit...
[18:04:04] Cleaning up work directory
[18:04:04] - Autosending finished units... [March 21 18:04:04 UTC]
[18:04:04] Trying to send all finished work units
[18:04:04] + No unsent completed units remaining.
[18:04:04] - Autosend completed
[18:04:04] + Attempting to get work packet
[18:04:04] Passkey found
[18:04:04] - Will indicate memory of 8181 MB
[18:04:04] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
[18:04:04] - Connecting to assignment server
[18:04:04] Connecting to http://assign.stanford.edu:8080/
[18:04:04] Posted data.
[18:04:04] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:04:04] + News From Folding@Home: Welcome to Folding@Home
[18:04:04] Loaded queue successfully.
[18:04:04] Sent data
[18:04:04] Connecting to http://171.64.65.75:8080/
[18:04:04] Posted data.
[18:04:04] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:04:04] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[18:04:22] + Attempting to get work packet
[18:04:22] Passkey found
[18:04:22] - Will indicate memory of 8181 MB
[18:04:22] - Connecting to assignment server
[18:04:22] Connecting to http://assign.stanford.edu:8080/
[18:04:23] Posted data.
[18:04:23] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:04:23] + News From Folding@Home: Welcome to Folding@Home
[18:04:23] Loaded queue successfully.
[18:04:23] Sent data
[18:04:23] Connecting to http://171.64.65.75:8080/
[18:04:23] Posted data.
[18:04:23] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:04:23] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[18:04:39] + Attempting to get work packet
[18:04:39] Passkey found
[18:04:39] - Will indicate memory of 8181 MB
[18:04:39] - Connecting to assignment server
[18:04:39] Connecting to http://assign.stanford.edu:8080/
[18:04:39] Posted data.
[18:04:39] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:04:39] + News From Folding@Home: Welcome to Folding@Home
[18:04:39] Loaded queue successfully.
[18:04:39] Sent data
[18:04:39] Connecting to http://171.64.65.75:8080/
[18:04:39] Posted data.
[18:04:39] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:04:39] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[18:05:08] + Attempting to get work packet
[18:05:08] Passkey found
[18:05:08] - Will indicate memory of 8181 MB
[18:05:08] - Connecting to assignment server
[18:05:08] Connecting to http://assign.stanford.edu:8080/
[18:05:08] Posted data.
[18:05:08] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:05:08] + News From Folding@Home: Welcome to Folding@Home
[18:05:08] Loaded queue successfully.
[18:05:08] Sent data
[18:05:08] Connecting to http://171.64.65.75:8080/
[18:05:09] Posted data.
[18:05:09] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:05:09] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[18:05:53] + Attempting to get work packet
[18:05:53] Passkey found
[18:05:53] - Will indicate memory of 8181 MB
[18:05:53] - Connecting to assignment server
[18:05:53] Connecting to http://assign.stanford.edu:8080/
[18:05:53] Posted data.
[18:05:53] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:05:53] + News From Folding@Home: Welcome to Folding@Home
[18:05:54] Loaded queue successfully.
[18:05:54] Sent data
[18:05:54] Connecting to http://171.64.65.75:8080/
[18:05:54] Posted data.
[18:05:54] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:05:54] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[18:07:24] + Attempting to get work packet
[18:07:24] Passkey found
[18:07:24] - Will indicate memory of 8181 MB
[18:07:24] - Connecting to assignment server
[18:07:24] Connecting to http://assign.stanford.edu:8080/
[18:07:25] Posted data.
[18:07:25] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:07:25] + News From Folding@Home: Welcome to Folding@Home
[18:07:25] Loaded queue successfully.
[18:07:25] Sent data
[18:07:25] Connecting to http://171.64.65.75:8080/
[18:07:25] Posted data.
[18:07:25] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:07:25] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
Re: Server 171.64.65.75
I cannot explain what's happening. We've had several reports of bad packets and there seems to be a connection with failing to upgrade to 6.34 but I'm not sure what that connection is.
How about deleting (or renaming) the \work folder and restarting the client. Does that clear it up?
If not, reconfigure the client to use a different MachineID. Does that clear it up?
How about deleting (or renaming) the \work folder and restarting the client. Does that clear it up?
If not, reconfigure the client to use a different MachineID. Does that clear it up?
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 126
- Joined: Sat Aug 02, 2008 3:08 am
Re: Server 171.64.65.75
Actually I just let the systems chug away and they finally got work units.
I had restarted them a few times and even rebooted the systems. Still had the packet errors.
Working now so whatever it was cleared up.
Thank Bruce.
BW
I had restarted them a few times and even rebooted the systems. Still had the packet errors.
Working now so whatever it was cleared up.
Thank Bruce.
BW
Re: Server 171.64.65.75
Getting same bad packets on this server.....
Code: Select all
[01:27:02] + Attempting to get work packet
[01:27:02] Passkey found
[01:27:02] - Will indicate memory of 1536 MB
[01:27:02] - Connecting to assignment server
[01:27:02] Connecting to http://assign.stanford.edu:8080/
[01:27:03] Posted data.
[01:27:03] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[01:27:03] + News From Folding@Home: Welcome to Folding@Home
[01:27:03] Loaded queue successfully.
[01:27:03] Sent data
[01:27:03] Connecting to http://171.64.65.75:8080/
[01:27:03] Posted data.
[01:27:03] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[01:27:03] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[01:28:27] + Attempting to get work packet
[01:28:27] Passkey found
[01:28:27] - Will indicate memory of 1536 MB
[01:28:27] - Connecting to assignment server
[01:28:27] Connecting to http://assign.stanford.edu:8080/
[01:28:28] Posted data.
[01:28:28] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[01:28:28] + News From Folding@Home: Welcome to Folding@Home
[01:28:28] Loaded queue successfully.
[01:28:28] Sent data
[01:28:28] Connecting to http://171.64.65.75:8080/
[01:28:28] Posted data.
[01:28:28] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[01:28:28] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[01:31:23] + Attempting to get work packet
[01:31:23] Passkey found
[01:31:23] - Will indicate memory of 1536 MB
[01:31:23] - Connecting to assignment server
[01:31:23] Connecting to http://assign.stanford.edu:8080/
[01:31:23] Posted data.
[01:31:23] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[01:31:23] + News From Folding@Home: Welcome to Folding@Home
[01:31:23] Loaded queue successfully.
[01:31:23] Sent data
[01:31:23] Connecting to http://171.64.65.75:8080/
[01:31:24] Posted data.
[01:31:24] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[01:31:24] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[01:36:47] + Attempting to get work packet
[01:36:47] Passkey found
[01:36:47] - Will indicate memory of 1536 MB
[01:36:47] - Connecting to assignment server
[01:36:47] Connecting to http://assign.stanford.edu:8080/
[01:36:48] Posted data.
[01:36:48] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[01:36:48] + News From Folding@Home: Welcome to Folding@Home
[01:36:48] Loaded queue successfully.
[01:36:48] Sent data
[01:36:48] Connecting to http://171.64.65.75:8080/
[01:36:48] Posted data.
[01:36:48] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[01:36:48] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
-
- Posts: 336
- Joined: Fri Jun 26, 2009 4:34 am
Re: Server 171.64.65.75
Rich_D, I've seen other "bad packet" reports in the past. Usually they were found to be a lack of work units on the server. As soon as some work surfaced, they went away. There does not appear to be many units available on this server on the stats page. Let us know if it continues. Thanks.
Re: Server 171.64.65.75
I had some machines assigned to this server this morning getting the same bad packet message. I've changed them all to advmethods, which allowed them to get work. They were all idle for the last 2-3 hours.