Some tasks being aborted due to "exceeded elapsed time limit"
log in

Advanced search

Message boards : Number crunching : Some tasks being aborted due to "exceeded elapsed time limit"

Author Message
Thyme Lawn
Send message
Joined: 25 Oct 12
Posts: 55
Credit: 371,176
RAC: 292
Message 2771 - Posted: 27 Nov 2016, 1:39:51 UTC

Run time is highly variable for ce12 tasks.

On my i7-6700K system the successful tasks have ranged from 9 seconds to 1:02:17. One task was aborted by BOINC with elapsed exceeded at 1:03:34 (I was watching BOINC Manager at the time and the task's progress indicator was over 99.9% when it happened):

26-Nov-2016 02:36:09 [Fight Neglected Diseases] Aborting task 16_1962_23339_68548_0: exceeded elapsed time limit 3829.82 (86400.00G/22.56G)

Similarly, on my i5-3230M system the run time for successful tasks has ranged from 14 seconds to 1:11:51, with one elapsed time exceeded abort after 1:37:21:

26-Nov-2016 19:52:03 [Fight Neglected Diseases] Aborting task 16_1978_23553_68548_0: exceeded elapsed time limit 5840.01 (86400.00G/14.79G)

The i5 was recently sent 76 tasks which have been reissued multiple times (31 * task number _5, 20 * _6, 19 * _7, 2 * _8 and 4 * _9). If my morning check reveals that some of these were aborted with exceeded elapsed time I'll make no apologies for manually aborting the rest of them ...
____________
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Dayle Diamond
Send message
Joined: 5 Dec 12
Posts: 62
Credit: 4,116,833
RAC: 1,127
Message 2772 - Posted: 27 Nov 2016, 2:00:42 UTC - in response to Message 2771.

I know you guys think there are priorities other than synching it so we can see all our work units, but I'm seeing _9 and _10 work units too, and I gotta know how much of my 6700K is failing too, and why, or I can't troubleshoot.

Rytis
Project developer
Send message
Joined: 25 Nov 16
Posts: 24
Credit: 219,107
RAC: 1,285
Message 2773 - Posted: 27 Nov 2016, 7:22:07 UTC
Last modified: 27 Nov 2016, 7:55:22 UTC

Yes, there is high variability in task durations and that throws BOINC off-track, especially if you are (un)lucky enough to get multiple short tasks in sequence. I'll try to increase the limits to avoid these aborts.

[edit] Tasks starting with 16_* have been adjusted to have higher limits. Now working on remaining tasks, mostly the ones starting with 17_*.
____________
GridRepublic

Thyme Lawn
Send message
Joined: 25 Oct 12
Posts: 55
Credit: 371,176
RAC: 292
Message 2776 - Posted: 27 Nov 2016, 9:28:17 UTC - in response to Message 2771.

The i5 was recently sent 76 tasks which have been reissued multiple times (31 * task number _5, 20 * _6, 19 * _7, 2 * _8 and 4 * _9). If my morning check reveals that some of these were aborted with exceeded elapsed time I'll make no apologies for manually aborting the rest of them ...

Much to my surprise 48 of those tasks were run overnight, all successfully completed (with run time range 15 seconds to 1:48:43). All of the tasks are of the 17_* variety (the highest reissues I received for 16_* were a few _3 and _4 tasks on my i7):

27-Nov-2016 03:17:46 [Fight Neglected Diseases] [task] Process for 17_1887_22429_68573_7 exited, exit code 0, task state 1 27-Nov-2016 03:25:40 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68568_9 exited, exit code 0, task state 1 27-Nov-2016 03:48:05 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68486_5 exited, exit code 0, task state 1 27-Nov-2016 03:53:22 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68550_5 exited, exit code 0, task state 1 27-Nov-2016 04:01:03 [Fight Neglected Diseases] [task] Process for 17_1887_22429_68521_6 exited, exit code 0, task state 1 27-Nov-2016 04:10:21 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68552_7 exited, exit code 0, task state 1 27-Nov-2016 04:21:36 [Fight Neglected Diseases] [task] Process for 17_1887_22429_68479_7 exited, exit code 0, task state 1 27-Nov-2016 04:28:50 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68628_7 exited, exit code 0, task state 1 27-Nov-2016 04:32:57 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68574_5 exited, exit code 0, task state 1 27-Nov-2016 04:38:32 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68551_5 exited, exit code 0, task state 1 27-Nov-2016 04:46:33 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68536_5 exited, exit code 0, task state 1 27-Nov-2016 04:56:46 [Fight Neglected Diseases] [task] Process for 17_1887_22429_68488_6 exited, exit code 0, task state 1 27-Nov-2016 05:06:11 [Fight Neglected Diseases] [task] Process for 17_1887_22428_68589_7 exited, exit code 0, task state 1 27-Nov-2016 05:12:56 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68502_5 exited, exit code 0, task state 1 27-Nov-2016 05:18:26 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68545_5 exited, exit code 0, task state 1 27-Nov-2016 05:39:01 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68468_6 exited, exit code 0, task state 1 27-Nov-2016 05:41:17 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68537_7 exited, exit code 0, task state 1 27-Nov-2016 06:02:58 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68626_6 exited, exit code 0, task state 1 27-Nov-2016 06:03:14 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68538_5 exited, exit code 0, task state 1 27-Nov-2016 06:07:14 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68501_9 exited, exit code 0, task state 1 27-Nov-2016 06:09:34 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68529_6 exited, exit code 0, task state 1 27-Nov-2016 06:13:01 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68459_5 exited, exit code 0, task state 1 27-Nov-2016 06:16:13 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68581_6 exited, exit code 0, task state 1 27-Nov-2016 06:21:39 [Fight Neglected Diseases] [task] Process for 17_1887_22428_68575_5 exited, exit code 0, task state 1 27-Nov-2016 06:24:24 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68464_5 exited, exit code 0, task state 1 27-Nov-2016 06:35:53 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68478_5 exited, exit code 0, task state 1 27-Nov-2016 06:46:22 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68490_6 exited, exit code 0, task state 1 27-Nov-2016 06:50:01 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68533_7 exited, exit code 0, task state 1 27-Nov-2016 06:52:15 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68580_5 exited, exit code 0, task state 1 27-Nov-2016 06:53:19 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68542_5 exited, exit code 0, task state 1 27-Nov-2016 07:17:43 [Fight Neglected Diseases] [task] Process for 17_1887_22428_68573_7 exited, exit code 0, task state 1 27-Nov-2016 07:36:55 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68573_7 exited, exit code 0, task state 1 27-Nov-2016 07:44:08 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68625_5 exited, exit code 0, task state 1 27-Nov-2016 07:46:01 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68470_9 exited, exit code 0, task state 1 27-Nov-2016 07:51:59 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68548_7 exited, exit code 0, task state 1 27-Nov-2016 08:10:03 [Fight Neglected Diseases] [task] Process for 17_1886_22423_68533_7 exited, exit code 0, task state 1 27-Nov-2016 08:11:50 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68534_5 exited, exit code 0, task state 1 27-Nov-2016 08:13:00 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68480_5 exited, exit code 0, task state 1 27-Nov-2016 08:13:54 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68471_5 exited, exit code 0, task state 1 27-Nov-2016 08:40:18 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68474_9 exited, exit code 0, task state 1 27-Nov-2016 08:41:10 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68527_7 exited, exit code 0, task state 1 27-Nov-2016 08:41:58 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68533_5 exited, exit code 0, task state 1 27-Nov-2016 08:50:56 [Fight Neglected Diseases] [task] Process for 17_1887_22430_68481_6 exited, exit code 0, task state 1 27-Nov-2016 08:55:20 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68547_5 exited, exit code 0, task state 1 27-Nov-2016 08:58:42 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68543_5 exited, exit code 0, task state 1 27-Nov-2016 09:06:50 [Fight Neglected Diseases] [task] Process for 17_1888_22432_68479_7 exited, exit code 0, task state 1 27-Nov-2016 09:11:52 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68472_7 exited, exit code 0, task state 1 27-Nov-2016 09:13:16 [Fight Neglected Diseases] [task] Process for 17_1887_22431_68578_5 exited, exit code 0, task state 1

I'd echo Dayle's plea for access to our task lists so we can dig deeper in our investigations to help you guys out. Personally I don't care whether it's here or on Grid Republic, but given that the forums are here it would make sense to make them accessible from our accounts here (links to pages on GR would work for me).
____________
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Richard Haselgrove
Send message
Joined: 30 May 15
Posts: 25
Credit: 1,979,129
RAC: 1,584
Message 2778 - Posted: 27 Nov 2016, 10:41:50 UTC - in response to Message 2771.

(I was watching BOINC Manager at the time and the task's progress indicator was over 99.9% when it happened)

@ Thyme Lawn:

Remember that BOINC's progress indicator is a highly suspect tool. Ever since about v7.4.9, it has replaced 'real' progress with 'pseudo' progress if applications report zero progress (because users have a tendency to abort tasks that appear not to progress).

Both the original vina app for FiND, and the new wrapper version, don't report their internal progress at all, ever. I got so fed up with the mis-reported pseudo progress that I build my own replacement clients with that function disabled (lines 704-708 of client/app.cpp), so now BOINC Manager - and other monitoring tools - report zero progress at all times. That's messy too, but I prefer the honest unvarnished truth.

Message boards : Number crunching : Some tasks being aborted due to "exceeded elapsed time limit"


Main page · Your account · Message boards


Copyright © 2017 Dr Anthony Chubb