21) Message boards : Theory Application : All errors (Message 8257)
Posted 16 Dec 2023 by Crystal Pellet
Post:
There is another mismatch between the current running app (Theory Simulation v5.95 (vbox64_theory) windows_x86_64) and the displayed version on the application page ( https://lhcathomedev.cern.ch/lhcathome-dev/apps.php ) 5.96 (vbox64_theory)
22) Message boards : Theory Application : All errors (Message 8255)
Posted 16 Dec 2023 by Crystal Pellet
Post:
Production runs fine so I have edited the vbox_job of -dev accordingly but after having so many errors, I can't fetch a job to test whether that will work.
I have enough quota to test, but I did not change the xml file. I made just a copy from Theory_2023_12_13.vdi to Theory_2023_12_12.vdi.
(I didn't used the 12_13.vdi before)

2023-12-16 09:35:55 (5216): Adding virtual disk drive to VM. (Theory_2023_12_12.vdi)
.
.
.
2023-12-16 09:37:24 (5216): Guest Log: 09:37:22 CET +01:00 2023-12-16: cranky: [INFO] ===> [runRivet] Sat Dec 16 08:37:22 UTC 2023 [boinc pp mb-inelastic 200 - - pythia6 6.427 353 100000 1062]


Laurence has to create a new Theory_2023_12_13.xml file with the right vdi version.
23) Message boards : Sixtrack Application : Xtrack beam simulation v0.01 windows_intelx86 (Message 8226)
Posted 24 Nov 2023 by Crystal Pellet
Post:
I'm really wondering, whether the Xtrack team is on track.
In March and June Windows 64bit version 0.11 was running and now in November 32bit version 0.01
24) Message boards : Sixtrack Application : Xtrack beam simulation (Message 8220)
Posted 23 Nov 2023 by Crystal Pellet
Post:
Another bunch of test tasks are sent to us volunteers without any communication.
I suppose this time the tasks are coming from researcher Frederik Van der Veken.
The tasks however are useless to test, because they all don't really start and all crash within a few seconds with too many exits.
25) Message boards : General Discussion : Tasks or no Tasks (Message 8075)
Posted 15 May 2023 by Crystal Pellet
Post:
I had run 8 Theory a couple days ago on the 8 thread host but at the same time the server claimed I also had these other 5 Theory tasks.
It happened to me last October, but not with Theory, but with 5 Xtrack beam simulations.
https://lhcathomedev.cern.ch/lhcathome-dev/results.php?hostid=4600&offset=20&show_names=0&state=6&appid=
26) Message boards : Theory Application : Why is there no native_theory on this project? (Message 8067)
Posted 28 Apr 2023 by Crystal Pellet
Post:
Or even vbox64_theory for linux?
On the production server there is:

Platform: Linux running on an AMD x86_64 or Intel EM64T CPU Version: 300.07 (vbox64_theory)
27) Message boards : ATLAS Application : ATLAS vbox and native 3.01 (Message 8046)
Posted 25 Mar 2023 by Crystal Pellet
Post:
I looked in details at the logs of this task and it looked like it took 8 or 9 minutes to get going full steam. But still it could be that the initialisation phase is indeed longer in this new software.
Much longer init phase on my fastest cruncher.
Now it's far over 30 minutes. In production the workers are on full steam after 6 minutes.
28) Message boards : ATLAS Application : ATLAS vbox and native 3.01 (Message 8015)
Posted 21 Mar 2023 by Crystal Pellet
Post:
I got a 500 events task on my dual core / 4 threaded laptop.
I configured it to run a 4 core VM with 3500 MB RAM.
Swap so far used 'only' 1024kB. After 2 hours uptime 49 events out the 500 are ready.
Host's VBoxHeadless.exe cpu-priority set to below normal, but of course laptop gets a bit sluggish.
29) Message boards : ATLAS Application : ATLAS vbox and native 3.01 (Message 8010)
Posted 21 Mar 2023 by Crystal Pellet
Post:
I had 16 dual core tasks, running 8 concurrently. VM setup to use 3500MB RAM.
15 of them did not use swap at all. 1 used 8 kByte of the swapping page.
I want to try to do this with 4-core tasks, but no tasks available.
30) Message boards : ATLAS Application : vbox console monitoring with 3.01 (Message 7996)
Posted 20 Mar 2023 by Crystal Pellet
Post:
The readable text is showing this:
31) Message boards : ATLAS Application : vbox console monitoring with 3.01 (Message 7992)
Posted 20 Mar 2023 by Crystal Pellet
Post:
The monitoring is not working very well.
I'm running a dual core VM, 4800 MB RAM
Only 1 worker is displayed (I also see only 1 python process almost 200% CPU)
Total number of events is displayed (50)
already finished, mean, min, max, estimated time left is not displayed and every 60 seconds several lines of text are flashing (not readable) and cleared.
Worker 1 Event showing showed 2nd, 4th and then 3th event ?? for this worker took ### s (### is changing now and then e.g. 421)

My differencing file 900MB

Edit picture and no swap used, but initial setup etc lasted over 30 minutes.
Flashing text:
32) Message boards : ATLAS Application : ATLAS vbox and native 3.01 (Message 7982)
Posted 20 Mar 2023 by Crystal Pellet
Post:
I would prefer quick tasks. Not because of the size of the HITS-file.
The problem with ATLAS- (and CMS-) tasks is that they don't allow longer suspended periods.
Not all users have fast machines with a lot of cores running 24/7.
They are already happy when they can run a dual-core ATLAS-task during their daily machine uptime.
33) Message boards : Sixtrack Application : Xtrack beam simulation (Message 7941)
Posted 10 Mar 2023 by Crystal Pellet
Post:
Aborted the resends I got. They are running endless.
I let one run overnight: https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3191964
34) Message boards : ATLAS Application : ATLAS vbox v.1.27 (Message 7907)
Posted 8 Dec 2022 by Crystal Pellet
Post:
I had two errors this morning.
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3162937
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3162961
I found in VBox media the parent VDI with a connected child with a yellow rectangle and exclamation mark.
The child however already left the home from his slot #1 last night at 1:15:58 UTC, but the shadow was still there.
I remove the shadow from VBox media and the next first task went fine.
Part of an error result:
2022-12-08 11:29:45 (15424): Adding virtual disk drive to VM. (ATLAS_vbox_1.27_image.vdi)
2022-12-08 11:29:52 (15424): Error in deregister parent vdi for VM: -2135228404
Command:
VBoxManage -q closemedium "D:\Boinc1/projects/lhcathomedev.cern.ch_lhcathome-dev/ATLAS_vbox_1.27_image.vdi" 
Output:
VBoxManage.exe: error: Cannot close medium 'D:\Boinc1\projects\lhcathomedev.cern.ch_lhcathome-dev\ATLAS_vbox_1.27_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 1862 of file VBoxManageDisk.cpp
35) Message boards : News : Server Release 1.4.0 (Message 7904)
Posted 2 Dec 2022 by Crystal Pellet
Post:
And now we are at 1.4.1.
The messages sorting issue in the Message boards reported here,
seems only related to the 'News' section.
36) Message boards : ATLAS Application : ATLAS vbox v.1.18 (Message 7884)
Posted 17 Nov 2022 by Crystal Pellet
Post:
Yesterday the tasks used the new wrapper v26206 as announced, but were still running the old version 1.17 of the application.

Today the new application 1.18-vdi was downloaded.
37) Message boards : News : Server Release 1.4.0 (Message 7883)
Posted 16 Nov 2022 by Crystal Pellet
Post:
Get this line

set_cached_data(): can't open ../cache/f2/server_status.php_job_status

on top of the Server status page.
38) Message boards : News : Server Release 1.4.0 (Message 7871)
Posted 10 Nov 2022 by Crystal Pellet
Post:
When forum posts selected to sort newest first, the newest post is shown below the previous (older) post.
39) Message boards : ATLAS Application : ATLAS vbox v.1.17 (Message 7867)
Posted 8 Nov 2022 by Crystal Pellet
Post:
@Laurence and/or David,

Any plans to update vboxwrapper to the official released version 26206 here at dev and production?
40) Message boards : CMS Application : New Version 60.68 (Message 7850)
Posted 4 Nov 2022 by Crystal Pellet
Post:
A new CMS version was deployed this morning.
No new files were downloaded to my system.

What is the difference to the previous version?

Is it more than avoiding requesting multiple idtokens?


Previous 20 · Next 20


©2024 CERN