Message boards :
Number crunching :
New Flood of WU's
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Sep 04 Posts: 282 Credit: 1,415,417 RAC: 0 |
10.000 ready to crunch... and rising! Sysfried |
Send message Joined: 2 Sep 04 Posts: 378 Credit: 10,765 RAC: 0 |
10.000 ready to crunch... and rising! Thanks. Just clicked the update button. I'm not the LHC Alex. Just a number cruncher like everyone else here. |
Send message Joined: 29 Sep 04 Posts: 42 Credit: 11,505,632 RAC: 0 |
Seems to be christmas!! CoM |
Send message Joined: 27 Sep 04 Posts: 282 Credit: 1,415,417 RAC: 0 |
20.000 and counting |
Send message Joined: 13 Jul 05 Posts: 143 Credit: 263,300 RAC: 0 |
WaaHoooo!! Here we go again !! More work for the dedicated crunchers. Hang on tight, cuz I dunno just how big this thing's agonna get ..... If I've lived this long, I've gotta be that old |
Send message Joined: 27 Sep 04 Posts: 282 Credit: 1,415,417 RAC: 0 |
WaaHoooo!! Here we go again !! doh, i missed them merry x-mas anyways! cheers, sysfried |
Send message Joined: 18 Sep 04 Posts: 38 Credit: 173,867 RAC: 0 |
:) got a few |
Send message Joined: 30 Sep 04 Posts: 112 Credit: 104,059 RAC: 0 |
Got a few also but many of them seem to be erroring out.... 12/24/2006 4:43:21 AM|lhcathome|Throughput 18662 bytes/sec 12/24/2006 4:43:24 AM|lhcathome|Sending scheduler request to http://lhcathome.cern.ch/lhcathome_cgi/cgi 12/24/2006 4:43:24 AM|lhcathome|Reason: To report completed tasks 12/24/2006 4:43:24 AM|lhcathome|Reporting 1 tasks 12/24/2006 4:43:29 AM|lhcathome|Scheduler request succeeded 12/24/2006 5:39:50 AM|lhcathome|Task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 exited with zero status but no 'finished' file 12/24/2006 5:39:50 AM|lhcathome|If this happens repeatedly you may need to reset the project. 12/24/2006 5:39:50 AM||Rescheduling CPU: application exited 12/24/2006 5:39:50 AM|lhcathome|Restarting task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 using sixtrack version 467 12/24/2006 6:38:35 AM|lhcathome|Task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 exited with zero status but no 'finished' file 12/24/2006 6:38:35 AM|lhcathome|If this happens repeatedly you may need to reset the project. 12/24/2006 6:38:35 AM||Rescheduling CPU: application exited 12/24/2006 6:38:35 AM|lhcathome|Restarting task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 using sixtrack version 467 12/24/2006 6:48:39 AM||Rescheduling CPU: application exited 12/24/2006 6:48:39 AM|lhcathome|Computation for task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 finished 12/24/2006 6:48:40 AM|lhcathome|Starting task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__12_14__6__85_1_sixvf_boinc322915_1 using sixtrack version 467 12/24/2006 6:48:42 AM|lhcathome|Started upload of file wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0_0 12/24/2006 6:48:47 AM|lhcathome|Finished upload of file wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0_0 12/24/2006 6:48:47 AM|lhcathome|Throughput 19004 bytes/sec 12/24/2006 6:48:52 AM|lhcathome|Sending scheduler request to http://lhcathome.cern.ch/lhcathome_cgi/cgi 12/24/2006 6:48:52 AM|lhcathome|Reason: To report completed tasks 12/24/2006 6:48:52 AM|lhcathome|Reporting 1 tasks 12/24/2006 6:48:57 AM|lhcathome|Scheduler request succeeded |
Send message Joined: 30 Sep 04 Posts: 112 Credit: 104,059 RAC: 0 |
Here's the specs on this box: AMD Athlon XP2400+ at Stock Speeds 1GB of PC3200 RAM ABIT NF7-2 Motherboard 80gb Western Digital IDE HDD NVIDIA GF2 MX400 Video Card Nothing special, just a basic cruncher.... Any ideas? |
Send message Joined: 13 Jul 05 Posts: 143 Credit: 263,300 RAC: 0 |
Logan5-- Your log listings show a possible solution: 12/24/2006 5:39:50 AM|lhcathome|Task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 exited with zero status but no 'finished' file 12/24/2006 5:39:50 AM|lhcathome|If this happens repeatedly you may need to reset the project. 12/24/2006 5:39:50 AM||Rescheduling CPU: application exited 12/24/2006 5:39:50 AM|lhcathome|Restarting task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 using sixtrack version 467 12/24/2006 6:38:35 AM|lhcathome|Task wsep0.55_0.2_v650.55_0.2__1__64.319_59.329__14_16__6__35_1_sixvf_boinc322922_0 exited with zero status but no 'finished' file 12/24/2006 6:38:35 AM|lhcathome|If this happens repeatedly you may need to reset the project. 12/24/2006 6:38:35 AM||Rescheduling CPU: application exited First thing I'd try is resetting the project, to see if a fresh program load might clear up the problem. Your machine seems to be well-suited to the crunching task, but check for dust on your cooling fins. Running a machine 24/7 in any environment other than a "clean room" setting will pick up lots of foreign material -- and if you have a cat or dog, it's even worse ... Good Luck If I've lived this long, I've gotta be that old |
Send message Joined: 1 Sep 04 Posts: 275 Credit: 2,652,452 RAC: 0 |
The "exited with zero status but no finished file" message can usually be ignored. It is a miscommunication between the client and the app and can be caused by changing the time clock on your host. Usually the client will fix the problem without intravention. BOINC WIKI BOINCing since 2002/12/8 |
Send message Joined: 27 Sep 04 Posts: 282 Credit: 1,415,417 RAC: 0 |
Amazingly: Up, 17661 workunits to crunch NEW WORK! |
Send message Joined: 30 Dec 06 Posts: 2 Credit: 84 RAC: 0 |
Does this means that there were 17661 individual work units or was it 17661/5 or *5 units in all as each work unit is sent out 5 times? |
Send message Joined: 4 Oct 06 Posts: 38 Credit: 24,908 RAC: 0 |
Does this means that there were 17661 individual work units or was it 17661/5 or *5 units in all as each work unit is sent out 5 times? There were 3532 (~17661/5) different WUs to crunch at that moment. Each of the 3532 WUs were copied 5 times and sent out. (I just noticed the terminology on the main page is a little misleading stating as "xxxxx workunits in progress" while the same number is reported on the server status page as "xxxxx results in progress") Don't get distracted by shiny objects. |
©2024 CERN