Message boards :
Theory Application :
Tasks showing about 10 days remaining time in BOINC manager
Message board moderation
Author | Message |
---|---|
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,391,707 RAC: 102,192 |
for serveral days I have been noticing that any new Theory task shows up with 10 days+ in the column "remaining time" in the BOINC manager, which stays quite some time after the task was startet, before it changes to 9 days+ and so on. In reality, these tasks run between less than one hour and just a couple of hours - see https://lhcathome.cern.ch/lhcathome/results.php?hostid=10555784 The problem with this behavour is that sometimes, no new tasks are being downloaded for quite a while (I run 6 tasks concurrently), even with the timebuffer in BOINC set to the maximum of 10 days. Sometimes, the download of GPUGRID tasks which I also run here is also affected. What's going wrong, and how can this problem be fixed? |
Send message Joined: 28 Sep 04 Posts: 674 Credit: 43,152,472 RAC: 15,698 |
What I have observed is that at task start (and before that) the remaining time shows about 2-3 hours. If the task is not finished by that time the remaining time changes to task_limit time, which is 10 days. The actual time the task will take is something between 10 minutes to infinity. Boinc does not know the progress of tasks in VirtualBox as that is not communicated to Boinc. [edit] What you see as progress in Boinc Manager is Boinc's simulated progress. In normal Boinc tasks that is used until science applications reports the actual progress it has achieved. As VirtualBox tasks do not report this to Boinc only simulated value can be shown in Boinc. |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,391,707 RAC: 102,192 |
the strange thing is that this enormous amount of "remaining time" has been showing only within the past 5 days or so. Before, it always was just a few hours. Normally, this would not matter anyway - because the task finishes when it's finished. After 50 minutes, after 2 hours, after 10 hours ... However, these unrealistic time spans are causing download problems, since the maximum work buffer in the BOINC manager cannot be set beyond 10 days. The question is: what causes theses tasks to show this totally unrealistic "remaining time" in the BOINC manager all of a sudden, whereas it all worked well until 5 days ago? |
Send message Joined: 28 Sep 04 Posts: 674 Credit: 43,152,472 RAC: 15,698 |
the strange thing is that this enormous amount of "remaining time" has been showing only within the past 5 days or so. Before, it always was just a few hours. I've seen this behavior ever since the 10 day run time limit was introduced in version 300.06. That was in May. There was some discussion about it already then, here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5419#42408 |
Send message Joined: 2 May 07 Posts: 2071 Credit: 156,137,814 RAC: 105,274 |
This Theory Theory_2390-1107648-40 stopped after 10 days without success: https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=144346124 |
Send message Joined: 18 Nov 17 Posts: 119 Credit: 51,296,823 RAC: 21,044 |
This Theory Theory_2390-1107648-40 stopped after 10 days without success: Looks like deadline and run-time limit of 10 days is not enough. I've just got successful result of this task: https://lhcathome.cern.ch/lhcathome/result.php?resultid=288477387 Run time 9 days 1 hours 1 min 4 sec CPU time 8 days 20 hours 19 min 40 sec It was runnig running 24/7 and still too close to deadline. |
Send message Joined: 15 Jun 08 Posts: 2386 Credit: 222,951,192 RAC: 137,202 |
https://lhcathome.cern.ch/lhcathome/result.php?resultid=288477387 It looks like the task started a couple of times from the scratch. Unfortunately the log doesn't tell why: Attempt 1 2020-10-30 21:35:05 (198628): Detected: vboxwrapper 26197 2020-10-30 21:35:05 (198628): Detected: BOINC client v7.7 2020-10-30 21:35:05 (198628): Status Report: Detected vboxsvc.exe. (PID = '6420') 2020-10-30 21:35:05 (198628): Detected: VirtualBox VboxManage Interface (Version: 5.2.22) . . . 2020-11-04 00:45:44 (198628): Status Report: CPU Time: '352315.310417' 2020-11-04 01:04:09 (198628): Stopping VM. 2020-11-04 01:04:10 (198628): Error in stop VM for VM: -2147024891 Command: VBoxManage -q controlvm "boinc_21b2f0ff66b42e14" savestate Output: VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: The object is not ready VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient 2020-11-04 01:04:10 (198628): VM did not stop when requested. 2020-11-04 01:04:10 (198628): VM was successfully terminated. Attempt 2 2020-11-04 01:05:17 (1172): Detected: vboxwrapper 26197 2020-11-04 01:05:17 (1172): Detected: BOINC client v7.7 2020-11-04 01:05:17 (1172): Status Report: Launching vboxsvc.exe. (PID = '716') 2020-11-04 01:05:28 (1172): Detected: VirtualBox VboxManage Interface (Version: 5.2.22) . . . 2020-11-04 01:08:53 (1172): Guest Log: 23:08:55 CET +01:00 2020-11-03: cranky: [INFO] ===> [runRivet] Tue Nov 3 22:08:54 UTC 2020 [boinc pp jets 13000 180,-,3560 - pythia8 8.240 cr1 100000 58] 2020-11-04 01:10:26 (1172): Stopping VM. 2020-11-04 01:10:26 (1172): Error in stop VM for VM: -2147024891 Command: VBoxManage -q controlvm "boinc_21b2f0ff66b42e14" savestate Output: VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: The object is not ready VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component VirtualBoxClientWrap, interface IVirtualBoxClient 2020-11-04 01:10:26 (1172): VM did not stop when requested. 2020-11-04 01:10:26 (1172): VM was successfully terminated. Attempt 3 (success after 4.8 d) 2020-11-04 10:55:19 (1068): Detected: vboxwrapper 26197 2020-11-04 10:55:19 (1068): Detected: BOINC client v7.7 2020-11-04 10:55:19 (1068): Status Report: Launching vboxsvc.exe. (PID = '1796') 2020-11-04 10:55:24 (1068): Detected: VirtualBox VboxManage Interface (Version: 5.2.22) . . . 2020-11-09 08:32:27 (1068): Guest Log: 6808m34.767s 73m26.831s 2020-11-09 08:32:27 (1068): Guest Log: job: cpuusage=412922 |
Send message Joined: 4 Oct 05 Posts: 32 Credit: 344,444 RAC: 0 |
I've gotten these as well, how forgiving are they on late returns for these? I've been cancelling them if they go more than a day past their due date. However, my host is not on 24/7. Click here to see My Detailed BOINC Stats |
Send message Joined: 4 Oct 05 Posts: 32 Credit: 344,444 RAC: 0 |
Looks like the "grace period" is 48 hours. 11 Jan 2021, 5:59:18 UTC 20 Jan 2021, 5:37:09 UTC Completed and validated 10 Jan 2021, 5:58:10 UTC 19 Jan 2021, 15:46:07 UTC Completed, too late to validate Click here to see My Detailed BOINC Stats |
Send message Joined: 14 Jan 10 Posts: 1268 Credit: 8,421,616 RAC: 2,139 |
Looks like the "grace period" is 48 hours.Your example was not a Theory task, but sixtrack: Sent 10 Jan 2021, 5:58:10 UTC Report deadline 17 Jan 2021, 21:30:24 UTC Received 19 Jan 2021, 15:46:07 UTC The resend was returned before yours. |
©2024 CERN