Message boards :
ATLAS application :
ATLAS vbox version 2.00
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · Next
Author | Message |
---|---|
Send message Joined: 15 Jun 08 Posts: 2532 Credit: 253,722,201 RAC: 34,439 |
From your logfile: 2019-10-14 18:06:37 (11056): Guest Log: "exeErrorDiag": "Non-zero return code from EVNTtoHITS (65); Logfile error in log.EVNTtoHITS: \"Segmentation fault: Event counter: 19; Run: 284500; Evt: 3543749; Current algorithm: ISF_Kernel_FullG4; Current Function: unknown\"", Segmentation fault This is something David Cameron should investigate or forward to the developers. |
Send message Joined: 19 Feb 08 Posts: 708 Credit: 4,336,250 RAC: 0 |
3 out of 4 produced HITS files. Another is running. Tullio |
Send message Joined: 14 Jan 10 Posts: 1417 Credit: 9,441,837 RAC: 794 |
Why do I get a task running the previous ATLAS version instead of version 2.00. It also re-downloaded the old ATLASM_2017_03_01.vdi Task: KNmMDmt2UevnsSi4apGgGQJmABFKDmABFKDmgPVNDmABFKDmL0ckcm_0 ----- 1.01 ATLAS Simulation (vbox64_mt_mcore_atlas) |
Send message Joined: 9 Jan 15 Posts: 151 Credit: 431,596,822 RAC: 0 |
Got a few ATLAS Simulation v2.00 (vbox64_mt_mcore_atlas) x86_64-pc-linux-gnu but server fallback to v1.01 on last downloaded task. Was there any issue with v2.00? Same as for others i got a few long runners up to 4 days now. 2 of them stalled with kernal panic and 2 with reset adapter. When check task list it appears that many vbox v1.01 got invalid/error on upload </stderr_txt> <message> upload failure: <file_xfer_error> <file_name>AqhLDmNm2dvnsSi4apGgGQJmABFKDmABFKDmRR5ZDmABFKDm4Ju39n_0_r644774494_ATLAS_result</file_name> <error_code>-161 (not found)</error_code> </file_xfer_error> </message> Was the data purged on server or any issue on servers to receive result file? Issue started yesterday and i see several from today. |
Send message Joined: 15 Jun 08 Posts: 2532 Credit: 253,722,201 RAC: 34,439 |
... previous ATLAS version instead of version 2.00 Might be that BOINC has not been restarted on at least one of the servers since v2.00 has bee released. |
Send message Joined: 9 Jan 15 Posts: 151 Credit: 431,596,822 RAC: 0 |
I have checked few of my host and it looks to an issue to get work on vbox vm:s. With old vbox 1.01 application it allow me to reach top and i would that only one process of Athena.py is running. I could not reach top from console on new 2.00 Centos 7. Stuck on login on each session but from system monitor they stay on low usage. Would like to see if cpu and ram usage and which processes but not possible. turn on Native application with 2.72 they fire up fine up running after getting data. |
Send message Joined: 13 May 14 Posts: 387 Credit: 15,314,184 RAC: 0 |
I have now deprecated the 1.01 versions so only 2.00 should be sent out now. |
Send message Joined: 7 May 08 Posts: 217 Credit: 1,575,053 RAC: 244 |
I'm returning to sixtrack, waiting for more stable atlas app |
Send message Joined: 27 Sep 08 Posts: 847 Credit: 691,371,233 RAC: 103,242 |
I got a few completed, pushed my success rate of ATLAS tasks to 34% |
Send message Joined: 13 May 14 Posts: 387 Credit: 15,314,184 RAC: 0 |
I have checked few of my host and it looks to an issue to get work on vbox vm:s. With old vbox 1.01 application it allow me to reach top and i would that only one process of Athena.py is running. With thanks (again) to computezrmle, we will now have a better "top" display on console 3 which avoids the annoying scrolling effects. This will become active for new WU within a few hours. |
Send message Joined: 6 Jul 17 Posts: 22 Credit: 29,430,354 RAC: 0 |
Version 2 works with Virtualbox fine on my machines, but it would be nice if the VM Console will show something at Alt-F2. That's the best point to control working of the WU. |
Send message Joined: 2 May 07 Posts: 2242 Credit: 173,902,375 RAC: 2,454 |
This is your Virtualbox in use on one PC: 2019-10-17 07:40:37 (6520): Guest Log: BIOS: VirtualBox 5.1.26 Please upgrade to 6.0.x. (with ExtPack) |
Send message Joined: 15 Jun 08 Posts: 2532 Credit: 253,722,201 RAC: 34,439 |
The currently active monitoring script doesn't output anything at ALT-F2 until at least 1 event has finished. As the current ATLAS batch sometimes needs up to 30-40m per event it may look like ALT-F2 has crashed. Be patient. I already sent David a suggestion for an improved monitoring but there are a few (hopefully minor) issues to solve before it can go live. |
Send message Joined: 6 Jul 17 Posts: 22 Credit: 29,430,354 RAC: 0 |
The currently active monitoring script doesn't output anything at ALT-F2 until at least 1 event has finished. I don't think that it will work after 1 Event is finished or 1 Event will use the whole WU run time. Normal i use this funktion only if the WU Runtime rises in an abnormal way. At startup of a WU i use only the CPU Utilisation % of BoincTask for the first hour. Perhaps it's a VirtualBox Version Problem, i think i got Version 5.2.XX on all machines. The version which comes with Boinc. |
Send message Joined: 2 Sep 04 Posts: 455 Credit: 201,207,665 RAC: 27,898 |
|
Send message Joined: 2 May 07 Posts: 2242 Credit: 173,902,375 RAC: 2,454 |
Yes Yeti, have one PC with 6.0.12, since a few days. 5.2.8 is default on Boinc-Webpage. Support is up to July 2020 for 5.2.x. So, will also wait for the complete upgrade. |
Send message Joined: 27 Sep 08 Posts: 847 Credit: 691,371,233 RAC: 103,242 |
I don't think the project team let us know, it's normally one of us that tries it. I still use 5.1.x as more reliable for me, I will try out 6.0.x it works well for the other subproject if I cap the maximum number of cores to be less than 100%, I have to do some testing to find the breaking point on my other computer as I have always let them run to 100% |
Send message Joined: 2 Sep 04 Posts: 455 Credit: 201,207,665 RAC: 27,898 |
I don't think the project team let us know, it's normally one of us that tries it. HM, not really a good idea. In the past, the wrapper of Atlas had some particularities so that it was not a good idea to switch to a new Major-Release from VirtualBox without the okay from the projectteam. Sometimes they had to make special preparations for the wrapper ... Supporting BOINC, a great concept ! |
Send message Joined: 25 Sep 17 Posts: 99 Credit: 3,425,566 RAC: 0 |
Running on Virtual Box 6.0.12 and I think I have a stuck work unit. I don't see any output to Alt+F2 nor Alt+F3 when I go to check. This task has been running for a day or so and I should at least get the TOP info. I have given it a few minutes to update the screens too. Windows task manager shows about 11% cpu usage so the VM is doing something. Is there anything else I can check to see if I am stuck? From Properties window in Boinc Application ATLAS Simulation 2.00 (vbox64_mt_mcore_atlas) Name YzILDmjJ6evnsSi4apGgGQJmABFKDmABFKDmwrETDmABFKDmuXz3im State Running Received 10/17/2019 3:58:54 PM Report deadline 10/24/2019 3:58:53 PM Resources 8 CPUs Estimated computation size 43,200 GFLOPs CPU time 1d 14:09:14 CPU time since checkpoint 00:01:31 Elapsed time 1d 00:49:30 Estimated time remaining 00:01:32 Fraction done 99.896% Virtual memory size 149.73 MB Working set size 9.96 GB Directory slots/0 Process ID 16176 Progress rate 3.960% per hour Executable vboxwrapper_26198ab7_windows_x86_64.exe |
Send message Joined: 25 Sep 17 Posts: 99 Credit: 3,425,566 RAC: 0 |
I took a look at stderr.txt and it appears I am missing the line showing the Atlas job starting.like all my successful, completed tasks. After "2019-10-17 16:03:29 (16176): Guest Log: ATHENA_PROC_NUMBER=8" I don't see something like this, Guest Log: *** Starting ATLAS job. I set no new tasks, aborted all other work units and left the stuck task running. Task link https://lhcathome.cern.ch/lhcathome/result.php?resultid=249135043 Work unit link https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=125127389 |
©2024 CERN