What is LHCathome-dev?

This is a BOINC server for LHC@home development. Please note that some of the applications on LHC@home requre Virtual Box to be installed. Please visit the LHC@home information site for more information. If you have any problems or questions please visit the Message Boards, Questions and Answers and FAQ.

Join LHCathome-dev

User of the Day

User profile Profile Steve Hawker*
I've been crunching since 2012 and the more I do, the more I like it. I try to crunch every project I can find. I don't have a server farm or a...

News

Using a local proxy to reduce network traffic for CMS
Thanks to computezrmle, with additional work from Laurence and a couple of CMS experts (and my adding one line to the site-local-config file) there is now a way to set up a local caching proxy to greatly reduce your network traffic. Each job instance that runs within s CMS BOINC task must retrieve a lot of set-up data from our database. This data doesn't change very often, so if you keep a local copy the job can access that rather than going over the network every time.
Instructions on how to do this are available at https://lhcathomedev.cern.ch/lhcathome-dev/forum_thread.phpp?id=475&postid=6396 or https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5052&postid=39072
7 Jun 2019, 14:22:51 UTC · Discuss


CMS -- Please set "no new tasks"
Hi to all CMS-ers. We need to drain the job queue so that a new version of the WMAgent can be installed.
Can you please set No New Tasks so that your current tasks can run out and no new jobs start? If you have any tasks waiting to run, please suspend or abort them.
Thanks, I'll let you know as soon as the change is done.
14 May 2019, 14:59:27 UTC · Discuss


Problem writing CMS job results; please avoid CMS tasks until we find the reason
Since some time last night CMS jobs appear to have problems writing results to CERN storage (DataBridge). It's not affecting BOINC tasks as far as I can see, they keep running and credit is given. However, Dashboard does see the jobs as failing, hence the large red areas on the job plots.
Until we find out where the problem lies, it's best to set No New Tasks or otherwise avoid CMS jobs. I'll let you know when things are back to normal again.
18 Apr 2019, 15:46:05 UTC · Discuss


CMS jobs
The batch I submitted last night is now showing on the monitor, so you can resume tasks at will.
23 Mar 2019, 17:55:46 UTC · Discuss


Warning: possible shortage of CMS jobs - set No New Tasks as a precaution
There was an intervention (i.e. upgrade) yesterday afternoon[1] on the cmsweb-testbed system we use to submit CMS workflows that left things a bit confused. One problem was fixed, and the monitor shows all good. However, we are running out of CMS jobs -- maybe 10 hours left -- but the new batch I submitted yesterday isn't showing up on the testbed monitor. I submitted another last night but still neither are being shown this morning, so I submitted yet another batch.
At the moment I don't know whether the submission has failed or whether the monitor hasn't picked up the new batches. As a precaution, set No New Tasks on your CMS project(s) to avoid tasks crashing due to lack of jobs. I'll let you know as soon as I'm sure jobs are available again.

[1] How many times do I have to tell people not to touch critical systems on a Friday -- especially Friday afternoon!?
23 Mar 2019, 11:32:45 UTC · Discuss


... more

News is available as an RSS feed   RSS


©2019 CERN