LHC@home

Hi,

I have two workunits that appear to be finished but somehow stuck.

They say "100.000%" under "Progress" and "---" under "To Completion", but they remain at "Running, high priority".

I have restarted the computer, restarted BOINC, and tried to suspend/resume, and to update the project, but the units stay the same.

The other info:
I am attempting to help test, running BOINC Manager pre-release 6.2.2 (32-bit Windows) on my Vista laptop.

It is set to run always.

Here is the startup information messages:
5/21/2008 8:11:20 PM||Starting BOINC client version 6.2.2 for windows_intelx86
5/21/2008 8:11:20 PM||This a development version of BOINC and may not function properly
5/21/2008 8:11:20 PM||log flags: task, file_xfer, sched_ops
5/21/2008 8:11:20 PM||Libraries: libcurl/7.18.0 OpenSSL/0.9.8e zlib/1.2.3
5/21/2008 8:11:20 PM||Executing as a daemon
5/21/2008 8:11:20 PM||Data directory: C:\\ProgramData\\BOINC
5/21/2008 8:11:20 PM||BOINC is running as a service and as a non-system user.
5/21/2008 8:11:21 PM||Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor TK-53 [x86 Family 15 Model 104 Stepping 1]
5/21/2008 8:11:21 PM||Processor features: fpu tsc pae nx sse sse2 pni 3dnow mmx
5/21/2008 8:11:21 PM||OS: Microsoft Windows Vista: Home Edition, (06.00.6000.00)
5/21/2008 8:11:21 PM||Memory: 958.00 MB physical, 2.12 GB virtual
5/21/2008 8:11:21 PM||Disk: 66.42 GB total, 9.53 GB free
5/21/2008 8:11:21 PM||Local time is UTC -7 hours
5/21/2008 8:11:21 PM||No coprocessors
5/21/2008 8:11:22 PM|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 706381; location: home; project prefs: default
5/21/2008 8:11:22 PM|boincsimap|URL: http://boinc.bio.wzw.tum.de/boincsimap/; Computer ID: 94539; location: home; project prefs: default
5/21/2008 8:11:22 PM|The Lattice Project|URL: http://boinc.umiacs.umd.edu/; Computer ID: 7420; location: (none); project prefs: default
5/21/2008 8:11:22 PM|climateprediction.net|URL: http://climateprediction.net/; Computer ID: 815601; location: home; project prefs: default
5/21/2008 8:11:22 PM|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1075031; location: home; project prefs: default
5/21/2008 8:11:22 PM|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9656796; location: home; project prefs: default
5/21/2008 8:11:22 PM|QMC@HOME|URL: http://qah.uni-muenster.de/; Computer ID: 85195; location: home; project prefs: default
5/21/2008 8:11:22 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4102266; location: home; project prefs: default
5/21/2008 8:11:22 PM|Spinhenge@home|URL: http://spin.fh-bielefeld.de/; Computer ID: 108636; location: home; project prefs: default
5/21/2008 8:11:22 PM|SZTAKI Desktop Grid|URL: http://szdg.lpds.sztaki.hu/szdg/; Computer ID: 287411; location: home; project prefs: default
5/21/2008 8:11:22 PM|malariacontrol.net|URL: http://www.malariacontrol.net/; Computer ID: 74245; location: (none); project prefs: default
5/21/2008 8:11:22 PM||General prefs: from http://predictor.scripps.edu/ (last modified 07-Jul-2007 12:39:15)
5/21/2008 8:11:22 PM||Host location: none
5/21/2008 8:11:22 PM||General prefs: using your defaults
5/21/2008 8:11:22 PM||Reading preferences override file
5/21/2008 8:11:22 PM||Preferences limit memory usage when active to 479.00MB
5/21/2008 8:11:22 PM||Preferences limit memory usage when idle to 862.20MB
5/21/2008 8:11:22 PM||Preferences limit disk usage to 8.60GB
5/21/2008 8:11:22 PM|lhcathome|Task wm72opt1_m72opt1__22__64.31_59.32__2_4__6__70_1_sixvf_boinc351227_2 is 2.63 days overdue.
5/21/2008 8:11:22 PM|lhcathome|You may not get credit for it. Consider aborting it.
5/21/2008 8:11:22 PM|lhcathome|Task wm72poc_m72zpoc__30__64.31_59.32__14_16__6__75_1_sixvf_boinc364072_3 is 0.13 days overdue.
5/21/2008 8:11:22 PM|lhcathome|You may not get credit for it. Consider aborting it.

---

Same problem here. This is my first LHC@Home unit so I don\'t have any \"it worked before\" to benchmark against. As I\'m writing this the work unit has been at 100% for 1hr 20mins and does not seem to be using any CPU usage on the WindowsXP task manager. However nor is it completing the task and other BOINC projects are waiting for it to finish.

I suppose if I has multiple processors I might not have even noticed this.

Same problem here. This is my first LHC@Home unit so I don\\\'t have any \\\"it worked before\\\" to benchmark against. As I\\\'m writing this the work unit has been at 100% for 1hr 20mins and does not seem to be using any CPU usage on the WindowsXP task manager. However nor is it completing the task and other BOINC projects are waiting for it to finish.

I suppose if I has multiple processors I might not have even noticed this.

Are you using a 6.2.x client? A number of people have had this problem with the version 6 clients. The answer seems to be to downgrade back to 5.10.45.

Hope this helps

Michael

Are you using a 6.2.x client? A number of people have had this problem with the version 6 clients. The answer seems to be to downgrade back to 5.10.45.

Hope this helps

Michael

Yes, it\\\'s the 6.2.17 client. Interesting to note it\\\'s a version problem. However, since I\\\'m running other projects I really don\\\'t want to go through the trouble of downgrading... also I\\\'ve personally found the 6.2.x series to be more sensitive and intelligent when it comes to determining idle time and running the cpu processing.

I have however got ONE lhc@home unit completed and reported (so I have 1 thing that my new project contribution works on it\\\'s own)... I did this by suspending the \\\'problem WU\\\' and the other one worked just fine. This one however continues to display the same behavior. Interestingly although it shows 100%, resuming it from suspension sends the progress meter down to 95% where it begins climbing back up to 100%. Once there however it continues to hang.

Currently I am just running LHC@Home on the one machine.

Yes, it\\\\\\\'s the 6.2.17 client. Interesting to note it\\\\\\\'s a version problem. However, since I\\\\\\\'m running other projects I really don\\\\\\\'t want to go through the trouble of downgrading... also I\\\\\\\'ve personally found the 6.2.x series to be more sensitive and intelligent when it comes to determining idle time and running the cpu processing.

I have however got ONE lhc@home unit completed and reported (so I have 1 thing that my new project contribution works on it\\\\\\\'s own)... I did this by suspending the \\\\\\\'problem WU\\\\\\\' and the other one worked just fine. This one however continues to display the same behavior. Interestingly although it shows 100%, resuming it from suspension sends the progress meter down to 95% where it begins climbing back up to 100%. Once there however it continues to hang.

Currently I am just running LHC@Home on the one machine.

The only thing I could suggest would be to try upgrading to the latest 6.2.18 client. I don\'t think it\'s helped other people, but you never know.

Michael

The only thing I could suggest would be to try upgrading to the latest 6.2.18 client. I don\\\\\\\'t think it\\\\\\\'s helped other people, but you never know.

Michael

Okay, I\\\'ve done this and am now running 6.2.18. It hasn\\\'t helped. I gave up on expecting this result to finish properly and decided that maybe the best thing to do was reset the specific computation/task. Unfortunately I messed up on this and ended up causing the task to end with a Compute Error (is this better than a result that hangs indefinitely? I don\\\'t know. At least this way the server gets contacted I guess). At the moment there is no more work available from the project so I will just have to wait and see what the future brings. I notice looking at the two tasks I have assigned that many other hosts are reporting one kind of error or another, so perhaps these issues are not isolated to myself. I\\\'ve got a 50% success rate myself :P

3 other BOINC projects active on this computer and reporting no issues.

Note: LHC Message Board doesn\'t seem to like my single apostraphe key.

06.09.2008 12:30 BST -

Hi,
Further to yesterday\'s news item, we are recommending that you download/use the 5.10.X version of the BOINC client for your operating system. We hope to have this sorted as soon as possible but with LHC turn on in 4 days everyone is busy preparing for that.
Later days,
Neasan

They haven\'t said why version 6 clients don\'t work but the most likely explanation is that the science application isn\'t compiled against the version 6 API.

Version 6 clients do work, it seems to be just some workunits on some peoples computers that have this problem. I haven\'t had any problems running LHC on 6.2.18, and as WildKard said above, 1 workunit completed and 1 failed on his PC.

Michael

I\\\'ve reset the project at least once since my last post. LHC has been quiet but finally two more WUs have come down the pipe and these ones are getting stuck within the first 10%, rather than waiting until reaching the end of the file. Again same symptoms as above: the computer\\\'s been left alone for 40+ minutes without any discernible change to the progress bar or the CPU time values. The process manager reports sixtrack_4.67_windows_intelx86.exe using 0% cpu and the System Idle Process in the 90% range.

This makes 1 success and 3 stuck WUs.

Again same symptoms as above: the computer\'s been left alone for 40+ minutes without any discernible change to the progress bar or the CPU time values.

Er.. that is to say 40+ minutes for each WU. it\'s probably longer than that, but 40 minutes is what I\'m able to confirm with no other CPU activity (however it is set to RUN ALWAYS so it could be longer). CPU time listed on BOINC for these units is less than 10 minutes altogether.

One other thing... whatever\'s going on with the sixtrack_4.67_windows_intelx86.exe , it seems to occasionally cause Windows to play the Error Sound Event. However I have no messages on screen or in the BOINC messages area to give me any more information. I\'ve checked the computer\'s event log and there\'s nothing in there either.

A also think I should mention that BOINC\'s running in a protected account mode, which means the exe is running as it\'s own limited user: boinc_project. (I think this is something new with 6.2.x). That *might* be a reason I\'m not getting an error pop-up.

One other thing... whatever\\\'s going on with the sixtrack_4.67_windows_intelx86.exe , it seems to occasionally cause Windows to play the Error Sound Event. However I have no messages on screen or in the BOINC messages area to give me any more information. I\\\'ve checked the computer\\\'s event log and there\\\'s nothing in there either.

A also think I should mention that BOINC\\\'s running in a protected account mode, which means the exe is running as it\\\'s own limited user: boinc_project. (I think this is something new with 6.2.x). That *might* be a reason I\\\'m not getting an error pop-up.

I got around the Vista permissions thing by installing Boinc in a separate directory than the default \'my programs\' location. I run it from it\'s own \'boinc\' folder on the C drive.

---

I'm not the LHC Alex. Just a number cruncher like everyone else here.