Page 1 of 1

Project: 6040 (Run 0, Clone 145, Gen 100)

Posted: Sun Nov 28, 2010 11:22 am
by poiuyut
UNSTABLE_MACHINE as soon as this work unit started, followed by redoing the same unit, successfully the second time. So, no real problem, but I haven't seen this happen before.

Code: Select all

[18:07:34] Project: 6040 (Run 0, Clone 145, Gen 100)
[18:07:34] 
[18:07:34] Entering M.D.
[18:07:42] Completed 0 out of 250000 steps  (0%)
[18:07:43] mdrun returned 255
[18:07:43] Going to send back what have done -- stepsTotalG=250000
[18:07:43] Work fraction=429496762368.0000 steps=250000.
[18:07:46] logfile size=12873 infoLength=12873 edr=25 trr=1
[18:07:46] logfile size: 12873 info=12873 bed=25 hdr=1
[18:07:46] - Writing 13411 bytes of core data to disk...
[18:07:47]   ... Done.
[18:08:39] 
[18:08:39] Folding@home Core Shutdown: UNSTABLE_MACHINE
[18:08:39] CoreStatus = 7A (122)
[18:08:39] Sending work to server
[18:08:39] Project: 6040 (Run 0, Clone 145, Gen 100)


[18:08:39] + Attempting to send results [November 25 18:08:39 UTC]
[18:08:39] - Reading file work/wuresults_00.dat from core
[18:08:39]   (Read 13411 bytes from disk)
[18:08:39] Connecting to http://171.64.65.54:8080/
[18:08:40] Posted data.
[18:08:40] Initial: 0000; - Uploaded at ~14 kB/s
[18:08:40] - Averaged speed for that direction ~74 kB/s
[18:08:40] + Results successfully sent
[18:08:40] Thank you for your contribution to Folding@Home.
[18:08:40] Trying to send all finished work units
[18:08:40] + No unsent completed units remaining.
[18:08:40] - Preparing to get new work unit...
[18:08:40] Cleaning up work directory
[18:08:40] + Attempting to get work packet
[18:08:40] Passkey found
[18:08:40] - Will indicate memory of 1171 MB
[18:08:40] - Connecting to assignment server
[18:08:40] Connecting to http://assign.stanford.edu:8080/
[18:08:40] Posted data.
[18:08:40] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[18:08:40] + News From Folding@Home: Welcome to Folding@Home
[18:08:40] Loaded queue successfully.
[18:08:40] Connecting to http://171.64.65.54:8080/
[18:08:43] Posted data.
[18:08:43] Initial: 0000; - Receiving payload (expected size: 7884376)
[18:08:57] - Downloaded at ~549 kB/s
[18:08:57] - Averaged speed for that direction ~512 kB/s
[18:08:57] + Received work.
[18:08:57] Trying to send all finished work units
[18:08:57] + No unsent completed units remaining.
[18:08:57] + Closed connections
[18:09:02] 
[18:09:02] + Processing work unit
[18:09:02] Core required: FahCore_a3.exe
[18:09:02] Core found.
[18:09:02] Working on queue slot 01 [November 25 18:09:02 UTC]
[18:09:02] + Working ...
[18:09:02] - Calling './FahCore_a3.exe -dir work/ -nice 19 -suffix 01 -np 8 -priority 96 -checkpoint 5 -verbose -lifeline 2297 -version 629'

[18:09:02] 
[18:09:02] *------------------------------*
[18:09:02] Folding@Home Gromacs SMP Core
[18:09:02] Version 2.22 (June 10, 2010)
[18:09:02] 
[18:09:02] Preparing to commence simulation
[18:09:02] - Looking at optimizations...
[18:09:02] - Created dyn
[18:09:02] - Files status OK
[18:09:02] - Expanded 7883864 -> 10126021 (decompressed 128.4 percent)
[18:09:02] Called DecompressByteArray: compressed_data_size=7883864 data_size=10126021, decompressed_data_size=10126021 diff=0
[18:09:03] - Digital signature verified
[18:09:03] 
[18:09:03] Project: 6040 (Run 0, Clone 145, Gen 100)
[18:09:03] 
[18:09:03] Assembly optimizations on if available.
[18:09:03] Entering M.D.
[18:09:11] Completed 0 out of 250000 steps  (0%)
[18:18:56] Completed 2500 out of 250000 steps  (1%)
[18:28:39] Completed 5000 out of 250000 steps  (2%)
[18:38:25] Completed 7500 out of 250000 steps  (3%)

Re: Project: 6040 (Run 0, Clone 145, Gen 100)

Posted: Sun Nov 28, 2010 12:55 pm
by toTOW
First attempt :
Hi poiuyut (team 0),
Your WU (P6040 R0 C145 G100) was added to the stats database on 2010-11-25 11:05:32 for 0.27 points of credit.
Second attempt :
Hi poiuyut (team 0),
Your WU (P6040 R0 C145 G100) was added to the stats database on 2010-11-26 03:05:24 for 10229.5 points of credit.
The thing I don't understand is why it sent you the same WU twice since your UM error was successfully recorded ...