Project: 11270 (Run 7, Clone 288, Gen 13)

[Baowoulf]

After the stubborn server problem last weekend was fixed and all the WU's started being accepted I had one that didn't send and gave me some message about a problem with unit.

Code: Select all

[22:44:40] Completed 47500 out of 250000 steps  (19%)
[22:53:48] Project: 6504 (Run 1, Clone 134, Gen 43)
[22:53:48] - Read packet limit of 540015616... Set to 524286976.


[22:53:48] + Attempting to send results [October 31 22:53:48 UTC]
[22:53:50] + Results successfully sent
[22:53:50] Thank you for your contribution to Folding@Home.
[22:53:50] + Number of Units Completed: 13

[22:53:50] Project: 11270 (Run 7, Clone 288, Gen 13)
[22:53:50] - Read packet limit of 540015616... Set to 524286976.


[22:53:50] + Attempting to send results [October 31 22:53:50 UTC]
[22:53:54] - Server reports problem with unit.
[22:53:54] + Working...
[23:02:26] Writing local files
[23:02:26] Completed 50000 out of 250000 steps  (20%)

As you can see the first WU is sent successfully but the second encounters a problem. What's the problem with WU and is there any way to fix it or is it lost?

Here is where I first downloaded the WU in question.

Code: Select all

--- Opening Log file [October 30 21:04:07 UTC] 


# Windows CPU Systray Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C:\Documents and Settings\Diane Arreola\Application Data\Folding@home-x86


[21:04:07] - Ask before connecting: No
[21:04:07] - User name: Baowoulf (Team 48759)
[21:04:07] - User ID: 647D3CB2A4A50E2
[21:04:07] - Machine ID: 1
[21:04:07] 
[21:04:07] Loaded queue successfully.
[21:04:08] Initialization complete
[21:04:08] - Preparing to get new work unit...
[21:04:08] + Attempting to get work packet
[21:04:08] Project: 6504 (Run 1, Clone 134, Gen 43)
[21:04:08] - Read packet limit of 540015616... Set to 524286976.


[21:04:08] + Attempting to send results [October 30 21:04:08 UTC]
[21:04:08] - Connecting to assignment server
[21:04:08] - Couldn't send HTTP request to server
[21:04:08]   (Got status 503)
[21:04:08] + Could not connect to Work Server (results)
[21:04:08]     (171.64.65.62:8080)
[21:04:08] + Retrying using alternative port
[21:04:08] - Couldn't send HTTP request to server
[21:04:08]   (Got status 503)
[21:04:08] + Could not connect to Work Server (results)
[21:04:08]     (171.64.65.62:80)
[21:04:08] - Error: Could not transmit unit 03 (completed October 30) to work server.
[21:04:08] - Read packet limit of 540015616... Set to 524286976.


[21:04:08] + Attempting to send results [October 30 21:04:08 UTC]
[21:04:08] - Successful: assigned to (171.67.108.33).
[21:04:08] + News From Folding@Home: Welcome to Folding@Home
[21:04:08] - Couldn't send HTTP request to server
[21:04:08]   (Got status 503)
[21:04:08] + Could not connect to Work Server (results)
[21:04:08]     (171.67.108.25:8080)
[21:04:08] + Retrying using alternative port
[21:04:08] Loaded queue successfully.
[21:04:08] - Couldn't send HTTP request to server
[21:04:08]   (Got status 503)
[21:04:08] + Could not connect to Work Server (results)
[21:04:08]     (171.67.108.25:80)
[21:04:08]   Could not transmit unit 03 to Collection server; keeping in queue.
[21:04:11] + Closed connections
[21:04:11] 
[21:04:11] + Processing work unit
[21:04:11] Core required: FahCore_78.exe
[21:04:11] Core found.
[21:04:11] Working on queue slot 04 [October 30 21:04:11 UTC]
[21:04:11] + Working ...
[21:04:12] 
[21:04:12] *------------------------------*
[21:04:12] Folding@Home Gromacs Core
[21:04:12] Version 1.90 (March 8, 2006)
[21:04:12] 
[21:04:12] Preparing to commence simulation
[21:04:12] - Looking at optimizations...
[21:04:12] - Created dyn
[21:04:12] - Files status OK
[21:04:12] - Expanded 375473 -> 1807444 (decompressed 481.3 percent)
[21:04:12] - Starting from initial work packet
[21:04:12] 
[21:04:12] Project: 11270 (Run 7, Clone 288, Gen 13)
[21:04:12] 
[21:04:12] Assembly optimizations on if available.
[21:04:12] Entering M.D.
[21:04:19] Protein: ALZHEIMERS DISEASE AMYLOID
[21:04:19] 
[21:04:19] Writing local files

Folding@Home Client Shutdown.

[bruce]

We've never had an official explanation of "...problem with a unit" but my best guess is that something was corrupted somewhere along the line and the server is saying that the WU does not pass the validity tests for accurate scientific results.

I'm not aware of WUs being accepted after they've gotten that message, but I can't see any reason to discard it until it has tried to upload a number of times. Eventually, you'll probably have to just discard it or wait until it expires and deletes itself.

[Baowoulf]

Well it was worth a shot. Thanks bruce.

[Fireball0236]

Bruce, I've received the same message this weekend, for 3 or 4 WUs. They were from different clients/pcs, the only thing they had in common were the Work Server (108.33) they came from. After my client received this message, it marked the WU as successfully uploaded, and thus I could no longer try and upload it. One time I took a complete copy of my directory, and tried uploading it; same result every single time...

Must have been on the server's end, as I've never had that message before, and when the server was having trouble I got it on all 3-4 Wus I had pending from that server...


~ Fireball0236

[VijayPande]

Thanks for the report. We'll look into it.

[Baowoulf]

Bruce, I've received the same message this weekend, for 3 or 4 WUs. They were from different clients/pcs, the only thing they had in common were the Work Server (108.33) they came from. After my client received this message, it marked the WU as successfully uploaded, and thus I could no longer try and upload it. One time I took a complete copy of my directory, and tried uploading it; same result every single time...

Must have been on the server's end, as I've never had that message before, and when the server was having trouble I got it on all 3-4 Wus I had pending from that server...


~ Fireball0236

How did it mark it as successfully uploaded? Mine I think deleted the WU after the server problem message. The slot where it was worked on in queue was then labeled empty/deleted.

[Fireball0236]

Successfully uploaded or not, the queue will always say "empty/deleted". For the first of the WUs I lost this way, I still had the work files, but it was removed from the queue; so I looked into the 3rd party tools if there was something that could generate a new queue. One of the queue information programs can output a whole lot more information than starting the client with "-queueinfo" can, one of those lines said that the WU was successfully uploaded. No luck recreating my queue, though; the only program that did that works only for v5 clients... (Afterwards I figured out that even if I had been able to recreate my queue, the server would've thrown the WU out every time I tried uploading it anyway).


~ Fireball0236