LHC@home

Never run CMS on Linux before so I assume I am doing something wrong, I have tried using both the Boinc Virtualbox app from the software repository and installing Virtualbox direct from the main site, both end in failed tasks, any idea what I am doing wrong?
Example of a failed task https://lhcathome.cern.ch/lhcathome/result.php?resultid=404588324

1st measure:
Reduce your work buffer to 0.01 until your tasks run stable!

You already burned nearly 100 Theory tasks and nearly 100 CMS tasks.
That's not a nice behaviour against the project.


2nd measure:
Use the url tags from the forum editor to mark links!
Wrong:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=404588324

Right:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=404588324


3rd measure:
Read the logfiles - stderr.txt in this case.
An error like this tells you VirtualBox is not running, even if you installed it.

VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

If you are not familiar with VirtualBox:
1. remove it completely!
2. Reboot
3. Install it again
4. Reboot

Buffer is 0.01, its downloading 32 for the CPU erroring out then immediately downloading more before I can stop it.

Ill check the Vbox site for details on how to check its running thanks.

Tried uninstalling, rebooting, reinstalling, rebooting again, no help, still crashing, I'll just stop sending tasks there for now until I find a solution here or on Google.
Might just go back to Windows on this box as its much simpler, just loose out on a few apps.

One thing to make sure of is that you've got virtualisation turned ON for your CPU.

Yea it is enabled

I have to edit the sytstemd for the boinic service and add the following:

/etc/systemd/system/boinc-client.service.d/override.conf

[Service]
ProtectSystem=full

I have this, still no joy

2024-01-23 23:55:20 (91333): Error in guest additions for VM: -1041038848
Is your Guest-Addition for Virtualbox conform with your Virtualbox-Version?

I have the guests iso installed

The additions are in the VM so you don't need to install them.
I assume the error is that they are the wrong version since the VM disk is older.

You have this error

Sudo-Version must be at least 1.9.10.

You have this error
Sudo-Version must be at least 1.9.10.

This is only for cgroups v2, not for v1.

Rosetta @ home is also bringing the following error "Postponed: Communication with VM Hypervisor failed" so I am assuming a config issue somewhere?

Part of the same issue that VirtualBox isn't working I think

You can run Virtualbox as the boinc user to see if there is some stale disks or it even loads

sudo -u boinc VirtualBox

I get the following error:

"Qt WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-boinc'

(VirtualBox:1122138): dbind-WARNING **: 09:50:08.269: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_0: Permission denied"

Any thoughts on this one?

Could be you need to grant permission to boinc it can use the video out:

sudo xhost si:localuser:boinc

No joy, same error

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
2024-02-03 13:03:44 (10112): Detected: vboxwrapper 26206
2024-02-03 13:03:44 (10112): Detected: BOINC client v7.18.1
2024-02-03 13:03:49 (10112): 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-02-03 13:03:49 (10112): Detected: VirtualBox VboxManage Interface (Version: 6.1.48)
2024-02-03 13:03:55 (10112): 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-02-03 13:03:55 (10112): WARNING: Communication with VM Hypervisor failed.
2024-02-03 13:03:55 (10112): ERROR: VBoxManage list hostinfo failed
13:03:55 (10112): called boinc_finish(1)

</stderr_txt>
]]>

I think I am just resigned to not running CMS (or Theory) on this box :(

No joy, same error
.
.
I think I am just resigned to not running CMS (or Theory) on this box :(

You could start with upgrade the VBox version from 6.1.48 to 7.0.14 and more important:
avoid to start several CMS-tasks or Theory/ATLAS-tasks at once, but one after the other.
It looks like you started >10 CMS-tasks concurrently.

Seem to have sorted it, adding an override file didn't seem to work but after some searching here editing this file /etc/systemd/system/multi-user.target.wants/boinc-client.service and changing ProtectSystem=strict to full seems to have fixed it, ill keep an eye on outputs.