1) Message boards : Number crunching : VirtualBox .. , , 6.1.36 , , .. (released July 19 2022) (Message 47161)
Posted 18 Aug 2022 by rjs5
Post:
I suspect there were suspended tasks during the update and VirtualBox stumbled over a snapshot.

This needs to be cleaned manually.

1. set BOINC to "no new tasks"
2. pause all vbox tasks that are not yet started
3. cancel all ATLAS tasks that are already started (they will not recover)
4. shut down BOINC
5. Check from the vbox GUI "Media Manager" if there are broken disk entries; remove them (but not the vdi file if you are asked about it!)
6. Restart BOINC (should work again)


Thanks to you and Crystal Pellet. It is great to have good volunteer support!!!

The only place I got stuck for a moment was deleting the VDI. I didn't notice the ">" on the left which indicated there was something (a disk) attached. I deleted it, the image and LHC is working again.
2) Message boards : Number crunching : VirtualBox .. , , 6.1.36 , , .. (released July 19 2022) (Message 47156)
Posted 18 Aug 2022 by rjs5
Post:
I upgraded my Windows 11 machine ( 10802580 ) to virtualbox 6.1.36 and I am seeing Atlas errors.
I have EXCLUDED the Boinc Data directory from antivirus scans.
Do you know what i am doing wrong?
Should I uninstall and install 6.1.34 again?
thanks


Stderr output

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code 2159738892 (0x80bb000c)</message>
<stderr_txt>
2022-08-17 23:00:57 (16204): Detected: vboxwrapper 26205
2022-08-17 23:00:57 (16204): Detected: BOINC client v7.20.2
2022-08-17 23:00:58 (16204): Detected: VirtualBox VboxManage Interface (Version: 6.1.36)
2022-08-17 23:00:58 (16204): Successfully copied 'init_data.xml' to the shared directory.
2022-08-17 23:00:59 (16204): Create VM. (boinc_42486e46406184d0, slot#23)
2022-08-17 23:00:59 (16204): Setting Memory Size for VM. (6600MB)
2022-08-17 23:01:00 (16204): Setting CPU Count for VM. (4)
2022-08-17 23:01:00 (16204): Setting Chipset Options for VM.
2022-08-17 23:01:00 (16204): Setting Graphics Controller Options for VM.
2022-08-17 23:01:00 (16204): Setting Boot Options for VM.
2022-08-17 23:01:01 (16204): Setting Network Configuration for NAT.
2022-08-17 23:01:01 (16204): Enabling VM Network Access.
2022-08-17 23:01:01 (16204): Disabling USB Support for VM.
2022-08-17 23:01:02 (16204): Disabling COM Port Support for VM.
2022-08-17 23:01:02 (16204): Disabling LPT Port Support for VM.
2022-08-17 23:01:02 (16204): Disabling Audio Support for VM.
2022-08-17 23:01:02 (16204): Disabling Clipboard Support for VM.
2022-08-17 23:01:03 (16204): Disabling Drag and Drop Support for VM.
2022-08-17 23:01:03 (16204): Adding storage controller(s) to VM.
2022-08-17 23:01:03 (16204): Adding virtual disk drive to VM. (ATLAS_vbox_2.02_image.vdi)
2022-08-17 23:01:10 (16204): Error in deregister parent vdi for VM: -2135228404
Command:
VBoxManage -q closemedium "E:\BOINC/projects/lhcathome.cern.ch_lhcathome/ATLAS_vbox_2.02_image.vdi"
Output:
VBoxManage.exe: error: Cannot close medium 'E:\BOINC\projects\lhcathome.cern.ch_lhcathome\ATLAS_vbox_2.02_image.vdi' because it has 1 child media
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "Close()" at line 1736 of file VBoxManageDisk.cpp

2022-08-17 23:01:10 (16204): Could not create VM
2022-08-17 23:01:10 (16204): ERROR: VM failed to start
2022-08-17 23:01:10 (16204): Powering off VM.
2022-08-17 23:01:10 (16204): Deregistering VM. (boinc_42486e46406184d0, slot#23)
2022-08-17 23:01:10 (16204): Removing network bandwidth throttle group from VM.
2022-08-17 23:01:11 (16204): Removing VM from VirtualBox.
3) Questions and Answers : Unix/Linux : failed to create /var/lib/condor directory (Message 46809)
Posted 20 May 2022 by rjs5
Post:
I fixed it by installing a local version of singularity. Running the local version was my key to successfully completing the native tasks.
4) Questions and Answers : Unix/Linux : failed to create /var/lib/condor directory (Message 46808)
Posted 20 May 2022 by rjs5
Post:
I am seeing a failure running all native MT Atlas jobs on my Fedora Linux system. I have not yet got this machine to run the native jobs. Anyone know what I am doing wrong? I followed the instructions in setting up the cvmfs and the probe and repos seem OK.

Thanks

[2022-05-20 12:01:28] Set ATHENA_PROC_NUMBER=8
[2022-05-20 12:01:28] Starting ATLAS job with PandaID=5458895246
[2022-05-20 12:01:28] Running command: /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/current/bin/singularity exec --pwd /var/lib/boinc/slots/23 -B /cvmfs,/var /cvmfs/atlas.cern.ch/repo/containers/fs/singularity/x86_64-centos7 sh start_atlas.sh
[2022-05-20 12:01:29] Job failed
[2022-05-20 12:01:29] FATAL: container creation failed: hook function for tag prelayer returns error: failed to create /var/lib/condor directory: mkdir /var/lib/condor: read-only file system
[2022-05-20 12:01:29] ./runtime_log



©2025 CERN