I've not encountered a ton, but there are several WU's in my Results page which are showing as "Computation Error" -- a result that matches several others' crunching attempts...

Bad work units maybe?

They all stsrt with the same date: 07mr07aj...

Anybody else running into these?

Just a heads up for all of you...

[edit]

Here's a few of them:

07mr07aj.7643.20931.3.6.20

07mr07aj.9032.7843.5.6.6

07mr07aj.9032.16023.5.6.12

[/edit]

---

Keep on crunching, all...
SETI@Home Forever!

___Tklop (Step-Founder, U.S. Air Force team)

I've not encountered a ton, but there are several WU's in my Results page which are showing as "Computation Error" -- a result that matches several others' crunching attempts...

Bad work units maybe?

They all stsrt with the same date: 07mr07aj...

Anybody else running into these?

Just a heads up for all of you...

[edit]

Here's a few of them:

07mr07aj.7643.20931.3.6.20

07mr07aj.9032.7843.5.6.6

07mr07aj.9032.16023.5.6.12

07mr07aj.9032.16023.5.6.12

[/edit]

Yesterday's outage caused some WUs with a bad header to go out... I had about 10 myself that surfaced last time I checked.

Yesterday's outage caused some WUs with a bad header to go out... I had about 10 myself that surfaced last time I checked.

Ah... Thanks!

---

Keep on crunching, all...
SETI@Home Forever!

___Tklop (Step-Founder, U.S. Air Force team)

Yesterday's outage caused some WUs with a bad header to go out... I had about 10 myself that surfaced last time I checked.

Ah... Thanks!

You're welcome.. and I just checked again and I have 39 of 'em :(

Yesterday's outage caused some WUs with a bad header to go out... I had about 10 myself that surfaced last time I checked.

Ah... Thanks!

You're welcome.. and I just checked again and I have 39 of 'em :(

So do we have to do anything with or to them?
I have one 17mr07ab.30863.409083.14.6.24_0

---

Anybody else running into these?

Yepp! :-(

---

All time #1 M.U.R.C. Cruncher!

Anybody else running into these?

Yepp! :-(

All my 17xxxxx's have failed within 3 seconds of starting.

Should I abort my remaining 17xxxxx's before they attempt to crunch? Is there any benefit in aborting them rather than letting them fail?ç

13's, 29's and 18's working OK.

Regards,

Nicholas

---

Everything sent today is failing with either client error or compute error.

17mr07ab.30757.4162.12.6.80
17mr07ab.30087.416036.11.6.145
18mr07aa.10677.21749.3.6.156
18mr07aa.10744.5389.5.6.174
18mr07aa.10568.21340.4.6.146
17mr07ab.14071.413991.3.6.121

And others with that workunit are also having their crunching fail.

It's broke. Get the duct tape.

---

* Viking *

Update: I deleted the setiathome_5.27 exe and redownloaded it (which took forever) but it's working okay, at least on this latest workunit - 08mr07ad.14035.1300.3.6.154.

I guess we'll see what happens...

---

* Viking *

Anybody else running into these?

Yepp! :-(

All my 17xxxxx's have failed within 3 seconds of starting.

Should I abort my remaining 17xxxxx's before they attempt to crunch? Is there any benefit in aborting them rather than letting them fail?ç

13's, 29's and 18's working OK.

Regards,

Nicholas

There could also be good 17xxxxx's, so it's better to do some checking. The problem causes the WU to be smaller than usual, so you could look in the boinc\\projects\\setiathome.berkeley.edu folder for those which are less than the usual size, then abort just those. It doesn't matter much if you abort or let them attempt to crunch, either will be seen as a client-side error and cause a reissue to someone else (until the sixth error is returned).

Another approach is to suspend the good WUs so BOINC tries to crunch the other stuff, then resume the good ones. That way you get the same error as if you'd just let them run normally, but sooner.

                                                               Joe

There could also be good 17xxxxx's, so it's better to do some checking. The problem causes the WU to be smaller than usual, so you could look in the boinc\\projects\\setiathome.berkeley.edu folder for those which are less than the usual size, then abort just those. It doesn't matter much if you abort or let them attempt to crunch, either will be seen as a client-side error and cause a reissue to someone else (until the sixth error is returned).

Another approach is to suspend the good WUs so BOINC tries to crunch the other stuff, then resume the good ones. That way you get the same error as if you'd just let them run normally, but sooner.

                                                               Joe

This is like playing whack-a-mole. Every time I abort one, another zero length WU downloads. And my max daily quota is dropping too. I'm going to let them crash normally. At least that way my max daily quota will suffer less.

I too have seen some Compute errors in the last
week and also now, after the restart from the
last tuesday outage.

Some minute ago this host http://setiathome.berkeley.edu/show_host_detail.php?hostid=1852935
had four errors like:

<core_client_version>5.10.20</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
SETI@home error -6 Bad workunit header
!swi.data_type || !found || !swi.nsamples
File: ..\\seti_header.cpp
Line: 235


</stderr_txt>
]]>

I use 5.10.20 with optimized seti (2.4V)

Optimized SETI@Home Enhanced application
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows SSE 32-bit based on S@H V5.15 'Noo? No - Ni!'
Revision: R-2.4V|xK|FFT:IPP_SSE|Ben-Joe

Bye,
Franz

PS: I had to add...
al the four run unit was sent to me the
9 Oct 2007 22:08:59 UTC ... after the last outage.
It is new job, not old.

---

Yep, there was a mess of clinkers early on after the restart for awhile, but the ones I've been getting since around midnight UTC seem to be clean so far.

Alinator

Yep, there was a mess of clinkers early on after the restart for awhile, but the ones I've been getting since around midnight UTC seem to be clean so far.

Alinator

I'm still getting 5-10% bad WUs, but nothing to worry about. They'll burn through quick enough..

I got two of them

<message>
process exited with code 250 (0xfa, -6)
</message>

or
<message>
- exit code -6 (0xfffffffa)
</message>

<stderr_txt>
SETI@home error -6 Bad workunit header
!swi.data_type || !found || !swi.nsamples
File: seti_header.cpp
Line: 235


wuid=163695795
wuid=163212600

Matthias

---

Matthias