171.64.65.64 (Windows SMP) problem

[Fireclown]

According to serverstats, it's DL has only 1 day left. I am constantly stuck in the following loop:

[15:23:06] Connecting to http://assign.stanford.edu:8080/
[15:23:07] Posted data.
[15:23:07] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[15:23:07] + News From Folding@Home: Welcome to Folding@Home
[15:23:07] Loaded queue successfully.
[15:23:07] Connecting to http://171.64.65.64:8080/
[15:25:07] Posted data.
[15:26:55] Initial: 484A; - Error: Bad packet type from server, expected work assignment
[15:26:55] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[15:27:09] + Attempting to get work packet
[15:27:09] - Will indicate memory of 12286 MB
[15:27:09] - Connecting to assignment server
[15:27:09] Connecting to http://assign.stanford.edu:8080/
[15:27:10] Posted data.
[15:27:10] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[15:27:10] + News From Folding@Home: Welcome to Folding@Home
[15:27:10] Loaded queue successfully.
[15:27:10] Connecting to http://171.64.65.64:8080/
[15:29:10] Posted data.
[15:30:08] Initial: 484A; - Error: Bad packet type from server, expected work assignment
[15:30:08] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.

Also interesting to note is there is always a 2 minute pause between connecting to the server and the "Posted data" message, if that helps at all.

[bruce]

The "bad packet" message generally means that you're communicating through a proxy that is doing bad things to some of the protocol messages.

[toTOW]

Or maybe that you don't accept big WUs ?

[Fireclown]

No I do accept big WU's, and I am certainly not intentionally using a proxy.

I am in South Africa and we have a pretty small pipe overseas, and I think my ISP proxies all traffic "transparently". Guess its more like "slightly opaquely" than transparently. They do it to conserve international bandwidth but I have occasionally had issues that would be explained by a proxy before. After a while I eventually do get a WU but I do get the above error quite a few times. I will report this to my ISP.

Thank you for the responses.

[SidVicious]

I'm experiencing a very similar issue : "Error: Bad work unit. Digital signatures don't match" & "Initial: 0000; - Error: Bad packet type from server, expected work assignment"

I tried the usual tricks, deleting the core, queue.dat and work folder to no avail, I keep getting bad WUs from this server.

-----EDIT-----

The server stopped sending me crap WU on or around 0115 GMT

Code: Select all

--- Opening Log file [October 30 00:21:38 UTC] 


# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.24R3

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\Folding\SMP
Service: C:\Program Files\Folding\SMP\smp
Arguments: -svcstart -d C:\Program Files\Folding\SMP -local -smp 4 -verbosity 9 -forceasm 

Launched as a service.
Entered C:\Program Files\Folding\SMP to do work.

[00:21:38] - Ask before connecting: No
[00:21:38] - User name: SidVicious (Team 40051)
[00:21:38] - User ID: 7BA100314E7ABA64
[00:21:38] - Machine ID: 1
[00:21:38] 
[00:21:38] Could not open work queue, generating new queue...
[00:21:38] - Preparing to get new work unit...
[00:21:38] Cleaning up work directory
[00:21:38] - Autosending finished units... [October 30 00:21:38 UTC]
[00:21:38] Trying to send all finished work units
[00:21:38] + No unsent completed units remaining.
[00:21:38] - Autosend completed
[00:21:38] + Attempting to get work packet
[00:21:38] - Will indicate memory of 2048 MB
[00:21:38] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[00:21:38] - Connecting to assignment server
[00:21:38] Connecting to http://assign.stanford.edu:8080/
[00:21:39] Posted data.
[00:21:39] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:21:39] + News From Folding@Home: Welcome to Folding@Home
[00:21:39] Loaded queue successfully.
[00:21:39] Connecting to http://171.64.65.64:8080/
[00:21:44] Posted data.
[00:21:44] Initial: 0000; - Receiving payload (expected size: 4714624)
[00:22:00] - Downloaded at ~287 kB/s
[00:22:00] - Averaged speed for that direction ~287 kB/s
[00:22:00] + Received work.
[00:22:00] + Closed connections
[00:22:00] 
[00:22:00] + Processing work unit
[00:22:00] Work type a1 not eligible for variable processors
[00:22:00] Core required: FahCore_a1.exe
[00:22:00] Core found.
[00:22:00] Using generic mpiexec calls
[00:22:00] Working on queue slot 01 [October 30 00:22:00 UTC]
[00:22:00] + Working ...
[00:22:00] - Calling 'mpiexec -np 4 -channel auto -host 127.0.0.1 FahCore_a1.exe -dir work/ -suffix 01 -checkpoint 3 -service -forceasm -verbose -lifeline 2396 -version 624'

[00:22:00] 
[00:22:00] *------------------------------*
[00:22:00] Folding@Home Gromacs SMP Core
[00:22:00] Version 1.74 (March 10, 2007)
[00:22:00] 
[00:22:00] Preparing to commence simulation
[00:22:00] - Assembly optimizations manually forced on.
[00:22:00] - Not checking prior termination.
[00:22:14] - Expanded 4714112 -> 24426905 (decompressed 518.1 percent)
[00:22:14] - Error: Bad work unit. Digital signatures don't match
[00:22:14] Error: Could not open work file
[00:22:14] 
[00:22:14] Folding@home Core Shutdown: FILE_IO_ERROR
[00:22:14] Finalizing output
[00:22:36] Service stop request received.
[00:22:36] ***** Got a SIGTERM signal (2)
[00:22:36] Killing all core threads
[00:22:36] Killing 4 cores
[00:22:36] Killing core 0
[00:22:36] Killing core 1
[00:22:36] Killing core 2
[00:22:36] Killing core 3

--- Opening Log file [October 30 00:29:10 UTC] 


# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.24R3

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Program Files\Folding\SMP
Service: C:\Program Files\Folding\SMP\smp
Arguments: -svcstart -d C:\Program Files\Folding\SMP -local -smp 4 -verbosity 9 -forceasm 

Launched as a service.
Entered C:\Program Files\Folding\SMP to do work.

[00:29:10] - Ask before connecting: No
[00:29:10] - User name: SidVicious (Team 40051)
[00:29:10] - User ID: 7BA100314E7ABA64
[00:29:10] - Machine ID: 1
[00:29:10] 
[00:29:10] Work directory not found. Creating...
[00:29:10] Could not open work queue, generating new queue...
[00:29:10] - Preparing to get new work unit...
[00:29:10] Cleaning up work directory
[00:29:10] - Autosending finished units... [October 30 00:29:10 UTC]
[00:29:10] Trying to send all finished work units
[00:29:10] + No unsent completed units remaining.
[00:29:10] - Autosend completed
[00:29:10] + Attempting to get work packet
[00:29:10] - Will indicate memory of 2048 MB
[00:29:10] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[00:29:10] - Connecting to assignment server
[00:29:10] Connecting to http://assign.stanford.edu:8080/
[00:29:11] Posted data.
[00:29:11] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[00:29:11] + News From Folding@Home: Welcome to Folding@Home
[00:29:11] Loaded queue successfully.
[00:29:11] Connecting to http://171.64.65.64:8080/
[00:29:14] Posted data.
[00:29:14] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[00:29:14] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.