Development for LHC@home

So, is the CMS-project now completly dead?(dev and production)

BOINC's feeder is not running: https://lhcathome.cern.ch/vLHCathome-dev/server_status.php

At least when using the new secure project URL.

My hosts got a couple of WUs from the non-dev project although it was clear they would run into an error.
Why can´t you stop sending out WUs until the patches are installed?

The VMs are also linux machines.
If they use a COW filesystem they are also affected by that bug.
I´m sure I am the very first thinking about that :-))

The patch for this bug was issued yesterday and will be applied automagically when your current task expires and your CernVM reboots.

As I stated a couple of times in this message board my hosts still do not get the most recent application versions (CMS, CMS-dev).
The older apps download/boot older VM images, e.g. CMS_2016_08_08.vdi in case of CMS-dev, which are not patched.

Resetting the projects or rebooting the hosts do not solve the problem.

Do you mean vLHC is hosted by an "external" laboratory ? I would have thought this was "inside" LHC infrastructure, somehow...

...

My hosts got a couple of WUs from the non-dev project although it was clear they would run into an error.
Why can´t you stop sending out WUs until the patches are installed?

The VMs are also linux machines.
If they use a COW filesystem they are also affected by that bug.
I´m sure I am the very first thinking about that :-))

This new version enables Web proxy auto discovery (wpad) which means the CVMFS traffic should be directed to either CERN for FNAL depending on where you are.

At least without app_config and no tasks, an empty cache and asking 0 days of work, I got 8 tasks for my 8 threaded (4 core HT) machine.
1 task started, created a VM with 8 processors, running 8 jobs with far too low memory. At least the swap is now used ;)

- the new project preference options set to 1 task max, 3 CPUs max

Is this setting only for (ex-)CERN-employees??

I only see a new "Limit the number of tasks per host?" with a tick-box

I got at least 3 tasks with this option set to yes.

Is there ANY way, i could run 3 jobs with 4 cores?

The load average running 4 jobs is about 7.
That means, that there is much more work per job, than a single core can process.
Before the multi-core version, i could do it, now i can only use 1 core per job, which is substantially overloaded and therefore slow.

If the aim of game is, to run as fast as possible,this should be implemented.
Alternatively, there could be 2 versions.
One as is and the other as it was before (through plan classes).

EDIT: Theory jobs

Thanks, Rom.
How is determined now, how many cores to be used?
By the project preference file? What if it is undefined?

...

I have a case, where i am running a 4 core tasks. For whatever reason, it decided after 3h or so, to discontinue 3 of them and runs only on one.
( as if it had hit the 12h mark, which it has not.)

Since about 5.44UTC there seem to be no jobs available.

BTW. Boinc-tasks should not error out, if no work is available.

EDIT:And this message shows at thr top of stderr.

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
Der Ring 2-Stapel wird bereits verwendet.
(0xcf) - exit code 207 (0xcf)
</message>

As before, now task a running , maybe 1 job and starting a new task.

ARE WE OUT OF JOBS?

Thanks for the detailed reply to my first question.

Rom just released vboxwrapper 26186 at the weekend to support VirtualBox 5.1 on Windows. The Theory app was updated so that the release on Monday would go with that version but the CMS app wasn't updated. It has been done now so please try again.

Does this apply as well to the production work at vLHC?