Posts by Holmis

1) Message boards : Number crunching : Status of the new clients (Message 6923) Posted 9 Apr 2005 by Holmis Post: > > They were chrunched using app. ver. 4.64 or am I misstaken. > > The bugfix is in app. ver. 4.66, right??? > > Great! How the hell did I get work for the broken client? Bad luck I guess. The first unit I got yesterday used 4.64 and the next used the new 4.66.
2) Message boards : Number crunching : Status of the new clients (Message 6915) Posted 9 Apr 2005 by Holmis Post: > Well, Trouble in Disneyland ... > > 84619 > 84143 > 84620 > > What is especially painful is that I know at least one of these ran for close > to the full 10 hours ... > They were chrunched using app. ver. 4.64 or am I misstaken. The bugfix is in app. ver. 4.66, right???
3) Message boards : Number crunching : New WU -- no check point. (Message 6909) Posted 9 Apr 2005 by Holmis Post: My first WU with the new app 4.66 seems to checkpoint ok. I shutdown boinc to defrag my harddrive and when I restarted it continued from the 10% it reached before the shutdown. All seems fine so far. This is the WU I'm host 21859.
4) Message boards : Number crunching : different credits for same unit - an unusual aspect of it (Message 5479) Posted 10 Dec 2004 by Holmis Post: If I remember correct they announced some time ago that the credit-system was goning to change here at LHC. You should get credit based on how well your result match the others. Close enough and you get full credit, a bit of and you get less and so on... Something like that anyway. It's better for us to get some credit even if the result don't match completley because we did crunch and dedicate CPU-time for the project. Look under the FAQ under 2.5 How and when do I get credit?
5) Message boards : Number crunching : Getting more than four or so WUs (Message 4489) Posted 27 Oct 2004 by Holmis Post: Under general preferences the setting "Connect to network about every x days" is responsible.
6) Message boards : Number crunching : I think restoring from System Standby killed a work unit. (Message 3811) Posted 14 Oct 2004 by Holmis Post: 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
7) Questions and Answers : Windows : Download errors (Message 3671) Posted 12 Oct 2004 by Holmis Post: As stated on the front page all server errors should be reported so here goes. I had a download error last nigth (all times GMT+1): Extract from log: LHC@home - 2004-10-12 00:54:32 - Requesting 9691 seconds of work LHC@home - 2004-10-12 00:54:32 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi LHC@home - 2004-10-12 00:54:54 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded LHC@home - 2004-10-12 00:54:54 - Started download of v64lhc1000profive23s8_10563.27_1_sixvf_12691.zip LHC@home - 2004-10-12 00:54:54 - Started download of v64lhc1000profive22s18_20578.57_1_sixvf_11862.zip LHC@home - 2004-10-12 00:55:17 - Giving up on download of v64lhc1000profive23s8_10563.27_1_sixvf_12691.zip: Downloaded file had wrong size: expected 277041, got 0 LHC@home - 2004-10-12 00:55:17 - Giving up on download of v64lhc1000profive22s18_20578.57_1_sixvf_11862.zip: Downloaded file had wrong size: expected 276833, got 0 LHC@home - 2004-10-12 00:55:17 - Started download of v64lhc1000profive22s18_20564.08_1_sixvf_11701.zip LHC@home - 2004-10-12 00:55:17 - MD5 computation error for v64lhc1000profive23s8_10563.27_1_sixvf_12691.zip: -108 LHC@home - 2004-10-12 00:55:17 - Checksum or signature error for v64lhc1000profive23s8_10563.27_1_sixvf_12691.zip LHC@home - 2004-10-12 00:55:17 - MD5 computation error for v64lhc1000profive22s18_20578.57_1_sixvf_11862.zip: -108 LHC@home - 2004-10-12 00:55:17 - Checksum or signature error for v64lhc1000profive22s18_20578.57_1_sixvf_11862.zip LHC@home - 2004-10-12 00:55:17 - Unrecoverable error for result v64lhc1000profive23s8_10563.27_1_sixvf_12691_2 (WU download error: couldn't get input files: v64lhc1000profive23s8_10563.27_1_sixvf_12691.zip: MD5 computation error ) LHC@home - 2004-10-12 00:55:17 - Unrecoverable error for result v64lhc1000profive22s18_20578.57_1_sixvf_11862_0 (WU download error: couldn't get input files: v64lhc1000profive22s18_20578.57_1_sixvf_11862.zip: MD5 computation error ) LHC@home - 2004-10-12 00:55:17 - Deferring communication with project for 1 minutes and 0 seconds LHC@home - 2004-10-12 00:55:38 - Giving up on download of v64lhc1000profive22s18_20564.08_1_sixvf_11701.zip: Downloaded file had wrong size: expected 276832, got 0 LHC@home - 2004-10-12 00:55:38 - MD5 computation error for v64lhc1000profive22s18_20564.08_1_sixvf_11701.zip: -108 LHC@home - 2004-10-12 00:55:38 - Checksum or signature error for v64lhc1000profive22s18_20564.08_1_sixvf_11701.zip LHC@home - 2004-10-12 00:55:38 - Unrecoverable error for result v64lhc1000profive22s18_20564.08_1_sixvf_11701_1 (WU download error: couldn't get input files: v64lhc1000profive22s18_20564.08_1_sixvf_11701.zip: MD5 computation error ) LHC@home - 2004-10-12 00:55:38 - Deferring communication with project for 1 minutes and 0 seconds
8) Message boards : Number crunching : Upload of WU yes......Upload of Ready to Report no (Message 2638) Posted 28 Sep 2004 by Holmis Post: > You might want to check if LHC now has 2 computers listed on your system. If > you DO have 2 comps, merge them and you might once again have access to your > older WUs... just a thought. > If the units aren't in the *.xml files the client will not recognize them.
9) Message boards : Number crunching : Upload of WU yes......Upload of Ready to Report no (Message 2532) Posted 28 Sep 2004 by Holmis Post: > 2004-09-27 18:08:10 - Can't resolve hostname www.lhcathome.cern.ch (valid > name, no data record of requested type) It seems to me that it's the wrong adress, I got this adress when I signed up. http://lhcathome.cern.ch What adress did you attach to??? If other than my above, try this instead...
10) Message boards : Number crunching : Upload of WU yes......Upload of Ready to Report no (Message 2302) Posted 25 Sep 2004 by Holmis Post: Redy to report means that BOINC is waiting to report to the scheduler that the work is done and uploaded. Try to manually update the project under the projects tab.

LHC@home