Questions and Answers : Unix/Linux : All tasks in scheduler state uninitialized
Previous · 1 · 2
Author | Message |
---|---|
SGAI-CSIC Send message Joined: 4 Apr 20 Posts: 19 Credit: 15,069,615 RAC: 0 |
I think the problem it's the boinc-client in CentOS, I have created another vm with Debian installation and the task are running: ======= Tasks ======== 1) ----------- name: bhfe_s01_SAVE_ALL_OUT_IGNORE_THE_REST_1iy1rc1g_913393_2_0 WU name: bhfe_s01_SAVE_ALL_OUT_IGNORE_THE_REST_1iy1rc1g_913393_2 project URL: https://boinc.bakerlab.org/rosetta/ report deadline: Sat Apr 18 16:15:23 2020 ready to report: no got server ack: no final CPU time: 0.000000 state: downloaded scheduler state: scheduled exit_status: 0 signal: 0 suspended via GUI: no active_task_state: EXECUTING app version num: 415 checkpoint CPU time: 0.000000 current CPU time: 21.956000 fraction done: 0.000187 swap size: 469 MB working set size: 215 MB estimated CPU time remaining: 21512.713905 2) ----------- name: Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6kl5yf9y_913404_1_0 WU name: Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6kl5yf9y_913404_1 project URL: https://boinc.bakerlab.org/rosetta/ report deadline: Sat Apr 18 16:15:34 2020 ready to report: no got server ack: no final CPU time: 0.000000 state: downloaded scheduler state: scheduled exit_status: 0 signal: 0 suspended via GUI: no active_task_state: EXECUTING app version num: 415 checkpoint CPU time: 0.000000 current CPU time: 14.716000 fraction done: 0.000110 swap size: 364 MB working set size: 116 MB estimated CPU time remaining: 21514.369500 |
SGAI-CSIC Send message Joined: 4 Apr 20 Posts: 19 Credit: 15,069,615 RAC: 0 |
That's right Mod.Sense, it seems a problem between the balance of CPU and memory, I have increased a little the RAM memory (6GB) and the task are running. I will continue to observe it ... |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1684 Credit: 17,933,837 RAC: 22,604 |
Thank you for your help, I try to stop boinc daemon a restart again and I see these messages in the log, perhaps it's a bug of the boinc-client on CentOS? Unfortunately the bottom is missing from the log there, but it looks like you got it sorted. The bottom of the log may (or may not) have had a message about insufficient RAM, but certainly there should have been more messages relating to starting the Tasks. Grant Darwin NT |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1684 Credit: 17,933,837 RAC: 22,604 |
That's right Mod.Sense, it seems a problem between the balance of CPU and memory, I have increased a little the RAM memory (6GB) and the task are running. I will continue to observe it ...You need to allow for up to 1.3GB RAM per Task, most of the current one use much less, but that's the highest requirement i've seen so far (over 3 weeks or so). And those large RAM requirement Tasks also like around 1GB of storage space as well- the Event log will get messages about low DIsk space if it occurs. Grant Darwin NT |
SGAI-CSIC Send message Joined: 4 Apr 20 Posts: 19 Credit: 15,069,615 RAC: 0 |
Thanks to all for the help, now all it's running. Ok, I see what you say, some task demand for memory that others, for example: Some task demand ~ 20 % of mem (1.2 GB) others less ~ 12% ( 700 MB). I understand then that in order to executing the task boinc makes sure have enough expected memory for the sum of all tasks and if it is not fulfilled the tasks do not initialize? |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1684 Credit: 17,933,837 RAC: 22,604 |
I understand then that in order to executing the task boinc makes sure have enough expected memory for the sum of all tasks and if it is not fulfilled the tasks do not initialize?Usually as many as are able to will run. If the next Task to start needs more memory than is available, it won't run. If the memory available is less than the minimum requirement for a single, low memory requirement Task, then none will be able to run. Grant Darwin NT |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Previously you had posted these messages from BOINC startup 19: 15-Apr-2020 14:33:14 (low) [] max memory usage when active: 1894.49 MB 20: 15-Apr-2020 14:33:14 (low) [] max memory usage when idle: 3410.09 MB This indicates that BOINC is configured to only allowed to use about 50% of memory when the machine is active. Depending on how often the machine is used for other things, this could limit things significantly so far as getting BOINC WUs completed. Rosetta Moderator: Mod.Sense |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1684 Credit: 17,933,837 RAC: 22,604 |
Previously you had posted these messages from BOINC startup So, SGAI-CSIC If you go to to your Account, Computing preferences, and change the available memory there to Memory When computer is in use, use at most 90 % When computer is not in use, use at most 95 %(or higher), and that will let BOINC crunch more work. Grant Darwin NT |
SGAI-CSIC Send message Joined: 4 Apr 20 Posts: 19 Credit: 15,069,615 RAC: 0 |
Ok, thanks, I will try :-) |
Questions and Answers :
Unix/Linux :
All tasks in scheduler state uninitialized
©2024 University of Washington
https://www.bakerlab.org