1)
Message boards :
Theory Application :
New version 263.90
(Message 37531)
Posted 4 Dec 2018 by peterfilla Post: I upgraded VBox to Vers. 5.2.22 - and now my JOBs are running . . . ist this the solution ??!! |
2)
Message boards :
ATLAS application :
Wrong memory usage for multicore
(Message 29750)
Posted 2 Apr 2017 by peterfilla Post: I had the same problem. The point is (somebody told it to me), that the value of Max # CPU on the LHC-page is used to calculate the amount of memory. I set the Max # CPU to a lower value (6 instead of 24) and use a cc_config for the real number. |
3)
Message boards :
ATLAS application :
New app version 1.01
(Message 29268)
Posted 14 Mar 2017 by peterfilla Post: Only 60 sec. for the checkpoint-interval ??? That should be more I think - perhaps . . . . . |
4)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29169)
Posted 10 Mar 2017 by peterfilla Post: The above error is "solved" (?) : I detached from LHC and reatached - and the new tasks finished OK (I do not know the reason why). My second error (not more than 2 ATLAS-tasks) will be "solved" too : I set the number of CPUs on the server to a lower value, so the calculation of "rsc_memory_bound" gives a lower value (this test is running today). At the moment I am running my CPU with 4-core-tasks at the limit for test - but later I will run 60 - 75 % load (4-core is a good number I heard). |
5)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29145)
Posted 9 Mar 2017 by peterfilla Post: Now I have much more information to continue testing - thanks to all !!! |
6)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29144)
Posted 9 Mar 2017 by peterfilla Post: !!! Thanks for all the informations - now I can continue with special testing !!! |
7)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29138)
Posted 9 Mar 2017 by peterfilla Post: What ist the difference between "Setting Memory Size for VM" (8400MB) 2017-03-09 09:03:40 (5764): vboxwrapper (7.7.26196): starting 2017-03-09 09:03:40 (5764): Feature: Checkpoint interval offset (300 seconds) 2017-03-09 09:03:40 (5764): Detected: VirtualBox COM Interface (Version: 5.1.16) 2017-03-09 09:03:40 (5764): Detected: Minimum checkpoint interval (900.000000 seconds) 2017-03-09 09:03:40 (5764): Successfully copied 'init_data.xml' to the shared directory. 2017-03-09 09:03:40 (5764): Create VM. (boinc_0521eef5705f3a8d, slot#0) 2017-03-09 09:03:40 (5764): Setting Memory Size for VM. (8400MB) 2017-03-09 09:03:40 (5764): Setting CPU Count for VM. (4) 2017-03-09 09:03:40 (5764): Setting Chipset Options for VM. and "rsc_memory_bound" in client_state.xml ? Is the number of CPUs set on the LHC-page used to calculate these values ? and: is this number of CPUs the phys. or the log. CPUs ? perhaps I should set the phys. number . . . and : I will try a changing . . . |
8)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29133)
Posted 9 Mar 2017 by peterfilla Post: Question : Can I change theses values in the client_state.xml ??? (carefully!) |
9)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29132)
Posted 9 Mar 2017 by peterfilla Post: LHC ist the only project. rsc_memory_bound for ATLAS is : 26633830400.00 for each task Theory : 500000000.00 This is in BYTEs ?! Then 2 ATLAS tasks have over 53 GB blocked ?! Am I right ??? |
10)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29128)
Posted 9 Mar 2017 by peterfilla Post: I have a 12/24-core CPU with 64 GB RAM. 2*13.4GB=26.8GB; 2*25.4GB=50.8GB; ??? But the memory_size in the app_config should overrule this . . . And in my actual running test there are 2 ATLAS tasks and 3 Theory task running . . so far, I will go on with testing. |
11)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29127)
Posted 9 Mar 2017 by peterfilla Post: I have a 12/24-core CPU with 64GB RAM. In Options RAM-usage was set to 90% max; the project can run 5 tasks max. The actual test uses 83% of CPU and 26% of RAM with 2 ATLAS and 3 Theory tasks, 3 tasks are waiting (1 ATLAS and 2 Theory). |
12)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29124)
Posted 9 Mar 2017 by peterfilla Post: There is plenty of space . . . <app_config> <app_version> <app_name>Theory</app_name> <plan_class>vbox64</plan_class> <avg_ncpus>4.000000</avg_ncpus> <cmdline>--memory_size_mb 1500</cmdline> </app_version> <app_version> <app_name>ATLAS</app_name> <avg_ncpus>4.000000</avg_ncpus> <plan_class>vbox64_mt_mcore_atlas</plan_class> <cmdline>--memory_size_mb 8400</cmdline> </app_version> </app_config> For the aktual test I reduced the Theory-memory-size, three are now running - but only 2 4-core-ATLAS with 1 waiting. |
13)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29120)
Posted 9 Mar 2017 by peterfilla Post: I am sure, that ist not the reason; I started my tests with 1280MB. But I have 2 problems: This error and the fact, that I can not run more than 2 ATLAS-tasks at the same time. So I set in the app_config for both projekts the mem to 8400MB. First I run ATLAS -> problem only 2 tasks Then I followed your advice : got this error on all tasks. Now I had uninstall VBox (14) and installed the latest (16) and I set up LHC new and make new tests. |
14)
Message boards :
ATLAS application :
-1073740791 (0xC0000409) STATUS_STACK_BUFFER_OVERRUN
(Message 29116)
Posted 8 Mar 2017 by peterfilla Post: I try to run more than one 4-core Theory-tasks and get this error. The memory_size in app_config is set to 5400. |
15)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29115)
Posted 8 Mar 2017 by peterfilla Post: Hello ! I made the same modifications, but set the memory_size to 5400 (last advice) - but : I can only run 2 tasks at the same time, the third task say "waiting for memory". Haw many tasks are you running ? |
16)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29107)
Posted 7 Mar 2017 by peterfilla Post: Thank you very much for helping !!! |
17)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29105)
Posted 7 Mar 2017 by peterfilla Post: Now I am running 6 4-core tasks from theory using the given theory-app_config - and habe no problems . . . perhaps ATLAS has a restriction ??? |
18)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29103)
Posted 7 Mar 2017 by peterfilla Post: I will try it . . . when ATLAS finished. My app_config is as your advice (with "app_config" at start and end). |
19)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29100)
Posted 7 Mar 2017 by peterfilla Post: Not working . . . I changed the app_config: not working; I rebooted: not working; I changed my preferences on the server: not working. At the beginning I got 4 tasks, 2 started and 2 are waiting, and this is now the same situation. |
20)
Message boards :
ATLAS application :
How can I run more than 2 4-core tasks ?
(Message 29097)
Posted 7 Mar 2017 by peterfilla Post: I have a 12/24 CPU with 64 GB Mem; in the old ATLAS project I could run up to 6 4-core tasks without any problems; app_config etc. all OK. |
©2024 CERN