I just forced to run my first Seti Enhanced result here on Seti.

I got a computation error.
In Messages I found:

05/05/2006 00:41:18|SETI@home|Unrecoverable error for result 01mr99aa.11938.5762.336072.3.211_5 ( - exit code -6 (0xfffffffa))

The Result ID shows:

<core_client_version>5.4.8</core_client_version>
<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: 210

---

05/05/2006 00:41:18|SETI@home|Unrecoverable error for result 01mr99aa.11938.5762.336072.3.211_5 ( - exit code -6 (0xfffffffa))

This is a corrupt wu, got a couple of these myself with same error-code, and a closer look revealed they was missing the wu-header...

For some reason we are getting an unusual number of download errors on both the standard and enhanced clients. We're looking into the cause...

05/05/2006 00:41:18|SETI@home|Unrecoverable error for result 01mr99aa.11938.5762.336072.3.211_5 ( - exit code -6 (0xfffffffa))

This is a corrupt wu, got a couple of these myself with same error-code, and a closer look revealed they was missing the wu-header...

---

@SETIEric@qoto.org (Mastodon)

01mr99aa.280.6337.529820.3.193

Is this one missing anything? It's already been a client error on 2 hosts. I haven't started crunching it yet.

---

Founder of BOINC team Objectivists. Oh the humanity! Rational people crunching data!
I did NOT authorize this belly writing!

I got one SETI Enhanced workunit and it also got a computation error, along with everyone else that got it. Bad header error.

Yep Same problem Client Error http://setiathome.berkeley.edu/workunit.php?wuid=76320383

John

---

01mr99aa.280.6337.529820.3.193

Is this one missing anything? It's already been a client error on 2 hosts. I haven't started crunching it yet.

This one errored out. Went thru messages and noticed that boinc requested 242 seconds of work on one occasionand .03 seconds onanother. never seenthat before.

---

Founder of BOINC team Objectivists. Oh the humanity! Rational people crunching data!
I did NOT authorize this belly writing!

For some reason we are getting an unusual number of download errors on both the standard and enhanced clients. We're looking into the cause...

BOINC core client v4.45-v5.3.14 has download-bugs, these normally only shows-up when server has high load, like now you're releasing a new application. So, till v5.4.xx is released, expect the download-errors to continue...


Of course, having atleast some wu released that contains everything except the header, doesn't help-out with the load either...

I just got my first SETI Enhanced unit. After it reached 85% Progress I suspended work while I went out (I did not shut down or restart my computer). When I resumed work the progress reset to 0%.

---

I just got my first SETI Enhanced unit. After it reached 85% Progress I suspended work while I went out (I did not shut down or restart my computer). When I resumed work the progress reset to 0%.

On a Mac? That's interesting. There were of course relatively few Macs in the beta testing, and I don't recall any for which problems were noted.

Some testers had problems with not resuming properly after being preempted by another project, IIRC they found it best to set preferences to leave the application in memory when preempted.

                                                              Joe

I was curious about the graphics on the enhanced, and clicked the show graphics button, which caused this wu to error out after over 6 hours computation. Won't do that again!!


work unit

---

Plus 5,026 SETI Classic Units

This WU has three other client errors.
I think it was simply corrupted.

regards Mike

---

With each crime and every kindness we birth our future.

Was greeted with a "Runtime error, click OK to crash" or something similar, on result-319380400

Now, while a crash in itself is bad, the application should never need to be "OK"-ed before it craps-out, since this means computer can sit idle for hours/days/weeks before user detects it's crashed or has the ability to kill it.


As for the actual message, "The system cannot find the path specified. (0x3) - exit code 3 (0x3)", don't know of anything that should have interfered, since the task was downloaded & crashed during the night when no-one could manually interfere with it, and isn't running the screensaver, and virus-scanner isn't checking BOINC-directories...

The only could guess is that the crash-handling in v5.4.9 or under win2003-64 doesn't work correctly...

I just noticed an odd fact — after processing my first "enhanced" WU - I looked at the "work" tab of BOINC manager, and noticed that all my non-"enhanced" WU's now showed "7:17:40" as their "time to completion" - B4 5.12 loaded, these were in the 4:25:00 range...

---

.

Hello, from Albany, CA!...

{edit]

This one errored out. Went thru messages and noticed that boinc requested 242 seconds of work on one occasion and .03 seconds on another. never seen that before.

I've noticed this B4 enhanced was released...

---

.

Hello, from Albany, CA!...

Just noticed this, not sure if its anything important, but on the graphics view of SETI enhanced the percentage complete is around 2-3% lower than that being displayed on BOINC, 53% complete as opposed to 56%. Not sure if this will make a difference in the end with BOINC thinking the project is done when in reality its not...

---

Human Stupidity Is Infinite...

Was greeted with a "Runtime error, click OK to crash" or something similar, on result-319380400

Now, while a crash in itself is bad, the application should never need to be "OK"-ed before it craps-out, since this means computer can sit idle for hours/days/weeks before user detects it's crashed or has the ability to kill it.


As for the actual message, "The system cannot find the path specified. (0x3) - exit code 3 (0x3)", don't know of anything that should have interfered, since the task was downloaded & crashed during the night when no-one could manually interfere with it, and isn't running the screensaver, and virus-scanner isn't checking BOINC-directories...

The only could guess is that the crash-handling in v5.4.9 or under win2003-64 doesn't work correctly...

That's a windows "error box" so the problem is with windows (I notice that you're using Win 2003, which I can't help you with, I've never run it...)

---

.

Hello, from Albany, CA!...

Usually when you get an error like "The system cannot find the path specified." it's because the directory or application associated with the file has been deleted.

Maybe that you had a result that expected the 5.12 executable in another location?
I know, if that's so, there's nothing you can do about it. ;)

---

Most of my WUs under Seti Enhanced have been finishing in under 3 hours, but one went for over 8 hours and ended with a computation error -- which occured just as I clicked on Show Graphics (I notice that another user experienced the same thing):

5/6/2006 7:09:46 AM|SETI@home|Unrecoverable error for result 01mr99ab.4149.21746.336072.3.153_2 ( - exit code -1073741819 (0xc0000005))


I know there will be occasional computation errors that occur quickly (5 minutes or less) but to waste 8 hours of cpu time seems a shame.

---

I just noticed an odd fact — after processing my first "enhanced" WU - I looked at the "work" tab of BOINC manager, and noticed that all my non-"enhanced" WU's now showed "7:17:40" as their "time to completion" - B4 5.12 loaded, these were in the 4:25:00 range...

The splitter time estimates for "enhanced" work aren't very good, so the DCF (Duration Correction Factor) which adjusts the estimate on your machine for the SETI@Home project just took a large upward jump. With enough data from enough hosts coming in, there should soon be enough data to develop more accurate formulas for the splitter estimates.

                                                           Joe