| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Task aborted by server when quorum not yet reached. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Beyond me, but happen to look because this task has been sitting there since june 6 in pending and since june 12 in pending verification state. The _6 task gets server aborted some 12 hours into the job for no apparent reason, log but for version info is empty. The _7 job is send before _6 is aborted and ends in no reply to initiate _8 due on the 23rd. Is this in snafu coding class, or does it have supernatural intelligence behind this?
FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 8-- - In Progress 6/19/14 15:32:30 6/23/14 03:32:30 0.00 0.0 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 7-- - No Reply 6/16/14 03:31:54 6/19/14 15:31:54 0.00 0.0 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 6-- 716 Server Aborted 6/12/14 15:31:46 6/16/14 05:44:59 11.52 101.7 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 5-- 716 Error 6/12/14 14:49:55 6/12/14 15:31:28 0.21 3.3 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 4-- 716 Pending Verification 6/10/14 20:16:52 6/12/14 14:49:29 16.71 254.0 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 3-- 716 Error 6/10/14 12:00:12 6/10/14 20:16:45 3.07 31.9 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 2-- 716 Error 6/10/14 11:51:50 6/10/14 11:59:51 0.00 0.0 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 1-- 716 Pending Verification 6/4/14 22:41:06 6/6/14 06:29:37 14.72 61.1 / 0.0 FAHV_ x3VQ5_ A_ IN_ LEDGFa_ rig_ 0219818_ 0062_ 0-- 716 Error 6/4/14 22:40:36 6/10/14 11:51:27 10.02 67.1 / 0.0 Do note that there seems to be an issue with tasks when the charging is not keeping up with the battery draw-down, leading to a continues suspend resume and eventual crashing of tasks. Someone was kind enough to request a hysteresis setting, to not resume computing until battery has reached a certain recharge level, but the conversation sadly went another deaf ear pathway from the developers side. This would have allowed to have an accelerated battery recharge and then a continuous computing until the lower battery level was reached again. To example, resume computing at 100% and pause when reaching 60%, to not resume until 100% is reached again. At any rate, these tasks keep crashing out with signal 11, without exception, not the infamous 195, to which we're still awaiting a fix. |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges: 
|
I don't think that tells us just when _6 was server aborted. I believe WCG runs with an error limit of five on its WUs. If the no reply is treated like an error towards this limit, then this WU would have hit it. Perhaps the processing that aborts the WU doesn't run constantly and hadn't aborted _8 at this point? Just speculating though.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not going to say much more, the No Reply _7 still came, 'after' _8 came back with error kicking off another copy sent. The _7 was declared a valid with one of the earlier pending verification copies. So much flooring the error theories, which anyway for the android platform is set higher than the regular platforms, else the android validation rate would be even worse then it's already, atrocious. You may fill it in as you go, the evidence, this result having collected 8 errors with 2 in progress:
FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 9-- - In Progress 6/19/14 00:00:09 6/22/14 12:00:09 0.00 0.0 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 8-- 716 Error 6/17/14 08:08:09 6/18/14 23:58:39 4.08 44.6 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 7-- 716 Error 6/17/14 07:38:27 6/17/14 08:04:01 0.03 0.5 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 6-- 716 Error 6/17/14 07:04:24 6/17/14 07:37:41 0.50 3.9 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 5-- 716 Error 6/17/14 06:59:40 6/17/14 07:04:00 0.00 0.0 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 4-- 716 Error 6/17/14 06:48:00 6/17/14 06:59:17 0.04 0.2 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 3-- 716 Error 6/16/14 16:17:44 6/17/14 06:46:02 0.10 1.9 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 2-- 716 Error 6/16/14 12:36:40 6/16/14 16:17:25 0.03 1.0 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 1-- - In Progress 6/16/14 12:08:06 6/26/14 12:08:06 0.00 0.0 / 0.0 FAHV_ x3NF8ledgfA1577_ 0816947_ 0036_ 0-- 716 Error 6/16/14 12:07:17 6/16/14 12:36:13 0.19 1.6 / 0.0 Question remains, for those that do have access to the code: Why was that _6 copy server aborted when it was running, no sign the whole task was to be taken out of circulation. |
||
|
|
|