Development for LHC@home

Yes we used to have that happen once in a while over at the original T4T/vLHC and the first thing was trying the reboot as you found out and sometimes that will work.

It does depend on if you run other projects at the same time or like over at Atlas if you try to run more than one task when you don't have enough Ram.

Two of your hosts only have 6 and 4GB ram so you can have problems if you try running a CMS-dev along with other tasks on a host such as your quad-core with only 4GB ram.

But if you have a task that says it has been running far beyond the 24hrs it may appear to be running when you check the Boinc Manager even after 50 hours but if you check the Boinc *checkpoint* it may say it stopped running after just a couple hours.

Those just need to be aborted and the VB Manager cleaned up and then give it another try but remembering not to try running too many other types of tasks at the same time.

Of course adding Ram to those 2 hosts will make a big difference too.

---

Mad Scientist For Life

http://boincai05.cern.ch/CMS-dev/results.php?hostid=306

ritterm, I just checked that host and your other ones and they all were working and getting completed tasks and no errors.

You can't do better than that!

(only one error and it was on one of your other pc's)

http://boincai05.cern.ch/CMS-dev/results.php?hostid=304

So that is 26 valid and just one error.

---

Mad Scientist For Life

...I just checked that host and your other ones and they all were working and getting completed tasks and no errors.

You can't do better than that!

That's true, but...I think I ought to be able to do better than having to re-boot one host everyday after its task has "stalled out" in order to successfully complete it. ;-)

I know there can be all sorts of reasons why one host in particular has a problem, but it would be nice to know why. Maybe I'll never know, but that's why I posed the question here. :-)

Anyway, I'm taking a break from this project for a bit to work on some others prior to the BOINC Pentathlon.

Cheers!

MarkR

Maybe when you get the chance you should update your old version of VB

I usually do a clean install but of course you can try just the update and I always make sure I download the *Extension Pack along with the VB update.

You are still running the old VirtualBox Version: 4.3.12

I admit I usually don't go all the way to the newest version and I think most or all of mine are using VB version 4.3.18

Have a fine weekend

-Samson

---

Mad Scientist For Life