LHC@home

Just got in.. restored from standby.
Noticed a dead work unit.

LHC@home - 2004-10-13 01:12:39 - Started upload of v64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 08:16:20 - Result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 exited with zero status but no 'finished' file
LHC@home - 2004-10-13 08:16:20 - If this happens repeatedly you may need to reset the project.
LHC@home - 2004-10-13 08:16:39 - Restarting result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 using sixtrack version 4.46
LHC@home - 2004-10-13 08:16:43 - Temporarily failed upload of v64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 08:16:43 - Backing off 1 minutes and 0 seconds on transfer of file v64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 08:17:43 - Started upload of v64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 08:17:50 - Finished upload of v64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 08:17:50 - Throughput 9906 bytes/sec
LHC@home - 2004-10-13 08:17:52 - Couldn't delete file projectslhcathome.cern.chv64lhc1000profive25s10_12584.96_1_sixvf_25919_1_0
LHC@home - 2004-10-13 19:10:34 - Result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 exited with zero status but no 'finished' file
LHC@home - 2004-10-13 19:10:34 - If this happens repeatedly you may need to reset the project.
LHC@home - 2004-10-13 19:10:34 - Restarting result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 using sixtrack version 4.46



actually, just noticed that it nuked that same work unit from this morning. I can't confirm what I did on the earlier failure, but I do know that the latest fail was when i came in and restored from standby.
______________________________________________________________
Did your tech wear a static strap? No? Well, there ya go! :p

I used system restore once before, I have since swore it off, (long story) but it will convert the executables back to a previous version and with the delicate balance of BOINC and all the code floating around it just gets reverted and when it is attempted to be ran everything just goes dead. There currently is nothing you can to except backup up and restore the BOINC directory do avoid this. However the easier solution is just not to use system restore if at all possible. ;)

If you check the names of the units you will find that they are the same and the last line of your log states that the unit is restarted.
If I read it correct the unit is ok and getting crunched.

LHC@home - 2004-10-13 19:10:34 - Result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 exited with...
...2004-10-13 19:10:34 - Restarting result v64lhc1000prosix29s12_1459.27_1_sixvf_20083_1 using sixtrack version 4.46

> I used system restore once ...

System standby.
aka sleep mode.
Laptops had it for the last decade. Desktops had it for the last couple years.
Press a button.. pc takes a nap.. press it again, and it starts where it left off.



______________________________________________________________
Did your tech wear a static strap? No? Well, there ya go! :p