Thanks Josef for that Explanation of a Validate Error. [ I think 'the server borked the result' is a good explanation, as it means nothing to fix on this end :D ]

@msattler
LOL, none of the crappy hardware I've owned would be considered overclockable at all (well maybe the CPUs), let alone 43%...
[Your description of the hazards of OCing sounds a bit like the warning I gave my mum when I upgraded her worn out p3 with a C2D, 'You'd better be careful mum! You can now muck things up about 50 times faster', but with a couple of naughtier words than that]

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Well, What I was also getting at is that, I remember seeing a post that there IS the occasional validate error no matter what with those CPU's, and that this will be fixed( or improved ) in an upcoming release of a new optimised application, along with the 'stuttering' that occurs with 2.2B apps, but only Simon or Josef can clarify that ( I can't find that post now, I may have read it wrong :S)

Those were failed validations, not validation errors per se. The former happens when a result is insufficiently similar to the others in the quorum; this can be due to very slight differences in the way the calculations are performed. Such results show an outcome of “Success” but aren’t granted any credit. The latter (the ostensible subject of this thread) originate server-side, usually caused by the validator being unable to find the result files it’s been asked to compare. Their outcome is shown as “Validate error”.

---

Something's not happy in SETI-land: have a look at this one.

seti@home 24/05/2007 21:09:19 Started upload of 27fe05aa.6988.31074.467332.3.165_2_0
seti@home 24/05/2007 21:09:24 Finished upload of 27fe05aa.6988.31074.467332.3.165_2_0
seti@home 24/05/2007 21:09:24 Throughput 11664 bytes/sec
seti@home 24/05/2007 21:09:29 Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
seti@home 24/05/2007 21:09:29 Reason: To report results
seti@home 24/05/2007 21:09:29 Reporting 1 results
seti@home 24/05/2007 21:09:34 Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Yet WU 130113129 shows:

537159502 3194562 22 May 2007 10:16:22 UTC 12 Jun 2007 17:58:40 UTC In Progress Unknown New --- --- ---
537159503 3145695 21 May 2007 23:09:44 UTC 22 May 2007 11:04:10 UTC Over Success Done 26,169.06 57.07 pending
537159504 1791152 22 May 2007 10:16:52 UTC 24 May 2007 21:09:29 UTC Over Validate error Done 12,255.28 --- ---
539564506 --- --- --- Unsent Unknown New --- --- ---

Have they added a delay in storing uploads, to defeat RRI? ;-)
(which I use unashamedly on this elderly, low-resource-share box)

Edit - this happened at a time when there were 37,120 workunits waiting for validation, according to the status page - why did mine attempt validation in the first second?

Those were failed validations, not validation errors per se. The former happens when a result is insufficiently similar to the others in the quorum; this can be due to very slight differences in the way the calculations are performed. Such results show an outcome of “Success” but aren’t granted any credit. The latter (the ostensible subject of this thread) originate server-side, usually caused by the validator being unable to find the result files it’s been asked to compare. Their outcome is shown as “Validate error”.

Thanks Odysseus, for clearing that up :D , I guess from the user's standpoint either condition is just as frustrating ( no credit for work done )

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

validate error for resultid 539168056

Since most are putting the wu info
WU 130736790

If this is just a result being not similar enough and not a "validate error", please enlighten me :)

http://setiathome.berkeley.edu/workunit.php?wuid=129454188

http://setiathome.berkeley.edu/workunit.php?wuid=129453491

http://setiathome.berkeley.edu/workunit.php?wuid=129452983




Thanx for answers!

---

http://setiathome.berkeley.edu/workunit.php?wuid=131099383

http://setiathome.berkeley.edu/workunit.php?wuid=131163073



I have sometimes:
Giving up on upload of ####################: server rejected file
And then it's a 'validate error'.
This is a server prob., or? When it's possible to fix this?

And when are the normally 'validate error' fixed?

---

http://setiathome.berkeley.edu/workunit.php?wuid=128723324

---

http://setiathome.berkeley.edu/workunit.php?wuid=128987572
[/quote]
http://setiathome.berkeley.edu/workunit.php?wuid=128983955
[/quote]
http://setiathome.berkeley.edu/workunit.php?wuid=128983931
[/quote]
http://setiathome.berkeley.edu/workunit.php?wuid=128979560
[/quote]
http://setiathome.berkeley.edu/workunit.php?wuid=128994832
[/quote]
http://setiathome.berkeley.edu/workunit.php?wuid=129000695
[/quote]

---

Official Abuser of Boinc Buttons...
And no good credit hound!

http://setiathome.berkeley.edu/workunit.php?wuid=131053431

---

http://setiathome.berkeley.edu/workunit.php?wuid=129043358

---

http://setiathome.berkeley.edu/workunit.php?wuid=131438553

---

I'm begining to feel that there should be a limit to the size of the signatures.

---

Grant
Darwin NT

I'm begining to feel that there should be a limit to the size of the signatures.

Wrong thread!

---

http://setiathome.berkeley.edu/workunit.php?wuid=131609673

---

http://setiathome.berkeley.edu/workunit.php?wuid=131587025

---

I'm begining to feel that there should be a limit to the size of the signatures.

Wrong thread!

Thank you for proving my point.

---

Grant
Darwin NT

Especially when posting it 3 times in a row. But he's a good dude. Just trying to figure out his OC.
But the sig could be a bit smaller.

---

"Time is simply the mechanism that keeps everything from happening all at once."

WU 132347036

It should be noted that prior to the outage / replacement / server-side code change, this system almost never had this happen. I say "almost never" because I can't be 100% sure that it never happened, but that being said, I never saw it happen...

@ Grant (SSSF)

Reduced my sig! :-)
O.K. now?


@ msattler

Thanks for compliment! :-)



BUT now, one more 'invalid result' :-(

http://setiathome.berkeley.edu/workunit.php?wuid=132340888

---