Development for LHC@home

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.

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.

By the way, FNAL means Fermi National Accelerator Lab which is near Chicago USA.

My host still gets v47.30 vbox64_mt_mcore_cms as described here.

See: https://lhcathome.cern.ch/vLHCathome-dev/result.php?resultid=274756

Batavia, Illinois

http://www.fnal.gov/

My host still gets v47.30 vbox64_mt_mcore_cms as described here.

I got CMS Simulation v47.40 (vbox64_mt_mcore) windows_x86_64

However application 47.60 (vbox64_mt_mcore_cms) is available.

Although the application table shows only v47.60 (vbox64_mt_mcore_cms) I still get v47.30.

You will probably notice when you get the new v47.60 vbox64_mt_mcore_cms since you will have to download the 640.23MB .vdi

---

Mad Scientist For Life

All failing on my Mac with "206 (0x000000CE) EXIT_INIT_FAILURE" error.

Example.

All failing on my Mac with "206 (0x000000CE) EXIT_INIT_FAILURE" error.

Example.

It looks like we have Condor problems here just like over at vLHC

I just got one of those [ERROR] Could not ping HTCondor when I tried to run one on this pc and next few minutes it was gone and now I see it was done by the server because I had the previous version that I got yesterday......so now I am going to wait a while for that .vdi to d/l

In your case you do have the new version and it is not making contact so I guess they need to go feed that Condor again.

---

Mad Scientist For Life

All failing on my Mac with "206 (0x000000CE) EXIT_INIT_FAILURE" error.

Example.

It looks like we have Condor problems here just like over at vLHC

I just got one of those [ERROR] Could not ping HTCondor when I tried to run one on this pc and next few minutes it was gone and now I see it was done by the server because I had the previous version that I got yesterday......so now I am going to wait a while for that .vdi to d/l

In your case you do have the new version and it is not making contact so I guess they need to go feed that Condor again.

No, RAL has shut down our servers over the "Dirty COW" Linux kernel bug. Apparently the mitigation suggested by Red Hat is not sufficient for the level of paranoia the RAL sysadmins have developed, so we wait for a proper kernel patch to be released. Keep watching the News, I'll let you know as soon as I hear the servers have been restarted. (Our nominal chap in control of our servers is on holidays ATM, but heard the news and let us know; the more central bods who made the decision may not even know we exist).

---

Thanks for the info.

When I'm grown up maybe I'll know what's RAL, ATM holidays and a dirty cow :)

When I'm grown up maybe I'll know what's RAL, ATM holidays and a dirty cow :)

Let's help to grow you a bit:
RAL --> Rutherford Appleton Laboratory
ATM --> At The Moment
dirty cow --> Explaining Dirty COW

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

Thanks for the nice video, ATM I probably only understood a portion of it, but that was nice ;)

So the "good news" is that the issue has nothing to do with the application itself nor my machine, so that's good enough for me !

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

...

The vLHC BOINC servers are at CERN but the Condor servers which supply jobs can be elsewhere. In this case, CMS jobs are being sent from RAL where Ivan is partly based.

Thu 27 Oct 2016 08:05:20 PM CEST | vLHCathome-dev | [cpu_sched_debug] enforce: result CMS_23154_1477523974.478450_0 can't run, too big 3000.00MB > 1871.86MB

I used to be able to run 4 tasks. Where does it get the 3000MB figure from?
The official memory requirment in the CMSXXX.xml file is 2048:

(Boinc 7.6.33)

EDIT:Boinc says,about 6000MB of swap is used, which i do not have(I have NO swap file at all)and set the swap setting in boinc to minimum (1%).

Any suggestions?

After I switched back to the non-HTTPS master URL I got a CMS task from version v47.60 (vbox64_mt_mcore_cms).

Settings:
no app_config.xml
Max # CPUs -> 3 (prefs on the website)


Result from stderr.txt:
2016-10-28 09:53:54 (26625): Setting Memory Size for VM. (3000MB)
2016-10-28 09:53:54 (26625): Setting CPU Count for VM. (1)


Shall I cancel the WU?

All tasks fail on this host except Benchmarks.
Tullio

All tasks fail on this host except Benchmarks.
Tullio

I tested only CMS.
Regarding that app you got an outdated version v47.40.

If your host is attached via the new HTTPS master URL you may detach and reattach via the old URL http://lhcathomedev.cern.ch/vLHCathome-dev/

Then check if you get the most recent CMS version v47.60 (vbox64_mt_mcore_cms).

Settings for cpus per task in the account preferences are being ignored.
It just uses 1 core.

Overriding with app_config.xml works.

VM did not restore from saved snapshot after resume, but booted http://lhcathomedev.cern.ch/vLHCathome-dev/result.php?resultid=280024

Next task with settings 2 cores creates a single core VM with 3000MB RAM.