-------- Original Message --------
Subject: Re: [boinc_dev] Retention of volunteers - why
ERR_TOO_MANY_EXITS?
Date: Tue, 18 Mar 2014 22:08:14 +0100
From: Filip Rydlo <[email protected]>
To: David Anderson <[email protected]>
David,
yeah, I think I know what might be the cause. I remember antivirus
*AVG
2013* free edition *DID kill* my WUs of asteroids and SETi several times, at
random times ... and also did display a message about it , moving it to
quarantine. It did this about once a month last year , and I was helpless to
convince it to add this to exceptions. I was fighting it really hard. ... On
an
OLD intel Atom 1.6 GHz with HT and sSSE3 ... (CPU without out-of-order
execution)
I finally given up and switched that minibook OFF for good, forever. :-)))
It might be the same or similar issue with security software there :-)
*Namaste*
Filip
2014-03-18 20:09 GMT+01:00 David Anderson <[email protected]
<mailto:[email protected]>>:
Are any other computers having this problem?
Let's maintain some perspective.
TOO_MANY_EXITS is not caused by BOINC suspending/resuming the app.
On Windows, it typically means that something outside BOINC is killing the
app.
Perhaps security software; BOINC has no way of knowing.
Problems like this are usually solved by communicating with the volunteer.
I'm not sure what you mean by "black box".
BOINC is the opposite of a black box.
Do you have any specific suggestions?
On 18-Mar-2014 8:05 AM, Richard Haselgrove wrote:
Looking around at SETI, trying to analyse how well the server was
performing
while the status page was dysfunctional, I came across this user.
http://setiathome.berkeley.__edu/show_host_detail.php?__hostid=7220378
<http://setiathome.berkeley.edu/show_host_detail.php?hostid=7220378>
He (and his - somewhat elderly - computer) have been members for about
3 weeks.
He's got a little credit, both at SETI and at Cosmology, so the computer
seems to
be in working order.
But now, every single task - at both projects, today - is failing with
Exit
status-226 (0xffffffffffffff1e) ERR_TOO_MANY_EXITS (oh, and a few
download
errors).
He seems to be using what was the recommended BOINC at the time (v7.2.39),
stock
science applications, and I'd be willing to bet default BOINC computing
settings.
BOINC has just *got* to work for volunteers like that, out of the box -
otherwise
there's no point.
So, as a reasonably experienced "reader of the runes", what can I deduce
from the
error messages presented that I might possibly pass on in a helpful
private
message? Er, as it happens, nothing. I'm stuck. Even task
http://www.cosmologyathome.__org/result.php?resultid=__28640358
<http://www.cosmologyathome.org/result.php?resultid=28640358> - which
ran for
nearly two hours - presents nothing useful in stderr_txt.
If we're going to seal the black box, so that no information leaks out
to the
target "volunteer spare cycles" user, then the onus is on us to make
sure it
works. First time, every time.
Otherwise it's no surprise the number of volunteers goes down, year
after year.
_________________________________________________ boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev> To unsubscribe,
visit
the above URL and (near bottom of page) enter your email address.
_________________________________________________
boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
