1) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7716)
Posted 6 days ago by maeax
Post:
Maybe you only get a black screen and have to wake up the display with e.g. only the Alt-key.
You probably also good improve your throughput by reducing the number of cores to 8 per VM and increase the number of tasks to 7 or even 8.

There is no problem, because of Number of Tasks, or number of using CPU's.
Had at the beginning (2.5 Months ago) this all checked.
for example from Threads (128) to use only Cores(64).
There are three free CPU's, when running no -dev (three, because Einstein@Home use one CPU).
2) Message boards : ATLAS Application : ATLAS vbox v.1.16 (Message 7714)
Posted 6 days ago by maeax
Post:
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3104828
3) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7711)
Posted 6 days ago by maeax
Post:
This two PC's are AMD Ryzen Threadripper PRO 3995WX 64-Cores.
There running only 6 Atlas from production with 10 CPU's per Task.
One of this two PC's running two Atlas-Tasks from -dev if avalaible (The last four days not!).
They have squid avalaible from a Win10-Workstation.
100 Atlas-Tasks per day and PC.
This never ending tasks are only a handful per day.
You can see this in production for this two PC's.

ALT+F1 or ALT+F2 or ALT+F3 in Virtualbox is not avalaible.

https://lhcathome.cern.ch/lhcathome/top_hosts.php
4) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7709)
Posted 6 days ago by maeax
Post:
There are not so many Atlas-Tasks in -dev to see such a problem.
Why, is there no chance for the Atlas-Team to take a deeper look?

Is it ok, to test this, when the new wrapper205 is in production?
5) Message boards : CMS Application : New Version 60.63 (Message 7704)
Posted 7 days ago by maeax
Post:
Ok,
welcome Fardringle,
thank you for your Info's.
6) Message boards : CMS Application : New Version 60.63 (Message 7701)
Posted 8 days ago by maeax
Post:
You have no country set.
7) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7696)
Posted 9 days ago by maeax
Post:
In Production Atlas-Task stopping for confirm-Error after 7-8 min itsself.
When there is no input and less 1 min. CPU,
the Task running hours, only the volunteer can stop this task.
This is for a handful tasks every day seen.
Is it possible to make a correction in this new version?
This is a example from last night (5 hours! - two of them started at the same time)
https://lhcathome.cern.ch/lhcathome/result.php?resultid=361685586


This is, when two Atlas-Tasks starting in the same second on the same PC!
<stderr_txt>
2022-07-30 18:59:49 (16048): Detected: vboxwrapper 26197
2022-07-30 18:59:49 (16048): Detected: BOINC client v7.7
2022-07-30 18:59:49 (16048): Detected: VirtualBox VboxManage Interface (Version: 6.1.36)
2022-07-30 18:59:50 (16048): Successfully copied 'init_data.xml' to the shared directory.
2022-07-30 18:59:51 (16048): Create VM. (boinc_95a7fe58546dd873, slot#5)
2022-07-30 18:59:51 (16048): Setting Memory Size for VM. (10250MB)

2022-07-30 18:59:49 (24000): Detected: vboxwrapper 26197
2022-07-30 18:59:49 (24000): Detected: BOINC client v7.7
2022-07-30 18:59:49 (24000): Detected: VirtualBox VboxManage Interface (Version: 6.1.36)
2022-07-30 18:59:50 (24000): Successfully copied 'init_data.xml' to the shared directory.
2022-07-30 18:59:52 (24000): Create VM. (boinc_e094d3f0813a1289, slot#6)
2022-07-30 18:59:52 (24000): Setting Memory Size for VM. (10250MB)

Discovered this after 2 hours runtime with less then 1 min. CPU-Time for both (using 10 CPU's).
8) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7691)
Posted 9 days ago by maeax
Post:
There are not so many Atlas-Tasks in -dev to see such a problem.
Why, is there no chance for the Atlas-Team to take a deeper look?
9) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7687)
Posted 9 days ago by maeax
Post:
This is from a production Atlas under Win11pro, ending after 7-8 min. with confirm-Error stderr.txt:
2022-07-30 11:20:42 (17436): Guest Log: *** The last 20 lines of the pilot log: ***
2022-07-30 11:20:42 (17436): Guest Log: ---- Retrieve pilot code ----
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,676 [wrapper] Using piloturl: local
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,676 [wrapper] Only supporting pilot3 so pilotbase directory: pilot3
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,677 [wrapper] piloturl=local so download not needed
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,678 [wrapper] local tarball pilot3.tar.gz exists OK
2022-07-30 11:20:42 (17436): Guest Log: tar: Skipping to next header
2022-07-30 11:20:42 (17436): Guest Log: gzip: stdin: unexpected end of file
2022-07-30 11:20:42 (17436): Guest Log: tar: Child returned status 1
2022-07-30 11:20:42 (17436): Guest Log: tar: Error is not recoverable: exiting now
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,688 [wrapper] ERROR: pilot extraction failed for pilot3.tar.gz
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,689 [wrapper] ERROR: pilot extraction failed for pilot3.tar.gz
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,690 [wrapper] FATAL: failed to get pilot code
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,691 [wrapper] FATAL: failed to get pilot code
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,692 [wrapper] apfmon messages muted
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,693 [wrapper] ==== wrapper stdout END ====
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,694 [wrapper] ==== wrapper stderr END ====
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,695 [wrapper] wrapperfault ec=1, duration=0
2022-07-30 11:20:42 (17436): Guest Log: 2022-07-30 09:20:42,696 [wrapper] apfmon messages muted
2022-07-30 11:20:42 (17436): Guest Log: *** Listing of results directory ***
10) Message boards : ATLAS Application : Threadripper pro 3995WX (Message 7684)
Posted 9 days ago by maeax
Post:
This month 9 TByte, last month 7 TByte over ISP.
Proxy: 4 TByte in LAN transfered. 2 GByte Data in 3 days in access.log
100 Atlas-Tasks (10 CPU) per day and PC.
11) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7675)
Posted 10 days ago by maeax
Post:
In Production Atlas-Task stopping for confirm-Error after 7-8 min itsself.
When there is no input and less 1 min. CPU,
the Task running hours, only the volunteer can stop this task.
This is for a handful tasks every day seen.
Is it possible to make a correction in this new version?
This is a example from last night (5 hours! - two of them started at the same time)
https://lhcathome.cern.ch/lhcathome/result.php?resultid=361685586
12) Message boards : ATLAS Application : ATLAS vbox v.1.15 (Message 7670)
Posted 10 days ago by maeax
Post:
29.07.2022 11:44:29 | lhcathome-dev | No tasks are available for ATLAS Simulation
Windows
13) Message boards : CMS Application : New Version 60.63 (Message 7663)
Posted 11 days ago by maeax
Post:
1.5 hour is the difference in your shown task between the next running job inside of the CMS task.
Why is this so long? Because of missing CMS-Data?
Have checked two in production from my side.
Seeing the same.
It seem only a protocol notice from the elapsed time.
14) Message boards : Theory Application : New Version 5.40 (Message 7659)
Posted 11 days ago by maeax
Post:
https://lhcathomedev.cern.ch/lhcathome-dev/workunit.php?wuid=2197795
making a upgrade of Virtualbox (6.1.36) in the next few hours. Was planned.
After this installation restart this task.

Now: alice.cern.ch waiting for the delivery of SIGUSR1
15) Message boards : Theory Application : New Version 5.40 (Message 7655)
Posted 11 days ago by maeax
Post:
grep: /etc/redhat-release: No such file or directory
shown also for Theory and CMS when task is starting.
-dev or Production.
Is this a normal info?

This task is broken from Virtualbox.
Last lines from stderr.txt
2022-07-28 11:41:55 (22340): Guest Log: [INFO] Detected local proxy http://10.241.124.14:3128 in init_data.xml
2022-07-28 11:41:55 (22340): Guest Log: [INFO] Testing connection to 10.241.124.14 on port 3128
2022-07-28 11:41:55 (22340): Guest Log: [INFO] Ncat: Version 7.50 ( https://nmap.org/ncat )
2022-07-28 11:41:55 (22340): Guest Log: Ncat: Connected to 10.241.124.14:3128.
2022-07-28 11:41:55 (22340): Guest Log: Ncat: 0 bytes sent, 0 bytes received in 0.02 seconds.
2022-07-28 11:41:55 (22340): Guest Log: [INFO] 0
2022-07-28 11:41:58 (22340): Guest Log: 11:41:52 CEST +02:00 2022-07-28: cranky: [INFO] Detected Theory App
2022-07-28 11:41:58 (22340): Guest Log: 11:41:52 CEST +02:00 2022-07-28: cranky: [INFO] Checking CVMFS.
2022-07-28 11:41:59 (22340): Guest Log: Probing /cvmfs/sft.cern.ch... OK
2022-07-28 11:41:59 (22340): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
2022-07-28 11:41:59 (22340): Guest Log: 2.5.2.0 4110 0 26084 23466 3 1 265080 4096000 0 65024 0 0 n/a 0 0 http://s1cern-cvmfs.openhtc.io/cvmfs/sft.cern.ch http://10.241.124.14:3128 1
2022-07-28 11:41:59 (22340): Guest Log: Probing /cvmfs/grid.cern.ch... OK
2022-07-28 11:41:59 (22340): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
2022-07-28 11:41:59 (22340): Guest Log: 2.5.2.0 4061 0 28492 18843 3 1 265080 4096000 0 65024 0 2 0 2138 6022 http://s1cern-cvmfs.openhtc.io/cvmfs/grid.cern.ch http://10.241.124.14:3128 1
2022-07-28 11:42:00 (22340): Guest Log: Probing /cvmfs/cernvm-prod.cern.ch... OK
2022-07-28 11:42:00 (22340): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
2022-07-28 11:42:00 (22340): Guest Log: 2.5.2.0 4082 0 26084 268 3 1 265080 4096000 0 65024 0 0 n/a 0 0 http://s1cern-cvmfs.openhtc.io/cvmfs/cernvm-prod.cern.ch http://10.241.124.14:3128 1
2022-07-28 11:42:00 (22340): Guest Log: Probing /cvmfs/alice.cern.ch... OK
2022-07-28 11:42:01 (22340): Guest Log: VERSION PID UPTIME(M) MEM(K) REVISION EXPIRES(M) NOCATALOGS CACHEUSE(K) CACHEMAX(K) NOFDUSE NOFDMAX NOIOERR NOOPEN HITRATE(%) RX(K) SPEED(K/S) HOST PROXY ONLINE
2022-07-28 11:42:01 (22340): Guest Log: 2.5.2.0 4038 0 37860 12923 3 1 265080 4096000 0 65024 0 0 n/a 0 0 http://s1cern-cvmfs.openhtc.io/cvmfs/alice.cern.ch http://10.241.124.14:3128 1
2022-07-28 11:42:01 (22340): Guest Log: 11:41:55 CEST +02:00 2022-07-28: cranky: [INFO] Checking runc.
2022-07-28 11:42:01 (22340): Guest Log: 11:41:55 CEST +02:00 2022-07-28: cranky: [INFO] Creating the filesystem.
2022-07-28 11:42:01 (22340): Guest Log: 11:41:55 CEST +02:00 2022-07-28: cranky: [INFO] Using /cvmfs/cernvm-prod.cern.ch/cvm3
2022-07-28 11:42:01 (22340): Guest Log: 11:41:55 CEST +02:00 2022-07-28: cranky: [INFO] Updating config.json.
2022-07-28 11:42:01 (22340): Guest Log: 11:41:55 CEST +02:00 2022-07-28: cranky: [INFO] Running Container 'runc'.
2022-07-28 11:42:04 (22340): Guest Log: job: htmld=/shared/html/job
2022-07-28 11:42:04 (22340): Guest Log: job: unpack exitcode=0
2022-07-28 11:42:05 (22340): Guest Log: 11:41:59 CEST +02:00 2022-07-28: cranky: [INFO] ===> [runRivet] Thu Jul 28 09:41:58 UTC 2022 [boinc pp jets 7000 20,-,360 - pythia8 8.244 tune-monash13 100000 271]
https://lhcathomedev.cern.ch/lhcathome-dev/workunit.php?wuid=2197795
was also errored out from wingman.
making a upgrade of Virtualbox (6.1.36) in the next few hours. Was planned.
After this will restart this task.
16) Message boards : CMS Application : New Version 60.63 (Message 7652)
Posted 11 days ago by maeax
Post:
Shutdown after 12 hours is now ok.
Graphic on the left side of the Boincmanager show Apache Testpage instead of CMS-Data.
17) Message boards : CMS Application : New Version 60.63 (Message 7642)
Posted 12 days ago by maeax
Post:
Seeing the same.
6 hours idle and 17:30 hours runtime.
18) Message boards : CMS Application : New Version 60.63 (Message 7635)
Posted 13 days ago by maeax
Post:
BOINC's Show graphics displays a webpage with: Scientific Linux Test Page ..... and not the log files.

+1
19) Message boards : General Discussion : WINDOWS Atlas and Theory vbox - postponed (Message 7628)
Posted 14 days ago by maeax
Post:
I restarted testing of a pre-release vboxwrapper with multi-attach disks in the combination 1 dev-ATLAS (multi-attach) , 1 dev-Theory (multi-attach) and 1 production-Theory (normal).
The developer has made a minor change working around a VirtualBox error.
Somehow sometimes Vbox wrote VM-disk properties into a file where it was usual in old VBox versions.
That's why we got in our error tasks these strange message:
the media type 'MultiAttach' can only be attached to machines that were created with VirtualBox 4.0 or later
Tasks returned after 10:00 UTC today have used the newest pre-release.
20) Message boards : General Discussion : WINDOWS Atlas and Theory vbox - postponed (Message 7625)
Posted 14 days ago by maeax
Post:
Have the developer changed this Statement,
the media type 'MultiAttach' can only be attached to machines that were created with VirtualBox 4.0 or later?


Next 20


©2022 CERN