Message boards :
ATLAS application :
atlas error
Message board moderation
Previous · 1 · 2 · 3 · 4
| Author | Message |
|---|---|
|
Send message Joined: 27 Apr 24 Posts: 21 Credit: 1,255,181 RAC: 872 |
My Atlas native work unit won't start up properly. In the stderr.txt, it gets as far as this, then after that it gets stuck, and nothing else happens: [2025-10-01 14:50:25] Using apptainer image /cvmfs/atlas.cern.ch/repo/containers/fs/singularity/x86_64-centos7 [2025-10-01 14:50:25] Checking for apptainer binary... [2025-10-01 14:50:25] Using apptainer found in PATH at /usr/bin/apptainer [2025-10-01 14:50:25] Running /usr/bin/apptainer --version [2025-10-01 14:50:25] apptainer version 1.4.3 [2025-10-01 14:50:25] Checking apptainer works with /usr/bin/apptainer exec -B /cvmfs /cvmfs/atlas.cern.ch/repo/containers/fs/singularity/x86_64-centos7 hostname |
|
Send message Joined: 26 Nov 16 Posts: 14 Credit: 215,138 RAC: 173 |
I'm also having problems with Atlas on Linux error out fairly soon after starting. https://lhcathome.cern.ch/lhcathome/result.php?resultid=427558480 Stderr output <core_client_version>8.0.4</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61)</message> <stderr_txt> 16:58:40 (28883): wrapper (7.7.26015): starting 16:58:40 (28883): wrapper: running run_atlas (--nthreads 2) awk: line 2: function strftime never defined 17:08:40 (28883): run_atlas exited; CPU time 0.008072 17:08:40 (28883): app exit status: 0x1 17:08:40 (28883): called boinc_finish(195) </stderr_txt> ]]> |
|
Send message Joined: 15 Jun 08 Posts: 2712 Credit: 293,027,798 RAC: 149,272 |
Your computer reports 3.79 GB RAM: https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10846970 This is enough to run XTrack. ATLAS/CMS/Theory recommend at least 16 GB although they may run with at least 8 GB. |
|
Send message Joined: 5 May 10 Posts: 10 Credit: 8,141,676 RAC: 59,990 |
Since CMS is still broken I thought I'd run ATLAS for a while. However, it appears to be complaining about a "VMMR0.r0" file not being able to load. I've reset the project and reinstalled virtualbox and still get this error. Not sure why it isn't working now since I've run ATLAS just fine before. The last task was started with virtualbox open and the VM showed up in the list of VMs but stayed powered off until disappearing from the list a couple seconds later. My only other VM is for Win98. There are no anomalies in the media manager. I definitely have enough RAM btw. <core_client_version>8.2.4</core_client_version> <![CDATA[ <message> Unspecified error (0x80004005) - exit code 2147500037 (0x80004005)</message> <stderr_txt> 2025-10-23 23:13:10 (2148): vboxwrapper version 26210 2025-10-23 23:13:10 (2148): BOINC client version: 8.2.4 2025-10-23 23:13:10 (2148): Detected: VirtualBox VboxManage Interface (Version: 7.2.4) 2025-10-23 23:13:10 (2148): Successfully copied 'init_data.xml' to the shared directory. 2025-10-23 23:13:11 (2148): Create VM. (boinc_d9feed172f2ad16e, slot#0) 2025-10-23 23:13:11 (2148): Setting Memory Size for VM. (4600MB) 2025-10-23 23:13:11 (2148): Setting CPU Count for VM. (6) 2025-10-23 23:13:12 (2148): Setting Chipset Options for VM. 2025-10-23 23:13:12 (2148): Setting Graphics Controller Options for VM. (Driver: VBoxVGA, 16MB) 2025-10-23 23:13:12 (2148): Setting Boot Options for VM. 2025-10-23 23:13:13 (2148): Setting Network Configuration for NAT. (Driver: virtio) 2025-10-23 23:13:13 (2148): Enabling VM Network Access. 2025-10-23 23:13:13 (2148): Disabling USB Support for VM. 2025-10-23 23:13:14 (2148): Disabling COM Port Support for VM. 2025-10-23 23:13:14 (2148): Disabling LPT Port Support for VM. 2025-10-23 23:13:14 (2148): Disabling Audio Support for VM. 2025-10-23 23:13:14 (2148): Disabling Clipboard Support for VM. 2025-10-23 23:13:15 (2148): Disabling Drag and Drop Support for VM. 2025-10-23 23:13:15 (2148): Adding storage controller(s) to VM. 2025-10-23 23:13:15 (2148): Adding virtual disk drive to VM. (ATLAS_vbox_3.03_image.vdi) 2025-10-23 23:13:17 (2148): Adding VirtualBox Guest Additions to VM. 2025-10-23 23:13:17 (2148): Adding network bandwidth throttle group to VM. (Defaulting to 1024GB) 2025-10-23 23:13:18 (2148): forwarding host port 57917 to guest port 80 2025-10-23 23:13:18 (2148): Enabling remote desktop for VM. 2025-10-23 23:13:19 (2148): Enabling shared directory for VM. 2025-10-23 23:13:19 (2148): Starting VM using VBoxManage interface. (boinc_d9feed172f2ad16e, slot#0) 2025-10-23 23:13:22 (2148): Error in start VM for VM: -2147467259 Command: VBoxManage -q startvm "boinc_d9feed172f2ad16e" --type headless Output: VBoxManage.exe: error: Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND). VBoxManage.exe: error: Failed to load VMMR0.r0 (VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole Waiting for VM "boinc_d9feed172f2ad16e" to power on... 2025-10-23 23:13:22 (2148): VM failed to start. 2025-10-23 23:13:22 (2148): Could not start 2025-10-23 23:13:22 (2148): ERROR: VM failed to start 2025-10-23 23:13:22 (2148): Powering off VM. 2025-10-23 23:13:22 (2148): Deregistering VM. (boinc_d9feed172f2ad16e, slot#0) 2025-10-23 23:13:22 (2148): Removing network bandwidth throttle group from VM. 2025-10-23 23:13:22 (2148): Removing VM from VirtualBox. |
|
Send message Joined: 15 Jun 08 Posts: 2712 Credit: 293,027,798 RAC: 149,272 |
Looks like a broken VirtualBox installation (SUP_IOCTL_LDR_OPEN). See: https://forums.virtualbox.org/viewtopic.php?t=104378 You may need to repair your VirtualBox. If the error still persists consider to send a bug report to VirtualBox. |
|
Send message Joined: 5 May 10 Posts: 10 Credit: 8,141,676 RAC: 59,990 |
After reinstalling virtualbox as administrator it didn't fix the issue. Looking further down on that thread they mentioned the bugged core isolation feature. Core isolation is shown as being off so I turned it on (rebooted) then back off (rebooted) and it's working now. It must of been turned back on with the win11 25h2 update. They still haven't fixed the bugged setting... but I shouldn't expect too much from microsoft. |
|
Send message Joined: 13 May 15 Posts: 1 Credit: 146,849 RAC: 488 |
Anyone using Windows 11 should consider virtualization. https://learn.microsoft.com/en-us/answers/questions/2186657/help-with-hyper-v-disabling-and-vt-x-enabling-for?forum=windowsclient-all&referrer=answers Generally, we all should check our computers to see if they're still delivering anything. Regardless of which operating system is installed. For example, this computer with Linux has already failed almost 2,000 WUs. https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10858958 User is TRIUMF-LCG2. And if I see it correctly, he has around 70 computers, and I'm afraid they all have the same problem. https://lhcathome.cern.ch/lhcathome/hosts_user.php?userid=567711 |
©2025 CERN