1) Message boards : Number crunching : Teams (Message 4751)
Posted 1 Mar 2017 by Profile Steve Hawker*
Any chance you can import all the teams please?
2) Message boards : News : New native Linux ATLAS application (Message 4706)
Posted 24 Feb 2017 by Profile Steve Hawker*
That is very strange, are you sure this message is for ATLAS? I have tested this app successfully on a machine without virtualbox.

Yes, for the Atlas. Only one application is allowed in the settings.

Packages installed (including SQUID), configured and tested (CVMFS probe)
Error message remained the same (no tasks + no VirtualBox )

Now, however, they do not really have on the server. I am waiting for new work

Are there any additional requirements for the host for these tasks? The size of the memory or disk, the number of CPUs, etc.

what did you do for the http proxy?

i ran the probe and it failed.

for fun i tried to get tasks and i too get the virtualbox message
3) Message boards : Number crunching : Host limited to only one task (Message 4308)
Posted 9 Nov 2016 by Profile Steve Hawker*
Yes, sorry. We reduced the number of tasks yesterday while experimenting with the multi-core Theory app. We have put it back to what it was (5).

Just had this with Benchmark. Server cancelled four because they weren't started by deadline. So:

1. Tasks are being sent out with 1 hour deadlines
2. I've been limited to one task even though I downloaded 8

The four that ran all had errors but I'm OK with that because dev site.
4) Message boards : ATLAS Application : New Experimental ATLAS Application (Message 3093)
Posted 29 Apr 2016 by Profile Steve Hawker*
Estimated duration ~75 hours
Actual duration ~ 3 minutes

Tasks say Running High Priority but no elapsed time and stuck at 0% for a few minutes as a minimum.
5) Message boards : Number crunching : Scheduler wait: VM environment needs to be cleaned up (Message 2767)
Posted 15 Apr 2016 by Profile Steve Hawker*
Had a couple of these now.

Linux, quad core, 8GB

Concurrent 2 x BitcoinUtopia + VirtualLHC@Home + Theory Simulation

Everything runs fine but I've now seen this twice. No way to recover so I abort.

2 from 57 tasks isn't a disaster but it just sits there so for unattended machines that IS a disaster


6) Message boards : News : Server Restart (Message 1895)
Posted 6 Feb 2016 by Profile Steve Hawker*
The sever has been restarted to hopefully address the issue of multiple tasks being sent to the BOINC client.

Not sure if it's had the desired effect.


Apparently I have 45 tasks on my machine. I actually have zero because I cant get new tasks since the server reset. Please also see this message:

7) Message boards : Number crunching : Disk Space warning following server reset (Message 1894)
Posted 6 Feb 2016 by Profile Steve Hawker*
Just tried to get a new task and got this message

Sat 06 Feb 2016 12:54:49 AM PST | CMS-dev | Message from server: CMS Simulation needs 3081.32MB more disk space. You currently have 6455.42 MB available and it needs 9536.74 MB.

I have allocated 100 GB for BOINC and its currently using 9 GB.

Sat 06 Feb 2016 12:54:22 AM PST | | Starting BOINC client version 7.2.42 for x86_64-pc-linux-gnu
Sat 06 Feb 2016 12:54:22 AM PST | | OS: Linux: 3.16.0-53-generic
Sat 06 Feb 2016 12:54:22 AM PST | | Memory: 7.80 GB physical, 8.00 GB virtual
Sat 06 Feb 2016 12:54:22 AM PST | | Disk: 285.41 GB total, 250.45 GB free
Sat 06 Feb 2016 12:54:22 AM PST | | VirtualBox version: 4.3.10_Ubuntur93012

I've never seen this message before having run CMS tasks on this machine since April 2015.
8) Message boards : Number crunching : Postponed: Please upgrade BOINC to the latest version (Message 1824)
Posted 3 Feb 2016 by Profile Steve Hawker*

You may find this useful:



9) Message boards : News : Migrating to vLHC@home (Message 1793)
Posted 2 Feb 2016 by Profile Steve Hawker*
Hi Steve,

I think that we found the reason why you got two tasks for the beta and changed the configuration so hopefully you will only get one in the future.

Thanks for acting on this, I will check

The direction that we would like to go is to have one LHC@home BOINC project which has different applications for the different experiments. With this in mind we have a number of options for the testing and development environment.

  • beta apps in the LHC@home project
  • a test/devel LHC@home project
  • separate projects per application

Which option is preferred?

As I mentioned in the "poll" thread, I would like to see sub-projects. If you have sub-projects, then two distinct and separate projects for prod and dev would be perfect.

I agree that this app is not quite ready for primetime but I hope that by starting a process of continuous improvement we can get there soon.

Unfortunately we need the virtualized approach and VBox is what the work has been based on up to now. We can try to address the issues but if this becomes a blocking issue we can review our options.

Well, I dont know why but I'm not gonna argue as its your show to run. I've had a bad time at ATLAS and most of that is due to VBox. CMS has been a smooth run so I'll stick with it.

In a different thread you wonder about community representation. You have it right here on the boards. The crunchers who care read the forums and the crunchers who care enough will post. The crunchers who would volunteer would be the ones who also care enough to post. Your stats will tell you what % that is. Just make a separate forum folder for such discussions.


10) Message boards : News : Constructive suggestions please (Message 1790)
Posted 1 Feb 2016 by Profile Steve Hawker*

I've had a lot of success with CMS-Dev, and some failures. But nothing has failed recently.

Until I tried the vLHC app. I am used to the 24 hour run time but when the app got to 2 days, I figured it was broken.

v46.20 runs on CMS-Dev but not on vLHC, same machine. This is strange, of course.

One swallow doesnt make a summer so inconclusive but maybe 46.20 not yet ready?

My constructive comment is that you need to run many thousands of WUs with zero unmitigated failures before promoting the app to production. Standard risk management/bug crunching.

11) Message boards : News : Poll (Message 1788)
Posted 1 Feb 2016 by Profile Steve Hawker*
As discused in a recent thread, There will potentially be 6 LHC related applications (Six Track, Test4Theory, ALICE, ATLAS, CMS and LHCb) and hence between 1 and 12 projects depending on how things are organised. The options are:
1. One project with beta apps
2. Two projects; prod and dev
3, One project and six dev projects
4. Six prod projects and six dev projects

What would you prefer?


Perhaps you can explain what one project would look like?

SETI has one production project and one dev project. Each supports two distinct application classes but credit is not split into two sub-projects.

Other projects have one production but split into multiple sub-projects.

If you have one production with six sub-projects and one dev with six sub-projects, I think this meets everyone's needs. People who want to set and leave can do so. People who like to adjust based on hours and/or credits can do so.

If you plan to lump all apps together then I'd vote for 6 + 6. If you have sub-projects, then I'd vote for 1 + 1.

Sub-projects with distinctly separate production and development projects is surely the best solution. If you go this route, please be careful with maintaining separations.


12) Message boards : News : Migrating to vLHC@home (Message 1687)
Posted 28 Jan 2016 by Profile Steve Hawker*
The CMS beta application which should be identical to this one is now available in vLHC@home.

Nitpicking possibly but here I can only run one at a time, which I prefer. But at vLHC I get two tasks and then either have to mess about with a config file or manually manage the tasks. Not the same experience as here at dev.

May I also add my voice to those who do not want to migrate to vLHC. SETI, Rosetta and Einstein have their own beta projects where they harden their apps on a smaller audience of committed crunchers. There have been and are other projects that keep their sandboxes separate. Might I urge you to retain this system.

As for whether the app is ready for primetime, I'd say yes but for the continual stream of bug reports. It's always worked for me IIRC but others experience issues. Of course its your decision but it doesn't seem baked enough to me.

Finally, seeing as I've opened my mouth, can I beg you to move away from VBox. It seems to cause more problems than its worth. I don't understand how a collection of brilliant minds at CERN cannot build native apps for the three main platforms. I'd even be OK with a Docker version as that seems to work fine over at Cosmology. I'll continue to crunch because I like to crunch everything, but I know serious crunchers who won't come near this project because it has Vbox.

Thanks for listening

13) Message boards : Number crunching : Multiple Jobs In A Single Host (Message 238)
Posted 9 Apr 2015 by Profile Steve Hawker*
I'm not, but when we get closer to production I'd like to be able to select myself how many to run --

Oh yes, please please please!!!
14) Message boards : News : VBox wrapper problems (Message 121)
Posted 20 Mar 2015 by Profile Steve Hawker*
Although this doesn't address any other macs attached. A better solution is to remove the mac app until you are ready to have people run it again.

I'm only running two Macs but I agree with Z67 that removing the app is the cleaner solution. I only burned through 150 WUs before I saw this.

15) Message boards : Number crunching : Out of work (Message 51)
Posted 11 Mar 2015 by Profile Steve Hawker*
Do you have plans to release more WUs?


16) Message boards : Number crunching : 41.01 on OSX (Message 50)
Posted 9 Mar 2015 by Profile Steve Hawker*
I've been running 41.01 on a couple of MacBooks - so far 50/54 tasks successful.

Three bombed out as error while computing. Two of those were code 5. The other was due to "finish file present too long"

The final failed task was quite odd. It ran overnight for 8 hours very slowly incrementing the % completion and then went into a VM state, "waiting to acquire lock". I've never seen this on any CERN VM and ATLAS has sent me plenty of hanging VM tasks. Often the cure is to suspend, exit BOINC and resume after restarting BOINC - this did not work at all. I suspended every other task and still no lock acquired. So I aborted. Due to the restart(s) the task shows about 22 minutes elapsed instead of the 8+ hours that task was running.

Given the extreme flakiness of the ATLAS VM, 4 fails out of 54 is darned good but zero is, I'm sure, your goal.


17) Message boards : News : New VM image and new console feature! (Message 47)
Posted 6 Mar 2015 by Profile Steve Hawker*
You can open the VM console by clicking on the CMS-dev job in your BOINC Manager and then on the "show VM Console"-button on the left.

On OSX, BOINCmgr 7.2.42, when I click on the task "show VM console" does not appear.

Do I need the latest BOINCmgr?



You do need the VirtualBox Extension Pack installed for the VBox version you are running.

Pretty sure I have that. Not sure how having it would make BOINC display the right button.
18) Message boards : Getting started : Usual BOINC links missing (Message 45)
Posted 6 Mar 2015 by Profile Steve Hawker*
Please ignore. This question was already asked:

19) Message boards : News : New VM image and new console feature! (Message 44)
Posted 6 Mar 2015 by Profile Steve Hawker*
You can open the VM console by clicking on the CMS-dev job in your BOINC Manager and then on the "show VM Console"-button on the left.

On OSX, BOINCmgr 7.2.42, when I click on the task "show VM console" does not appear.

Do I need the latest BOINCmgr?



©2024 CERN