LHC@home

Every ATLAS vbox task ends in 12 seconds with "output file [...] for task [...] absent." I can see the virtualbox task running in system monitor - it just stops quickly. I know Virtualbox works because I can create my own VMs. I installed Virtualbox using the boinc-virtualbox package. This is a fresh install of Ubuntu 23.10 and I'm using an AMD Ryzen 5 3600 CPU. I'm running LHC@home through my Science United account. Any ideas for troubleshooting?

Welcome,
do you have CVMFS installed correct?

No, I do not. I will look into that. Is CVMFS just required for ATLAS or for all LHC@home tasks?

I just installed cvmfs according to the debian/ubuntu instructions here (https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html), but I'm still getting the same error. I didn't do any of the "setup" steps because I wasn't sure if they were applicable to LHC@home.

Is anything else required? Are there any good guides that describe how to get this up and running?

A local CVMFS installation is not required if you run VirtualBox apps.

Instead make your computer visible for other volunteers in your project prefs and post a link to it.
If this is not possible because it is attached via Science United disable that first and attach the computer directly.

I checked the box next to "Should LHC@home show your computers on its web site?" and clicked the update button in BOINC but I think it might still be hidden. My profile is here https://lhcathome.cern.ch/lhcathome/show_user.php?userid=934692

I'm not sure exactly what you need, but I pasted a few screenshots here in case it's still showing up as hidden https://drive.proton.me/urls/DCMXPR3Z6W#mQHS2Fhw5arG

I checked the box next to "Should LHC@home show your computers on its web site?"

OK.

I'm not sure exactly what you need

Your computer(s) are still shown as hidden.
If you attached the computer in question via an account manager like Science United disconnect it from the account manager and connect it directly to this project and run a task.
Then your computer(s) will be visible as links under your account.
That's what I ask for before I continue.

Looks like most of the error messages give a similar output:

<core_client_version>7.20.5</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2024-03-07 14:42:45 (85674): Detected: vboxwrapper 26206
2024-03-07 14:42:45 (85674): Detected: BOINC client v7.20.5
2024-03-07 14:42:51 (85674): Error in guest additions for VM: -1041038848
Command:
VBoxManage -q list systemproperties
Output:
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

2024-03-07 14:42:51 (85674): Detected: VirtualBox VboxManage Interface (Version: 7.0.14)
2024-03-07 14:42:56 (85674): Error in host info for VM: -1041038848
Command:
VBoxManage -q list hostinfo 
Output:
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_SOCKET_FAIL (0xC1F30200) - IPC daemon socket error (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

2024-03-07 14:42:56 (85674): WARNING: Communication with VM Hypervisor failed.
2024-03-07 14:42:56 (85674): ERROR: VBoxManage list hostinfo failed
14:42:56 (85674): called boinc_finish(1)

</stderr_txt>
]]>

looks like it's un-hidden now! Can you see it?

https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10847319

From your logs:
Most likely, the VirtualBox COM server is not running or failed to start.
This is a problem with VirtualBox, not a problem caused by this project.

looks like it's working now!

As of a sudden?
Other volunteers having the same problem may be interested how you solved it.
Could you post what you did?

Sorry that was misleading - I only meant that my computer was now visible under my profile. I'm still getting the same errors while computing.

If I'm able to successfully create and run a virtualbox VM separate from BOINC, doesn't that mean that virtualbox is not the issue?

Is the user account running BOINC a member of the group "vboxusers"?


If yes, check the steps below.


Check you BOINC's systemd unit file for this entry:
ProtectSystem=strict


If this is set, it is too strict.

Do this:
1. stop BOINC
2. create an override file "/etc/systemd/system/boinc-client.service.d/override.conf" containing the following 2 lines:
[Service]
ProtectSystem=full
3. run "sudo systemctl daemon-reload"
4. start BOINC and try the next VirtualBox task



If this doesn't succeed, post your complete boinc-client.service file.

I think that did the trick! It's been running for a few minutes now. Thank you so much. I will keep an eye on it to see if it finishes successfully.