171.64.65.55 sending bad packets

Moderators: Site Moderators, FAHC Science Team

djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

171.64.65.55 sending bad packets

Post by djchandler »

The last time this occurred communicating with me was at 10:00 GMT on 3/3/11.

Code: Select all

[10:06:07] + Attempting to get work packet
[10:06:07] Passkey found
[10:06:07] - Will indicate memory of 2560 MB
[10:06:07] - Connecting to assignment server
[10:06:07] Connecting to http://assign.stanford.edu:8080/
[10:06:07] Posted data.
[10:06:07] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:06:07] + News From Folding@Home: Welcome to Folding@Home
[10:06:07] Loaded queue successfully.
[10:06:07] Sent data
[10:06:07] Connecting to http://171.64.65.55:8080/
[10:06:08] Posted data.
[10:06:08] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:06:08] - Attempt #7  to get work failed, and no other work to do. Waiting before retry.
This is something I haven't encountered before. Is anybody else having this problem?
Folding for Cures
dvanatta
Pande Group Member
Posts: 62
Joined: Tue Sep 14, 2010 7:00 pm

Re: 171.64.65.55 sending bad packets

Post by dvanatta »

Which project is this?

Thanks,
Dan
toTOW
Site Moderator
Posts: 6349
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: 171.64.65.55 sending bad packets

Post by toTOW »

This error usually means that the server has no work to send ...

Dan> it's not specific to a project ...
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

Re: 171.64.65.55 sending bad packets

Post by djchandler »

This happened again today. It took almost 5 hours (14 failed attempts) to get assigned to a server with valid work units. Is there any way on the client side to force changing servers or shut down the client after x number of failed attempts?

I'm trying to limit F@H use of this particular machine to overnight only (using -oneunit flag) while still returning A3 units as quickly as possible. Save for the odd 6701 or 6702 getting assigned on my second overnight run, this is largely successful. Due to the delay getting switched over today, not so much. Are we running out of A3 WUs?

Code: Select all

[10:15:05] Loaded queue successfully.
[10:15:05] - Preparing to get new work unit...
[10:15:05] - Autosending finished units... [March 4 10:15:05 UTC]
[10:15:05] Cleaning up work directory
[10:15:05] Trying to send all finished work units
[10:15:05] + No unsent completed units remaining.
[10:15:05] - Autosend completed
[10:15:05] + Attempting to get work packet
[10:15:05] Passkey found
[10:15:05] - Will indicate memory of 3072 MB
[10:15:05] - Detect CPU. Vendor: AuthenticAMD, Family: 15, Model: 10, Stepping: 0
[10:15:05] - Connecting to assignment server
[10:15:05] Connecting to http://assign.stanford.edu:8080/
[10:15:06] Posted data.
[10:15:06] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:15:06] + News From Folding@Home: Welcome to Folding@Home
[10:15:06] Loaded queue successfully.
[10:15:06] Sent data
[10:15:06] Connecting to http://171.64.65.55:8080/
[10:15:06] Posted data.
[10:15:06] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:15:06] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[10:15:21] + Attempting to get work packet
[10:15:21] Passkey found
[10:15:21] - Will indicate memory of 3072 MB
[10:15:21] - Connecting to assignment server
[10:15:21] Connecting to http://assign.stanford.edu:8080/
[10:15:22] Posted data.
[10:15:22] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:15:22] + News From Folding@Home: Welcome to Folding@Home
[10:15:22] Loaded queue successfully.
[10:15:22] Sent data
[10:15:22] Connecting to http://171.64.65.55:8080/
[10:15:22] Posted data.
[10:15:22] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:15:22] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[10:15:43] + Attempting to get work packet
[10:15:43] Passkey found
[10:15:43] - Will indicate memory of 3072 MB
[10:15:43] - Connecting to assignment server
[10:15:43] Connecting to http://assign.stanford.edu:8080/
[10:15:44] Posted data.
[10:15:44] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:15:44] + News From Folding@Home: Welcome to Folding@Home
[10:15:44] Loaded queue successfully.
[10:15:44] Sent data
[10:15:44] Connecting to http://171.64.65.55:8080/
[10:15:44] Posted data.
[10:15:44] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:15:44] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[10:16:10] + Attempting to get work packet
[10:16:10] Passkey found
[10:16:10] - Will indicate memory of 3072 MB
[10:16:10] - Connecting to assignment server
[10:16:10] Connecting to http://assign.stanford.edu:8080/
[10:16:10] Posted data.
[10:16:10] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:16:10] + News From Folding@Home: Welcome to Folding@Home
[10:16:10] Loaded queue successfully.
[10:16:10] Sent data
[10:16:10] Connecting to http://171.64.65.55:8080/
[10:16:11] Posted data.
[10:16:11] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:16:11] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[10:16:53] + Attempting to get work packet
[10:16:53] Passkey found
[10:16:53] - Will indicate memory of 3072 MB
[10:16:53] - Connecting to assignment server
[10:16:53] Connecting to http://assign.stanford.edu:8080/
[10:16:54] Posted data.
[10:16:54] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:16:54] + News From Folding@Home: Welcome to Folding@Home
[10:16:54] Loaded queue successfully.
[10:16:54] Sent data
[10:16:54] Connecting to http://171.64.65.55:8080/
[10:16:54] Posted data.
[10:16:54] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:16:54] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[10:18:28] + Attempting to get work packet
[10:18:28] Passkey found
[10:18:28] - Will indicate memory of 3072 MB
[10:18:28] - Connecting to assignment server
[10:18:28] Connecting to http://assign.stanford.edu:8080/
[10:18:29] Posted data.
[10:18:29] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:18:29] + News From Folding@Home: Welcome to Folding@Home
[10:18:29] Loaded queue successfully.
[10:18:29] Sent data
[10:18:29] Connecting to http://171.64.65.55:8080/
[10:18:29] Posted data.
[10:18:29] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:18:29] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[10:21:21] + Attempting to get work packet
[10:21:21] Passkey found
[10:21:21] - Will indicate memory of 3072 MB
[10:21:21] - Connecting to assignment server
[10:21:21] Connecting to http://assign.stanford.edu:8080/
[10:21:21] Posted data.
[10:21:21] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:21:21] + News From Folding@Home: Welcome to Folding@Home
[10:21:22] Loaded queue successfully.
[10:21:22] Sent data
[10:21:22] Connecting to http://171.64.65.55:8080/
[10:21:22] Posted data.
[10:21:22] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:21:22] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[10:26:56] + Attempting to get work packet
[10:26:56] Passkey found
[10:26:56] - Will indicate memory of 3072 MB
[10:26:56] - Connecting to assignment server
[10:26:56] Connecting to http://assign.stanford.edu:8080/
[10:26:56] Posted data.
[10:26:56] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:26:56] + News From Folding@Home: Welcome to Folding@Home
[10:26:56] Loaded queue successfully.
[10:26:56] Sent data
[10:26:56] Connecting to http://171.64.65.55:8080/
[10:26:57] Posted data.
[10:26:57] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:26:57] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[10:37:47] + Attempting to get work packet
[10:37:47] Passkey found
[10:37:47] - Will indicate memory of 3072 MB
[10:37:47] - Connecting to assignment server
[10:37:47] Connecting to http://assign.stanford.edu:8080/
[10:37:48] Posted data.
[10:37:48] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[10:37:48] + News From Folding@Home: Welcome to Folding@Home
[10:37:48] Loaded queue successfully.
[10:37:48] Sent data
[10:37:48] Connecting to http://171.64.65.55:8080/
[10:37:48] Posted data.
[10:37:48] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[10:37:48] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[10:59:10] + Attempting to get work packet
[10:59:10] Passkey found
[10:59:10] - Will indicate memory of 3072 MB
[10:59:10] - Connecting to assignment server
[10:59:10] Connecting to http://assign.stanford.edu:8080/
[10:59:11] Posted data.
[10:59:11] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[10:59:11] + News From Folding@Home: Welcome to Folding@Home
[10:59:11] Loaded queue successfully.
[10:59:11] Sent data
[10:59:11] Connecting to http://171.64.65.54:8080/
[10:59:11] Posted data.
[10:59:11] Initial: 0000; + Could not connect to Work Server
[10:59:11] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[11:41:54] + Attempting to get work packet
[11:41:54] Passkey found
[11:41:54] - Will indicate memory of 3072 MB
[11:41:54] - Connecting to assignment server
[11:41:54] Connecting to http://assign.stanford.edu:8080/
[11:41:54] Posted data.
[11:41:54] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[11:41:54] + News From Folding@Home: Welcome to Folding@Home
[11:41:54] Loaded queue successfully.
[11:41:54] Sent data
[11:41:54] Connecting to http://171.64.65.55:8080/
[11:41:55] Posted data.
[11:41:55] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[11:41:55] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[12:30:09] + Attempting to get work packet
[12:30:09] Passkey found
[12:30:09] - Will indicate memory of 3072 MB
[12:30:09] - Connecting to assignment server
[12:30:09] Connecting to http://assign.stanford.edu:8080/
[12:30:10] Posted data.
[12:30:10] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[12:30:10] + News From Folding@Home: Welcome to Folding@Home
[12:30:10] Loaded queue successfully.
[12:30:10] Sent data
[12:30:10] Connecting to http://171.64.65.54:8080/
[12:30:11] Posted data.
[12:30:11] Initial: 0000; + Could not connect to Work Server
[12:30:11] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[13:18:11] + Attempting to get work packet
[13:18:11] Passkey found
[13:18:11] - Will indicate memory of 3072 MB
[13:18:11] - Connecting to assignment server
[13:18:11] Connecting to http://assign.stanford.edu:8080/
[13:18:11] Posted data.
[13:18:11] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[13:18:11] + News From Folding@Home: Welcome to Folding@Home
[13:18:12] Loaded queue successfully.
[13:18:12] Sent data
[13:18:12] Connecting to http://171.64.65.55:8080/
[13:18:12] Posted data.
[13:18:12] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[13:18:12] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[14:06:12] + Attempting to get work packet
[14:06:12] Passkey found
[14:06:12] - Will indicate memory of 3072 MB
[14:06:12] - Connecting to assignment server
[14:06:12] Connecting to http://assign.stanford.edu:8080/
[14:06:13] Posted data.
[14:06:13] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[14:06:13] + News From Folding@Home: Welcome to Folding@Home
[14:06:13] Loaded queue successfully.
[14:06:13] Sent data
[14:06:13] Connecting to http://171.64.65.55:8080/
[14:06:14] Posted data.
[14:06:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[14:06:14] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[14:54:16] + Attempting to get work packet
[14:54:16] Passkey found
[14:54:16] - Will indicate memory of 3072 MB
[14:54:16] - Connecting to assignment server
[14:54:16] Connecting to http://assign.stanford.edu:8080/
[14:54:17] Posted data.
[14:54:17] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[14:54:17] + News From Folding@Home: Welcome to Folding@Home
[14:54:17] Loaded queue successfully.
[14:54:17] Sent data
[14:54:17] Connecting to http://171.64.65.54:8080/
[14:54:18] Posted data.
[14:54:18] Initial: 0000; - Receiving payload (expected size: 1764722)
[14:54:20] - Downloaded at ~861 kB/s
[14:54:20] - Averaged speed for that direction ~717 kB/s
[14:54:20] + Received work.
[14:54:20] + Closed connections
[14:54:20] 
[14:54:20] + Processing work unit
[14:54:20] Core required: FahCore_a3.exe
[14:54:20] Core found.
[14:54:20] Working on queue slot 09 [March 4 14:54:20 UTC]
[14:54:20] + Working ...
Folding for Cures
dvanatta
Pande Group Member
Posts: 62
Joined: Tue Sep 14, 2010 7:00 pm

Re: 171.64.65.55 sending bad packets

Post by dvanatta »

djchandler,

I'm looking into this, but I think I should wait for a report from another user before shutting my server down, if only to get more information about the problem.


-Dan
djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

Re: 171.64.65.55 sending bad packets

Post by djchandler »

I have more than one box doing this. My first machine referenced here is running an AMD Phenom II X6 1090T. But I just checked my wife's computer F@H logs that runs F@H 24/7. It has been getting the same assignment problems. The following occurred March 2.

Code: Select all

[18:30:12] + Attempting to get work packet
[18:30:12] Passkey found
[18:30:12] - Will indicate memory of 2048 MB
[18:30:12] - Connecting to assignment server
[18:30:12] Connecting to http://assign.stanford.edu:8080/
[18:30:12] Posted data.
[18:30:12] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:30:12] + News From Folding@Home: Welcome to Folding@Home
[18:30:12] Loaded queue successfully.
[18:30:12] Sent data
[18:30:12] Connecting to http://171.64.65.55:8080/
[18:30:13] Posted data.
[18:30:13] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:30:13] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:30:23] + Attempting to get work packet
[18:30:23] Passkey found
[18:30:23] - Will indicate memory of 2048 MB
[18:30:23] - Connecting to assignment server
[18:30:23] Connecting to http://assign.stanford.edu:8080/
[18:30:23] Posted data.
[18:30:23] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:30:23] + News From Folding@Home: Welcome to Folding@Home
[18:30:24] Loaded queue successfully.
[18:30:24] Sent data
[18:30:24] Connecting to http://171.64.65.55:8080/
[18:30:24] Posted data.
[18:30:24] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:30:24] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:30:40] + Attempting to get work packet
[18:30:40] Passkey found
[18:30:40] - Will indicate memory of 2048 MB
[18:30:40] - Connecting to assignment server
[18:30:40] Connecting to http://assign.stanford.edu:8080/
[18:30:40] Posted data.
[18:30:40] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:30:40] + News From Folding@Home: Welcome to Folding@Home
[18:30:41] Loaded queue successfully.
[18:30:41] Sent data
[18:30:41] Connecting to http://171.64.65.55:8080/
[18:30:41] Posted data.
[18:30:41] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:30:41] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:31:03] + Attempting to get work packet
[18:31:03] Passkey found
[18:31:03] - Will indicate memory of 2048 MB
[18:31:03] - Connecting to assignment server
[18:31:03] Connecting to http://assign.stanford.edu:8080/
[18:31:03] Posted data.
[18:31:03] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:31:03] + News From Folding@Home: Welcome to Folding@Home
[18:31:03] Loaded queue successfully.
[18:31:03] Sent data
[18:31:03] Connecting to http://171.64.65.55:8080/
[18:31:04] Posted data.
[18:31:04] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:31:04] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:31:55] + Attempting to get work packet
[18:31:55] Passkey found
[18:31:55] - Will indicate memory of 2048 MB
[18:31:55] - Connecting to assignment server
[18:31:55] Connecting to http://assign.stanford.edu:8080/
[18:31:56] Posted data.
[18:31:56] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:31:56] + News From Folding@Home: Welcome to Folding@Home
[18:31:56] Loaded queue successfully.
[18:31:56] Sent data
[18:31:56] Connecting to http://171.64.65.55:8080/
[18:31:56] Posted data.
[18:31:56] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:31:56] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:33:17] + Attempting to get work packet
[18:33:17] Passkey found
[18:33:17] - Will indicate memory of 2048 MB
[18:33:17] - Connecting to assignment server
[18:33:17] Connecting to http://assign.stanford.edu:8080/
[18:33:17] Posted data.
[18:33:17] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:33:17] + News From Folding@Home: Welcome to Folding@Home
[18:33:17] Loaded queue successfully.
[18:33:17] Sent data
[18:33:17] Connecting to http://171.64.65.55:8080/
[18:33:18] Posted data.
[18:33:18] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:33:18] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:36:05] + Attempting to get work packet
[18:36:05] Passkey found
[18:36:05] - Will indicate memory of 2048 MB
[18:36:05] - Connecting to assignment server
[18:36:05] Connecting to http://assign.stanford.edu:8080/
[18:36:06] Posted data.
[18:36:06] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[18:36:06] + News From Folding@Home: Welcome to Folding@Home
[18:36:06] Loaded queue successfully.
[18:36:06] Sent data
[18:36:06] Connecting to http://171.64.65.55:8080/
[18:36:06] Posted data.
[18:36:06] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[18:36:06] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[18:41:34] + Attempting to get work packet
[18:41:34] Passkey found
[18:41:34] - Will indicate memory of 2048 MB
[18:41:34] - Connecting to assignment server
[18:41:34] Connecting to http://assign.stanford.edu:8080/
[18:41:35] Posted data.
[18:41:35] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[18:41:35] + News From Folding@Home: Welcome to Folding@Home
[18:41:35] Loaded queue successfully.
[18:41:35] Sent data
[18:41:35] Connecting to http://171.64.65.75:8080/
[18:41:36] Posted data.
[18:41:36] Initial: 0000; - Receiving payload (expected size: 987341)
[18:41:38] - Downloaded at ~482 kB/s
[18:41:38] - Averaged speed for that direction ~522 kB/s
[18:41:38] + Received work.
[18:41:38] Trying to send all finished work units
[18:41:38] + No unsent completed units remaining.
[18:41:38] + Closed connections
[18:41:38] 
[18:41:38] + Processing work unit
[18:41:38] Core required: FahCore_a3.exe
[18:41:38] Core found.
[18:41:38] Working on queue slot 02 [March 2 18:41:38 UTC]
[18:41:38] + Working ...
[18:41:38] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 02 -np 4 -checkpoint 15 -forceasm -verbose -lifeline 3324 -version 630'

[18:41:38] 
[18:41:38] *------------------------------*
[18:41:38] Folding@Home Gromacs SMP Core
[18:41:38] Version 2.19 (Mar 12, 2010)
[18:41:38] 
[18:41:38] Preparing to commence simulation
[18:41:38] - Assembly optimizations manually forced on.
[18:41:38] - Not checking prior termination.
[18:41:38] Need version 227
[18:41:38] Error: Work unit read from disk is invalid
[18:41:38] 
[18:41:38] Folding@home Core Shutdown: CORE_OUTDATED
[18:41:42] CoreStatus = 6E (110)
[18:41:42] + Core out of date. Auto updating...
[18:41:42] - Attempting to download new core...
[18:41:42] + Downloading new core: FahCore_a3.exe
[18:41:42] Downloading core (/~pande/Win32/x86/Core_a3.fah from www.stanford.edu)
After downloading a new A3 core, it then started this:

Code: Select all

[18:41:52] Verifying core Core_a3.fah...
[18:41:52] Signature is VALID
[18:41:52] 
[18:41:52] Trying to unzip core FahCore_a3.exe
[18:41:54] Decompressed FahCore_a3.exe (10057216 bytes) successfully
[18:41:59] + Core successfully engaged
[18:42:04] 
[18:42:04] + Processing work unit
[18:42:04] Core required: FahCore_a3.exe
[18:42:04] Core found.
[18:42:04] Working on queue slot 02 [March 2 18:42:04 UTC]
[18:42:04] + Working ...
[18:42:04] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 02 -np 4 -checkpoint 15 -forceasm -verbose -lifeline 3324 -version 630'

[18:42:04] 
[18:42:04] *------------------------------*
[18:42:04] Folding@Home Gromacs SMP Core
[18:42:04] Version 2.27 (Dec. 15, 2010)
[18:42:04] 
[18:42:04] Preparing to commence simulation
[18:42:04] - Assembly optimizations manually forced on.
[18:42:04] - Not checking prior termination.
[18:42:05] - Expanded 986829 -> 2040300 (decompressed 206.7 percent)
[18:42:05] Called DecompressByteArray: compressed_data_size=986829 data_size=2040300, decompressed_data_size=2040300 diff=0
[18:42:05] - Digital signature verified
[18:42:05] 
[18:42:05] Project: 10115 (Run 6, Clone 0, Gen 3)
[18:42:05] 
[18:42:05] Assembly optimizations on if available.
[18:42:05] Entering M.D.
[18:42:10] Mapping NT from 4 to 4 
[18:42:11] Completed 0 out of 2000000 steps  (0%)
Edit: Irrelevant comments and suppositions removed on 3/7.
Last edited by djchandler on Mon Mar 07, 2011 10:01 am, edited 2 times in total.
Folding for Cures
HendricksSA
Posts: 336
Joined: Fri Jun 26, 2009 4:34 am

Re: 171.64.65.55 sending bad packets

Post by HendricksSA »

I went through a short spell of "no work" from this server on the 2nd and 3rd. It seemed to coincide with delivery of the new A3-227 core. All my machines finally got work. Two were assigned to 171.64.65.75 and are now chugging through Project 10114 with frame times between 22-27 minutes (X6 vs X4). I couldn't find an atom count for this A3 project. It seems like a whole bunch of new projects have hit the streets. I also processed a 6951 (from 128.143.199.96) which I couldn't find anything on in the Project Summaries.
dvanatta
Pande Group Member
Posts: 62
Joined: Tue Sep 14, 2010 7:00 pm

Re: 171.64.65.55 sending bad packets

Post by dvanatta »

OK, I think I've fixed it.
Lemme know.

-Dan
DavidMudkips
Posts: 15
Joined: Wed Sep 23, 2009 6:04 am

Re: 171.64.65.55 sending bad packets

Post by DavidMudkips »

Got same problem here, finally connected to another server after 7 attempts and got a WU

Code: Select all

[22:03:09] - Autosending finished units... [March 6 22:03:09 UTC]
[22:03:09] Trying to send all finished work units
[22:03:09] + Attempting to get work packet
[22:03:09] + No unsent completed units remaining.
[22:03:09] Passkey found
[22:03:09] - Autosend completed
[22:03:09] - Will indicate memory of 4087 MB
[22:03:09] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 14, Stepping: 5
[22:03:09] - Connecting to assignment server
[22:03:09] Connecting to http://assign.stanford.edu:8080/
[22:03:10] Posted data.
[22:03:10] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:03:10] + News From Folding@Home: Welcome to Folding@Home
[22:03:10] Loaded queue successfully.
[22:03:10] Sent data
[22:03:10] Connecting to http://171.64.65.55:8080/
[22:03:10] Posted data.
[22:03:10] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:03:10] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[22:03:28] + Attempting to get work packet
[22:03:28] Passkey found
[22:03:28] - Will indicate memory of 4087 MB
[22:03:28] - Connecting to assignment server
[22:03:28] Connecting to http://assign.stanford.edu:8080/
[22:03:29] Posted data.
[22:03:29] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:03:29] + News From Folding@Home: Welcome to Folding@Home
[22:03:29] Loaded queue successfully.
[22:03:29] Sent data
[22:03:29] Connecting to http://171.64.65.55:8080/
[22:03:29] Posted data.
[22:03:29] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:03:29] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[22:03:49] + Attempting to get work packet
[22:03:49] Passkey found
[22:03:49] - Will indicate memory of 4087 MB
[22:03:49] - Connecting to assignment server
[22:03:49] Connecting to http://assign.stanford.edu:8080/
[22:03:49] Posted data.
[22:03:49] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:03:49] + News From Folding@Home: Welcome to Folding@Home
[22:03:50] Loaded queue successfully.
[22:03:50] Sent data
[22:03:50] Connecting to http://171.64.65.55:8080/
[22:03:50] Posted data.
[22:03:50] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:03:50] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[22:04:13] + Attempting to get work packet
[22:04:13] Passkey found
[22:04:13] - Will indicate memory of 4087 MB
[22:04:13] - Connecting to assignment server
[22:04:13] Connecting to http://assign.stanford.edu:8080/
[22:04:13] Posted data.
[22:04:13] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:04:13] + News From Folding@Home: Welcome to Folding@Home
[22:04:13] Loaded queue successfully.
[22:04:13] Sent data
[22:04:13] Connecting to http://171.64.65.55:8080/
[22:04:14] Posted data.
[22:04:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:04:14] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[22:04:54] + Attempting to get work packet
[22:04:54] Passkey found
[22:04:54] - Will indicate memory of 4087 MB
[22:04:54] - Connecting to assignment server
[22:04:54] Connecting to http://assign.stanford.edu:8080/
[22:04:55] Posted data.
[22:04:55] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:04:55] + News From Folding@Home: Welcome to Folding@Home
[22:04:55] Loaded queue successfully.
[22:04:55] Sent data
[22:04:55] Connecting to http://171.64.65.55:8080/
[22:04:55] Posted data.
[22:04:55] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:04:55] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[22:06:23] + Attempting to get work packet
[22:06:23] Passkey found
[22:06:23] - Will indicate memory of 4087 MB
[22:06:23] - Connecting to assignment server
[22:06:23] Connecting to http://assign.stanford.edu:8080/
[22:06:24] Posted data.
[22:06:24] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:06:24] + News From Folding@Home: Welcome to Folding@Home
[22:06:24] Loaded queue successfully.
[22:06:24] Sent data
[22:06:24] Connecting to http://171.64.65.55:8080/
[22:06:24] Posted data.
[22:06:24] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:06:24] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[22:09:12] + Attempting to get work packet
[22:09:12] Passkey found
[22:09:12] - Will indicate memory of 4087 MB
[22:09:12] - Connecting to assignment server
[22:09:12] Connecting to http://assign.stanford.edu:8080/
[22:09:12] Posted data.
[22:09:12] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:09:12] + News From Folding@Home: Welcome to Folding@Home
[22:09:13] Loaded queue successfully.
[22:09:13] Sent data
[22:09:13] Connecting to http://171.64.65.55:8080/
[22:09:13] Posted data.
[22:09:13] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:09:13] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[22:14:37] + Attempting to get work packet
[22:14:37] Passkey found
[22:14:37] - Will indicate memory of 4087 MB
[22:14:37] - Connecting to assignment server
[22:14:37] Connecting to http://assign.stanford.edu:8080/
[22:14:38] Posted data.
[22:14:38] Initial: 40AB; - Successful: assigned to (171.64.65.75).
[22:14:38] + News From Folding@Home: Welcome to Folding@Home
[22:14:38] Loaded queue successfully.
[22:14:38] Sent data
[22:14:38] Connecting to http://171.64.65.75:8080/
[22:14:39] Posted data.
[22:14:39] Initial: 0000; - Receiving payload (expected size: 661247)
[22:14:46] - Downloaded at ~92 kB/s
[22:14:46] - Averaged speed for that direction ~92 kB/s
[22:14:46] + Received work.
[22:14:46] + Closed connections
[22:14:46] 
[22:14:46] + Processing work unit
[22:14:46] Core required: FahCore_a3.exe
[22:14:46] Core found.
[22:14:46] Working on queue slot 01 [March 6 22:14:46 UTC]
djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

Re: 171.64.65.55 sending bad packets

Post by djchandler »

Getting good data from 171.64.65.55 now, no communication errors. Thank you.

Code: Select all

[22:33:17] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:33:17] + News From Folding@Home: Welcome to Folding@Home
[22:33:17] Loaded queue successfully.
[22:33:17] Sent data
[22:33:17] Connecting to http://171.64.65.55:8080/
[22:33:18] Posted data.
[22:33:18] Initial: 0000; - Receiving payload (expected size: 535436)
[22:33:19] - Downloaded at ~522 kB/s
[22:33:19] - Averaged speed for that direction ~576 kB/s
[22:33:19] + Received work.
[22:33:19] Trying to send all finished work units
[22:33:19] + No unsent completed units remaining.
[22:33:19] + Closed connections
[22:33:19] 
[22:33:19] + Processing work unit
[22:33:19] Core required: FahCore_a3.exe
[22:33:19] Core found.
[22:33:19] Working on queue slot 04 [March 4 22:33:19 UTC]
Folding for Cures
dvanatta
Pande Group Member
Posts: 62
Joined: Tue Sep 14, 2010 7:00 pm

Re: 171.64.65.55 sending bad packets

Post by dvanatta »

:-)
djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

Re: 171.64.65.55 sending bad packets

Post by djchandler »

It was working! But bad packets are getting sent again. The good news is that it didn't make my machine sit for hours with nothing to do this time.

Code: Select all

[22:40:36] + Attempting to send results [March 8 22:40:36 UTC]
[22:40:36] - Reading file work/wuresults_09.dat from core
[22:40:36]   (Read 3526051 bytes from disk)
[22:40:36] Connecting to http://128.143.199.96:8080/
[22:40:59] Posted data.
[22:40:59] Initial: 0000; - Uploaded at ~149 kB/s
[22:40:59] - Averaged speed for that direction ~158 kB/s
[22:40:59] + Results successfully sent
[22:40:59] Thank you for your contribution to Folding@Home.
[22:40:59] + Number of Units Completed: 407

[22:41:04] Trying to send all finished work units
[22:41:04] + No unsent completed units remaining.
[22:41:04] - Preparing to get new work unit...
[22:41:04] Cleaning up work directory
[22:41:04] + Attempting to get work packet
[22:41:04] Passkey found
[22:41:04] - Will indicate memory of 2048 MB
[22:41:04] - Connecting to assignment server
[22:41:04] Connecting to http://assign.stanford.edu:8080/
[22:41:05] Posted data.
[22:41:05] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:41:05] + News From Folding@Home: Welcome to Folding@Home
[22:41:05] Loaded queue successfully.
[22:41:05] Sent data
[22:41:05] Connecting to http://171.64.65.55:8080/
[22:41:05] Posted data.
[22:41:05] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:41:05] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[22:41:12] + Attempting to get work packet
[22:41:12] Passkey found
[22:41:12] - Will indicate memory of 2048 MB
[22:41:12] - Connecting to assignment server
[22:41:12] Connecting to http://assign.stanford.edu:8080/
[22:41:13] Posted data.
[22:41:13] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:41:13] + News From Folding@Home: Welcome to Folding@Home
[22:41:13] Loaded queue successfully.
[22:41:13] Sent data
[22:41:13] Connecting to http://171.64.65.55:8080/
[22:41:14] Posted data.
[22:41:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:41:14] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[22:41:24] + Attempting to get work packet
[22:41:24] Passkey found
[22:41:24] - Will indicate memory of 2048 MB
[22:41:24] - Connecting to assignment server
[22:41:24] Connecting to http://assign.stanford.edu:8080/
[22:41:25] Posted data.
[22:41:25] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:41:25] + News From Folding@Home: Welcome to Folding@Home
[22:41:25] Loaded queue successfully.
[22:41:25] Sent data
[22:41:25] Connecting to http://171.64.65.55:8080/
[22:41:25] Posted data.
[22:41:25] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:41:25] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[22:41:57] + Attempting to get work packet
[22:41:57] Passkey found
[22:41:57] - Will indicate memory of 2048 MB
[22:41:57] - Connecting to assignment server
[22:41:57] Connecting to http://assign.stanford.edu:8080/
[22:41:57] Posted data.
[22:41:57] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:41:57] + News From Folding@Home: Welcome to Folding@Home
[22:41:58] Loaded queue successfully.
[22:41:58] Sent data
[22:41:58] Connecting to http://171.64.65.55:8080/
[22:41:58] Posted data.
[22:41:58] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:41:58] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[22:42:49] + Attempting to get work packet
[22:42:49] Passkey found
[22:42:49] - Will indicate memory of 2048 MB
[22:42:49] - Connecting to assignment server
[22:42:49] Connecting to http://assign.stanford.edu:8080/
[22:42:49] Posted data.
[22:42:49] Initial: 40AB; - Successful: assigned to (171.64.65.55).
[22:42:49] + News From Folding@Home: Welcome to Folding@Home
[22:42:50] Loaded queue successfully.
[22:42:50] Sent data
[22:42:50] Connecting to http://171.64.65.55:8080/
[22:42:50] Posted data.
[22:42:50] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[22:42:50] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[22:44:24] + Attempting to get work packet
[22:44:24] Passkey found
[22:44:24] - Will indicate memory of 2048 MB
[22:44:24] - Connecting to assignment server
[22:44:24] Connecting to http://assign.stanford.edu:8080/
[22:44:25] Posted data.
[22:44:25] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[22:44:25] + News From Folding@Home: Welcome to Folding@Home
[22:44:25] Loaded queue successfully.
[22:44:25] Sent data
[22:44:25] Connecting to http://171.64.65.54:8080/
[22:44:26] Posted data.
[22:44:26] Initial: 0000; - Receiving payload (expected size: 1765239)
[22:44:29] - Downloaded at ~574 kB/s
[22:44:29] - Averaged speed for that direction ~800 kB/s
[22:44:29] + Received work.
Folding for Cures
dvanatta
Pande Group Member
Posts: 62
Joined: Tue Sep 14, 2010 7:00 pm

Re: 171.64.65.55 sending bad packets

Post by dvanatta »

Strange, I've been travelling and haven't touched anything since Sunday.

OK, maybe I did execute a rather CPU intensive process last night (finished now)... That might have tripped up the server... Let's see if this keeps happening.
djchandler
Posts: 60
Joined: Mon Aug 03, 2009 6:43 pm
Hardware configuration: AMD Ryzen 7 5700G with Radeon Graphics 3.80 GHz
16.0 GB
HP Pavilion Desktop model TP01-2xxx without discrete video card
Windows 11 Pro
Native client running 1 slot, 8 cores

Re: 171.64.65.55 sending bad packets

Post by djchandler »

Still happening as I type this @ 02:03 GMT.
Folding for Cures
connor3485
Posts: 1
Joined: Tue Feb 22, 2011 1:34 am

Re: 171.64.65.55 sending bad packets

Post by connor3485 »

I am having the same issue.
Post Reply