Status 'Cancelled by server' changed

Message boards : BOINC client : Status 'Cancelled by server' changed
Message board moderation

To post messages, you must log in.

AuthorMessage
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 44809 - Posted: 10 Jul 2012, 11:01:36 UTC

Hi Rom, David,

In the newer BOINC versions beyond 7.0.25 the status of by server aborted tasks changed.

Versions 6.10.58, 6.12.33, 6.12.34 and 7.0.25 shows the expected status of ´Cancelled by server´ on the project result pages.
With versions 7.0.27 and 7.0.28 the status is ´Aborted by user´, although I didn´t aborted the tasks, but were surely cancelled by the project,
because the initially sent results were returned to late, but earlier as the resents finished or even started.

CP
ID: 44809 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 44813 - Posted: 10 Jul 2012, 13:23:53 UTC - in response to Message 44809.  

Adding information:

Sent .................... 9 Jul 2012 | 21:45:39 UTC
Received .............. 9 Jul 2012 | 22:49:53 UTC
Server state ......... Over
Outcome .............. Computation error
Client state ........... Aborted by user
Exit status ........... 202 (0xca) Unknown error number
Report deadline ..... 12 Jul 2012 | 0:09:39 UTC
Run time .............. 0.00
CPU time .............. 0.00
Validate state ....... Invalid
Credit .................. 0.00
Application version .. BOINCSIMAP simap application v5.12

Stderr output

<core_client_version>7.0.28</core_client_version>

-------------------

Those server cancellations treated like user aborts are also happening in the SETI@home/AstroPulse Beta project
ID: 44813 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 44814 - Posted: 10 Jul 2012, 13:38:46 UTC - in response to Message 44809.  

I don't think this is a client issue.

It's possible that CP has been misled by a server code update happening at the same time as the new client release - it would be helpful to know which project these messages were seen at - but I suspect this is a mis-reading of what the project is reporting.

There is a difference between 'Cancelled by server' (and the closely related 'Didn't need', for a task which is cancelled before being sent out), and 'Aborted by user'.

Where there is certainly a problem is in the web code which renders the task outcome into text for the user to see. We had a discussion about this at Einstein, some time ago: message 111673, 111705.

Ever since BOINC v6.6.12 (March 2009), the client will self-abort a task in the cache which hasn't been started before the deadline is reached. In that case, the client returns

#define EXIT_UNSTARTED_LATE         200

rather than the alternatives (from http://boinc.berkeley.edu/trac/browser/boinc/trunk/boinc/lib/error_numbers.h)

#define EXIT_ABORTED_BY_CLIENT      194
#define EXIT_ABORTED_VIA_GUI        203

I think it would be a great improvement if exit codes 194 and 200 could be rendered on the website task lists as "Aborted by client", and only exit code 203 rendered as "Aborted by user". The other possible exit codes need appropriate handling too.

@ CP,

You can see the actual exit code/status returned by the client in the task detail page on the project website - it might be helpful if you could check that for the tasks that you're worried about, and post it back here.

Edit - I see (in preview) that CP has posted while I was writing. I'll post the above anyway, even though some of it may have been overtaken by events.
ID: 44814 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 44815 - Posted: 10 Jul 2012, 13:45:46 UTC - in response to Message 44813.  

Ah. So it's

#define EXIT_ABORTED_BY_PROJECT     202

which isn't being picked up by the SIMAP web server code, and is being mis-reported (confusingly reported) as "Aborted by user".

Their code is pretty recent:

<!-- $Id: util.inc 24968 2012-01-02 05:53:42Z davea $ -->

so it's probably quite a widespread problem - as the observations at SETI would confirm.
ID: 44815 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 44816 - Posted: 10 Jul 2012, 14:15:55 UTC - in response to Message 44815.  

Thanks Richard for responding.

Don't forget that BOINC client versions 7.0.25 and older are treated well, if a task is aborted by the project and newer clients have this weird issue.
That's why I posted it in the BOINC core client thread.

I hope Rom and/or David will pickup this 'problem'.

It also has a negative influence on the reliability of hosts, I suppose.
ID: 44816 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 44818 - Posted: 10 Jul 2012, 14:24:42 UTC

Yes, looking again at [trac]changeset:25601[/trac], and specifically at http://boinc.berkeley.edu/trac/changeset/25601/boinc/trunk/boinc/lib/error_numbers.h#, it does look as if those error/exit numbers were substantially revised on 25 April, after v7.0.25 was compiled on 04 April.

It doesn't look as if any change was made to the user web code to accurately reflect both old and new versions of the returned status codes. Do you want to report that to the boinc_alpha mailing list, or should I?
ID: 44818 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 44821 - Posted: 10 Jul 2012, 14:57:39 UTC - in response to Message 44818.  

Hi Richard,

I'm not really an alpha tester, so if you would be so kind to put this bug into the alpha mailing list.

TIA

CP
ID: 44821 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 44822 - Posted: 10 Jul 2012, 15:06:14 UTC - in response to Message 44821.  

OK, will do. I've been having a look round, and there seem to be other inconsistencies - I have a task with

Outcome Computation error 
Client state Compute error 
Exit status -5 (0xfffffffffffffffb) Unknown error number

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
 - exit code -5 (0xfffffffb)
</message>
<stderr_txt>
SETI@home error -5 Can't open file
(work_unit.sah) in read_wu_state() errno=2

File: ..\worker.cpp
Line: 131

</stderr_txt>
]]>

(Just preserving task 2515612720 so I can find it, until it gets purged)

I've got to go out now, but I'll work up a bug report when I get back.
ID: 44822 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 44825 - Posted: 10 Jul 2012, 22:37:53 UTC

Report made, and David has made a fix. So far, deployed on the SETI Main website - look for the line

<!-- $Id: result.inc 25858 2012-07-10 20:21:12Z davea $ -->

(or later - there's a small typo) in the page source of the result pages on other projects to see when they've deployed it.
ID: 44825 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 45185 - Posted: 8 Aug 2012, 6:37:44 UTC - in response to Message 44825.  

I tested it again with BOINC v7.0.33 on the SIMAP project.
IMO it should be fixed in this version, but it isn't.

SIMAP was running: Server software version: 25897

That's higher then the version Richard mentioned and the client version is also built after the code change.


480888 223509 31 Jul 2012 | 1:13:57 UTC 31 Jul 2012 | 3:45:41 UTC Completed and validated 3,094.89 3,086.12 18.27 BOINCSIMAP simap application v5.10
480889 220818 31 Jul 2012 | 1:14:30 UTC 7 Aug 2012 | 18:01:22 UTC Completed and validated 4,784.18 4,303.38 18.27 BOINCSIMAP simap application v5.11
1873251 161968 7 Aug 2012 | 1:14:38 UTC 7 Aug 2012 | 18:01:56 UTC Aborted by user 0.00 0.00 --- BOINCSIMAP simap application v5.12 <-- By server aborted, not by me!

Result:
Name 20120801.239329_2
Workunit 239330
Created 7 Aug 2012 | 1:14:33 UTC
Sent 7 Aug 2012 | 1:14:38 UTC
Received 7 Aug 2012 | 18:01:56 UTC
Server state Over
Outcome Computation error
Client state Aborted by user
Exit status 202 (0xca) Unknown error number
Computer ID 161968
Report deadline 9 Aug 2012 | 3:38:38 UTC
Run time 0.00
CPU time 0.00
Validate state Invalid
Credit 0.00
Application version BOINCSIMAP simap application v5.12
Stderr output

<core_client_version>7.0.33</core_client_version>
ID: 45185 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 45186 - Posted: 8 Aug 2012, 8:18:49 UTC - in response to Message 45185.  

I tested it again with BOINC v7.0.33 on the SIMAP project.
IMO it should be fixed in this version, but it isn't.

SIMAP was running: Server software version: 25897

That's higher then the version Richard mentioned and the client version is also built after the code change.

Unfortunately, the SIMAP web code seems not to have been updated:

<!-- SVN VERSIONS -->
<!-- $Id: translation.inc 21878 2010-07-06 23:31:26Z davea $ -->
<!-- $Id: pm.inc 14019 2007-11-01 23:04:39Z davea $ -->
<!-- $Id: news.inc 23119 2011-02-28 19:02:59Z davea $ -->
<!-- $Id: text_transform.inc 24622 2011-11-20 17:26:32Z davea $ -->
<!-- $Id: stats_sites.inc 22859 2011-01-02 03:07:14Z davea $ -->
<!-- $Id: team.inc 24050 2011-08-26 18:30:13Z davea $ -->
<!-- $Id: user.inc 24447 2011-10-21 06:58:35Z davea $ -->
<!-- $Id: profile.inc 24050 2011-08-26 18:30:13Z davea $ -->
<!-- $Id: util.inc 24968 2012-01-02 05:53:42Z davea $ -->
<!-- $Id: result.inc 24964 2012-01-01 23:54:58Z romw $ -->

That's the one which matters, and the later version is working properly, e.g.

<!-- $Id: result.inc 25858 2012-07-10 20:21:12Z davea $ -->

Result 2524003864: Exit status 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED

I'm afraid it's up to the SIMAP web administrators to update some more of their code - you could try dropping them a line.
ID: 45186 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 45188 - Posted: 8 Aug 2012, 11:56:02 UTC - in response to Message 45186.  

I'm afraid it's up to the SIMAP web administrators to update some more of their code - you could try dropping them a line.

Richard, thanks for answering.

I'll drop them a line, if I understand you right:
The server version doesn't mean automatically, that you also has installed all former source changes,
because your mentioned changes 24964 and 25858 are both lower than SIMAP's server version I mentioned 25897.

Because I found another bug in inconsistent deadlines for resents, SIMAP upgraded meanwhile to software version: 25993

ID: 45188 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 45199 - Posted: 9 Aug 2012, 6:27:53 UTC - in response to Message 45188.  

Because I found another bug in inconsistent deadlines for resents, SIMAP upgraded meanwhile to software version: 25993

Seems not to be a bug, but a feature.

Anyway: using server version 25993 together with client 7.0.33 didn't solve the 'Aborted by user' issue.
The task is cancelled by the server, but the client returns the result with an unknown exit code:

Name 20120801.252506_3
Workunit 252507
Created 9 Aug 2012 | 4:59:19 UTC
Sent 9 Aug 2012 | 4:59:23 UTC
Received 9 Aug 2012 | 5:34:24 UTC
Server state Over
Outcome Computation error
Client state Aborted by user
Exit status 202 (0xca) Unknown error number
Computer ID 161968
Report deadline 11 Aug 2012 | 7:23:23 UTC
Run time 0.00
CPU time 0.00
Validate state Invalid
Credit 0.00
Application version BOINCSIMAP simap application v5.12
Stderr output

<core_client_version>7.0.33</core_client_version>

---------------------

Using older client versions (7.0.25 and older) the state and exit code is OK:


Name 20120801.455673_3
Workunit 455674
Created 9 Aug 2012 | 0:36:49 UTC
Sent 9 Aug 2012 | 0:36:55 UTC
Received 9 Aug 2012 | 1:44:58 UTC
Server state Over
Outcome Redundant result
Client state Cancelled by server
Exit status -221 (0xffffffffffffff23) ERR_ABORTED_BY_PROJECT
Computer ID 222900
Report deadline 11 Aug 2012 | 3:00:55 UTC
Run time 0.00
CPU time 0.00
Validate state Not necessary
Credit 0.00
Application version BOINCSIMAP simap application v5.12
Stderr output

<core_client_version>7.0.25</core_client_version>
ID: 45199 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 45202 - Posted: 9 Aug 2012, 9:36:14 UTC - in response to Message 45199.  

Because I found another bug in inconsistent deadlines for resents, SIMAP upgraded meanwhile to software version: 25993

Seems not to be a bug, but a feature.

Anyway: using server version 25993 together with client 7.0.33 didn't solve the 'Aborted by user' issue.
The task is cancelled by the server, but the client returns the result with an unknown exit code:

Well, whatever they've updated, it seems not to have been the web display code.

That crucial result.inc file is still showing as being rev 24964 when I look at the source HTML for one of my SIMAP result pages this morning. Whether you call it a bug or a feature, it won't go away until they update that file.
ID: 45202 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 45209 - Posted: 9 Aug 2012, 17:53:27 UTC - in response to Message 45202.  

Hello Richard,

I gave them a hint or better said exactly which result.inc to include.

The feature I meant had nothing to do with this 'Aborted by user' issue.
We figured that, although resents should get a shorter deadline, it sometimes happens that a resent gets a longer deadline, when no reliable hosts are available with low workload.
In that case a resent is sent with a longer deadline to a reliable host with an already high workload.

Thanks again.
ID: 45209 · Report as offensive
Crystal Pellet

Send message
Joined: 23 Apr 12
Posts: 40
Netherlands
Message 45210 - Posted: 9 Aug 2012, 20:20:49 UTC - in response to Message 45209.  

The SIMAP project admin/scientist upgraded the result.inc to a bit higher version as you proposed:

<!-- $Id: result.inc 25873 2012-07-13 22:19:26Z boincadm $ -->

Issue solved, hopefully without side effects.

Name 20120801.690336_2
Workunit 690337
Created 9 Aug 2012 | 10:37:46 UTC
Sent 9 Aug 2012 | 10:37:51 UTC
Received 9 Aug 2012 | 20:11:39 UTC
Server state Over
Outcome Computation error
Client state Aborted by user
Exit status 202 (0xca) EXIT_ABORTED_BY_PROJECT
Computer ID 161968
Report deadline 11 Aug 2012 | 13:01:51 UTC
Run time 0.00
CPU time 0.00
Validate state Invalid
Credit 0.00
Application version BOINCSIMAP simap application v5.12
Stderr output

<core_client_version>7.0.33</core_client_version>
ID: 45210 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4602
United Kingdom
Message 45211 - Posted: 9 Aug 2012, 20:38:28 UTC - in response to Message 45210.  

Excellent news - between us, we got it sorted. Just 498 more BOINC projects to fix..... ;-)
ID: 45211 · Report as offensive

Message boards : BOINC client : Status 'Cancelled by server' changed

Copyright © 2021 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.