|
1)
Message boards :
ATLAS Application :
ATLAS v0.50 and 0.51
(Message 5303)
Posted 23 Dec 2017 by  Dingo
Post:
I installed the two applications but still get the same error. I stopped and started boinc after the install. https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=373956 The system is Linux CentOS Linux 7 (Core) [3.10.0-693.11.1.el7.x86_64] and this shows that the software is loaded: [root@dingo4 ~]# yum info cvmfs Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.gbeservers.com * extras: mirror.steadfast.net * updates: mirror.dal10.us.leaseweb.net Available Packages Name : cvmfs Arch : x86_64 Version : 2.4.4 Release : 1.el7.centos Size : 8.8 M Repo : cernvm/7/x86_64 Summary : CernVM File System License : BSD Description : HTTP File System for Distributing Software to CernVM. : See http://cernvm.cern.ch : Copyright (c) CERN ---------------------------------------------------------------- yum could not find singularity as it wasn't installed with yum. But it is on the system: [root@dingo4 ~]# find / -name singularity /root/singularity /root/singularity/bin/singularity /root/singularity/etc/bash_completion.d/singularity /usr/local/bin/singularity /usr/local/etc/bash_completion.d/singularity /usr/local/etc/singularity /usr/local/include/singularity /usr/local/lib/singularity /usr/local/libexec/singularity /usr/local/var/singularity I cannot seem to run this any help appreciated. |
|
2)
Message boards :
ATLAS Application :
ATLAS v0.50 and 0.51
(Message 5292)
Posted 22 Dec 2017 by Dingo
Post: All my Atlas work failed on this machine. https://lhcathomedev.cern.ch/lhcathome-dev/show_host_detail.php?hostid=2290 This is an example: Name DyAMDm4oKmrnOmbckoZBDNAoABFKDmABFKDm4NGKDmABFKDmPLzY5n_0 Workunit 360631 Created 21 Dec 2017, 18:32:56 UTC Sent 22 Dec 2017, 0:49:58 UTC Report deadline 29 Dec 2017, 0:49:58 UTC Received 22 Dec 2017, 3:50:17 UTC Server state Over Outcome Computation error Client state Compute error Exit status 195 (0x000000C3) EXIT_CHILD_FAILED Computer ID 2290 Run time 10 min 4 sec CPU time Validate state Invalid Credit 0.00 Device peak FLOPS 39.97 GFLOPS Application version ATLAS Simulation v0.50 (native_mt) x86_64-pc-linux-gnu Peak working set size 6.91 MB Peak swap size 170.48 MB Peak disk usage 253.28 MB Stderr output <core_client_version>7.7.0</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61)</message> <stderr_txt> 20:11:16 (22315): wrapper (7.7.26015): starting 20:11:16 (22315): wrapper: running run_atlas (--nthreads 12) sys.argv = ['run_atlas', '--nthreads', '12'] THREADS=12 Checking for CVMFS sh: cvmfs_config: command not found sh: cvmfs_config: command not found sh: cvmfs_config: command not found check cvmfs return values are 32512, 32512 CVMFS not found, aborting running start_atlas return value is 1 tar czvf shared/result.tar.gz tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. *****************The last 100 lines of the pilot log****************** tail: cannot open ‘pilotlog.txt’ for reading: No such file or directory ***************diag file************ cat: *.diag: No such file or directory ******************************WorkDir*********************** total 36 drwxrwx--x 3 root root 177 Dec 21 20:11 . drwxrwx--x 31 root root 286 Dec 14 19:37 .. -rw-r--r-- 1 root root 0 Dec 21 20:11 boinc_lockfile -rw-r--r-- 1 root root 8192 Dec 21 20:11 boinc_mmap_file -rw-r--r-- 1 root root 5920 Dec 21 20:11 init_data.xml -rw-r--r-- 1 root root 112 Dec 21 20:11 job.xml -rwxr-xr-x 1 root root 7456 Dec 21 20:11 run_atlas drwxrwx--x 2 root root 86 Dec 21 20:11 shared -rw-r--r-- 1 root root 760 Dec 21 20:11 stderr.txt -rw-r--r-- 1 root root 107 Dec 21 20:11 wrapper_26015_x86_64-pc-linux-gnuparent process exit 1 child process exit 1 20:21:19 (22315): run_atlas exited; CPU time 0.034227 20:21:19 (22315): app exit status: 0x1 20:21:19 (22315): called boinc_finish(195) </stderr_txt> ]]>[/url] |
|
3)
Message boards :
LHCb Application :
New version v1.02
(Message 5291)
Posted 22 Dec 2017 by Dingo
Post: I have run threee of theese and they all end in error code 5. This is an example LHCb Simulation v1.02 (vbox64_mt_mcore) x86_64-pc-linux-gnu
Name LHCb_25826_1513818422.243445_0
Workunit 360294
Created 21 Dec 2017, 1:07:05 UTC
Sent 21 Dec 2017, 12:33:30 UTC
Report deadline 28 Dec 2017, 12:33:30 UTC
Received 21 Dec 2017, 12:57:06 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 5 (0x00000005) Unknown error code
Computer ID 2332
Run time 30 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 34.79 GFLOPS
Application version LHCb Simulation v1.02 (vbox64_mt_mcore)
x86_64-pc-linux-gnu
Peak working set size 16.36 MB
Peak swap size 317.56 MB
Peak disk usage 2,382.03 MB
Stderr output
<core_client_version>7.6.33</core_client_version>
<![CDATA[
<message>
process exited with code 5 (0x5, -251)
</message>
<stderr_txt>
2017-12-21 07:36:44 (11935): vboxwrapper (7.7.26196): starting
2017-12-21 07:36:44 (11935): Feature: Checkpoint interval offset (308 seconds)
2017-12-21 07:36:44 (11935): Detected: VirtualBox VboxManage Interface (Version: 5.2.4)
2017-12-21 07:36:44 (11935): Detected: Minimum checkpoint interval (600.000000 seconds)
2017-12-21 07:36:44 (11935): Detected: Heartbeat check (file: 'heartbeat' every 1200.000000 seconds)
2017-12-21 07:36:44 (11935): Successfully copied 'init_data.xml' to the shared directory.
2017-12-21 07:36:44 (11935): Create VM. (boinc_d9679f03a02df903, slot#35)
2017-12-21 07:37:00 (11935): Setting Memory Size for VM. (1830MB)
2017-12-21 07:37:00 (11935): Setting CPU Count for VM. (12)
2017-12-21 07:37:00 (11935): Setting Chipset Options for VM.
2017-12-21 07:37:00 (11935): Setting Boot Options for VM.
2017-12-21 07:37:00 (11935): Setting Network Configuration for NAT.
2017-12-21 07:37:00 (11935): Enabling VM Network Access.
2017-12-21 07:37:13 (11935): Disabling USB Support for VM.
2017-12-21 07:37:13 (11935): Disabling COM Port Support for VM.
2017-12-21 07:37:13 (11935): Disabling LPT Port Support for VM.
2017-12-21 07:37:13 (11935): Disabling Audio Support for VM.
2017-12-21 07:37:13 (11935): Disabling Clipboard Support for VM.
2017-12-21 07:37:14 (11935): Disabling Drag and Drop Support for VM.
2017-12-21 07:37:14 (11935): Adding storage controller(s) to VM.
2017-12-21 07:37:14 (11935): Adding virtual disk drive to VM. (vm_image.vdi)
2017-12-21 07:37:19 (11935): Error in storage attach (fixed disk) for VM: -2135228411
Command:
VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:19 (11935): Powering off VM.
2017-12-21 07:37:19 (11935): Deregistering VM. (boinc_d9679f03a02df903, slot#35)
2017-12-21 07:37:19 (11935): Removing network bandwidth throttle group from VM.
2017-12-21 07:37:19 (11935): Removing storage controller(s) from VM.
2017-12-21 07:37:19 (11935): Removing VM from VirtualBox.
2017-12-21 07:37:20 (11935): Removing virtual disk drive from VirtualBox.
Hypervisor System Log:
VM Execution Log:
VM Startup Log:
VM Trace Log:
UUID: 24a70507-9078-46e2-abe8-80c3a9795403
Settings file: '/usr/bin/slots/35/boinc_d9679f03a02df903/boinc_d9679f03a02df903.vbox'
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --description "LHCb_25826_1513818422.243445_0"
Exit Code: 0
Output:
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --memory 1830
Exit Code: 0
Output:
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --cpus 12
Exit Code: 0
Output:
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --acpi on --ioapic on
Exit Code: 0
Output:
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --boot1 disk --boot2 dvd --boot3 none --boot4 none
Exit Code: 0
Output:
2017-12-21 07:37:00 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --nic1 nat --natdnsproxy1 on --cableconnected1 off
Exit Code: 0
Output:
2017-12-21 07:37:13 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --cableconnected1 on
Exit Code: 0
Output:
2017-12-21 07:37:13 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --usb off
Exit Code: 0
Output:
2017-12-21 07:37:13 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --uart1 off --uart2 off
Exit Code: 0
Output:
2017-12-21 07:37:13 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --lpt1 off --lpt2 off
Exit Code: 0
Output:
2017-12-21 07:37:13 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --audio none
Exit Code: 0
Output:
2017-12-21 07:37:14 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --clipboard disabled
Exit Code: 0
Output:
2017-12-21 07:37:14 (11935):
Command: VBoxManage -q modifyvm "boinc_d9679f03a02df903" --draganddrop disabled
Exit Code: 0
Output:
2017-12-21 07:37:14 (11935):
Command: VBoxManage -q storagectl "boinc_d9679f03a02df903" --name "Hard Disk Controller" --add "ide" --controller "PIIX4"
Exit Code: 0
Output:
2017-12-21 07:37:14 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:15 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:16 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:17 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:18 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:19 (11935):
Command: VBoxManage -q storageattach "boinc_d9679f03a02df903" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --setuuid "" --medium "/usr/bin/slots/35/vm_image.vdi"
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/usr/bin/slots/35/vm_image.vdi"
2017-12-21 07:37:19 (11935):
Command: VBoxManage -q snapshot "boinc_d9679f03a02df903" list
Exit Code: 0
Output:
This machine does not have any snapshots
2017-12-21 07:37:19 (11935):
Command: VBoxManage -q bandwidthctl "boinc_d9679f03a02df903" remove "boinc_d9679f03a02df903_net"
Exit Code: -2135228415
Output:
VBoxManage: error: Could not find a bandwidth group named 'boinc_d9679f03a02df903_net'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component BandwidthControlWrap, interface IBandwidthControl, callee nsISupports
VBoxManage: error: Context: "DeleteBandwidthGroup(name.raw())" at line 259 of file VBoxManageBandwidthControl.cpp
2017-12-21 07:37:19 (11935):
Command: VBoxManage -q storagectl "boinc_d9679f03a02df903" --name "Hard Disk Controller" --remove
Exit Code: 0
Output:
2017-12-21 07:37:20 (11935):
Command: VBoxManage -q unregistervm "boinc_d9679f03a02df903" --delete
Exit Code: 0
Output:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2017-12-21 07:37:20 (11935):
Command: VBoxManage -q closemedium disk "/usr/bin/slots/35/vm_image.vdi" --delete
Exit Code: -2135228411
Output:
VBoxManage: error: Could not get the storage format of the medium '/usr/bin/slots/35/vm_image.vdi' (VERR_NOT_SUPPORTED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
07:37:25 (11935): called boinc_finish(-2135228411)
</stderr_txt>
]]>
|
|
4)
Message boards :
Number crunching :
issue of the day
(Message 808)
Posted 21 Aug 2015 by Dingo
Post: I am running CMS on my desktop OK but on my Windows 7 laptop it does not run. It sits at 0.00% complete and when I looked at Vbox it had thid message. Runtime error opening 'C:\ProgramData\BOINC\slots\3\boinc_7b8c6c74b1591434\boinc_7b8c6c74b1591434.vbox' for reading: -103(Path not found.). D:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long __cdecl Machine::registeredInit(void)). Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} I had a look and the file is not there ? C:\ProgramData\BOINC\slots\3\boinc_7b8c6c74b1591434\boinc_7b8c6c74b1591434.vbox This is the host: http://boincai05.cern.ch/CMS-dev/results.php?hostid=641 |
©2023 CERN