Development for LHC@home

This new version provides a new image along with an updated version of the vboxwrapper (v26205). The cvmfs reload and proxy setting functions have been temporarily disabled. This will be revised in a future update.

1.57GB
I guess I will d/l one here since this is my isp high-speed at 2am and I rather not use it all up doing this so I will do the rest during the day where I already used up all my high-speed in 4 days

In this version ALT-F# key strokes, except ALT-F3 (top), don't display what it was in the previous version.
ALT-F2: Running job output should appear here
ALT-F4: Output of the job wrapper may appear here.
ALT-F5: Error messages may appear here.

BOINC's Show graphics displays a webpage with: Scientific Linux Test Page ..... and not the log files.

My first task crashed after 20 minutes because of: VM Heartbeat file specified, but missing

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3102023


No heartbeat file in the shared folder

VM Heartbeat file specified, but missing.
VM Heartbeat file specified, but missing file system status. (errno = '2')

{This machine does not have any snapshots}, preserve=false aResultDetail=0
(well glad I only did the d/l once)......goodnight

BOINC's Show graphics displays a webpage with: Scientific Linux Test Page ..... and not the log files.

+1

BOINC's Show graphics displays a webpage with: Scientific Linux Test Page ..... and not the log files.

+1

Same here

Thanks for testing. The fix for the heartbeat issue should be live in a few minutes. There are a number of things that need to be fixed before this version is ready. The main thing we are testing is an updated connection method to the CMS job pool and the vboxwrapper.

Thanks for testing. The fix for the heartbeat issue should be live in a few minutes. There are a number of things that need to be fixed before this version is ready. The main thing we are testing is an updated connection method to the CMS job pool and the vboxwrapper.

Confirmed. Heartbeat once a minute. Cool!

Process 'cmsRun' running fine.

Differencing disk 'only' 241 MB so far after 44 minutes runtime.
In the past the whole 4GB vdi was copied into the slot-folder for every CMS-task.

Task seems to be running fine on my Windows 10 box. I also see the Apache home page rather than logs in "Show graphics". In the console window, Ctrl-Alt-F1 brings up the console output, Ctrl-Alt-F3 brings up the "top" output and Ctrl-Alt-F6 shows the console login page. With F2, F4 and F5 I just get the dummy messages that job output/job wrapper/error messages may appear, but they don't.

---

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3102051
This task does not shut down correctly.

During normal operation "cmsRun" was the leading process in the top output and in BOINC CPU-time was always a bit ahead of runtime (since it is a 2-core VM).

Now "cmsRun" is not shown any more and the VM is idle (don't know since when).
Top shows load averages close to 0.
Runtime is continuously increasing (currently 16:43:10) but CPU-time is sitting at 13:57:12.

Will let it run until the hard runtime limit to see whether this will end the task.

Seeing the same.
6 hours idle and 17:30 hours runtime.

The same here. VM-lifetime > 13 hours.
I suppose it's the same as the missing heartbeat file.

computezrmle will wait until the shutdown is done by vboxwrapper. I'm sure it will.

I'll help the task a bit.

As foreseen by CP the vboxwrapper watchdog correctly shut down the task.
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3102051

Thanks for the information. I think I know what the problems are. Will try to fix them.

I made a couple of changes. Let's see if that improves things.

This the first one I ran yesterday https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3102096
Run time 18 hours 1 min 6 sec
CPU time 4 hours 18 min 13 sec

I just started a new one on that host and today got the vdi and wrapper on another so just started that one too.
I will add the other host tomorrow and then the 4th on the next day since I rather not use up all of my 2am fast speed
You are all lucky you are not stuck using Hughes satellite isp because loading the new vdi and wrapper I started at 5:30pm and ran until 2am and only had 51% of the d/l but at 2am when I get full speed again it finished the rest in 5 minutes.
So tomorrow I will start the next d/l at around noon but I imagine my late night "bonus" high speed I get will soon be gone which means it will be hard to even get 4 hosts running a single task when I run out of what ever I have left and right now the Hughes website page will not even load so I can see what I have left and my new month doesn't start until Aug. 13th at midnight

A (correctly configured) local proxy ensures you would have to download the vdi just once independent of the #computers in your LAN using it.

Has anyone else run into a problem with the vboxwrapper under Linux? I get the message:

../../projects/lhcathomedev.cern.ch_lhcathome-dev/vboxwrapper_26205_x86_64-pc-linux-gnu: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ../../projects/lhcathomedev.cern.ch_lhcathome-dev/vboxwrapper_26205_x86_64-pc-linux-gnu)

It seems vboxwrapper_26205_x86_64-pc-linux-gnu was built on a system with glibc 2.29 but I'm using Rocky Linux 8.6 (derived from RHEL 8) which still uses 2.28.
It's not immediately obvious to me how to build my own version of vboxwrapper (it seems you have to build the whole BOINC tree, but that always trips up over the wx-widgets version unless you are lucky). I tried copying the V26204 wrapper to my directory tree and renaming that to V26205, but have yet to find out if that works as BOINC won't serve me new tasks since I had so many failures last night before I realised something was wrong.

---

Vboxwrapper 26205 has been compiled on the official Github platform including the lib versions they use there.
Best would be to upgrade your system libs.


If you compile it yourself you may switch off generating vboxmanager since only this component uses wx-widgets.
It's also the component that requires most of the compilation time.


Suggested steps to configure/compile the BOINC client (including required helpers) and vboxwrapper:

1. cd to the base directory of your sourcecode
2. run "make distclean"
3. run ./configure with the options "--disable-server --disable-manager --enable-apps-vbox --enable-optimize"
4. run make
5. cd to <base directory>/samples/vboxwrapper
6. run make
7. run "strip vboxwrapper"



This is just a workaround.
Be aware that under certain circumstances the BOINC client requests a fresh copy from the project server.