It seems like some diety above has set itself against me completing any work for SETI (ah, I get it - it's the work of the aliens!). This time the result died with the following logged error message (client 4.25):

2005-03-10 20:55:12 [SETI@home] Computation for result 07ja05aa.3636.11152.553406.58 finished
2005-03-10 20:55:12 [SETI@home] Output file 07ja05aa.3636.11152.553406.58_4_0 for result 07ja05aa.3636.11152.553406.58_4 exceeds size limit.
2005-03-10 20:55:12 [SETI@home] File size: 139645.000000 bytes. Limit: 65536.000000 bytes
2005-03-10 20:55:12 [SETI@home] Unrecoverable error for result 07ja05aa.3636.11152.553406.58_4 (<file_xfer_error>
<file_name>07ja05aa.3636.11152.553406.58_4_0</file_name>
<error_code>-131</error_code>
<error_message></error_message>
</file_xfer_error>
)

Size limit in general preferences was set to 0.2GB with leave at least 0GB free. The whole BOINC directory is currently 56MB. And I definitely never set a size linit to 65536.000000 bytes.

I have another SETI result due in 35 minutes and have upped the size limit to 2GB and updated the project in hopes that the next result will not get deleted. Any other suggestions as to why this error occured?

---

---
<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=875&amp;trans=off" />
Everything is just <A HREF="http://heim.ifi.uio.no/~stanisls/fysisk/">A Question of Physics</A>

To make sure result-files isn't becoming very huge, both making it expensive and time-consuming to upload, but also for the project to save the results and to guard against users trying to fill-up the result-directory with uploading garbage, there are limits on each wu how big the result-file can become, and BOINC refuses to upload if passed the limit.

For SETI@home, this limit is 65536 bytes, and should normally never be passed since the seti-application should stop crunching when nearing 32768 bytes and instead terminate with -9 result_overflow.


Seeing how many errors you've managed to produce already, would recommend to run some tests like prime95 and memtest86+. If overclocking, revert to normal clock.

Thank you for the explanation.

- No overclocking.
- Not a single faulty result on Predictor and Einstein

I had a power outage in the house while this result was in computation, this might be the cause. I had to ask to make sure that the problem was not with the user-level settings.

...

The next result has just been returned with success status, so I thinkg it was the power outage that destroyed the previous result.

---

---
<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=875&amp;trans=off" />
Everything is just <A HREF="http://heim.ifi.uio.no/~stanisls/fysisk/">A Question of Physics</A>