I have a 'validate error' from 1 Feb 2008 14:51:10 UTC and to now it's not fixed..
So please can someone say, when the script is running every day?

wuid=209397711

---

I believe the cause was the purple report less than 20 seconds after the green upload completed. AFAIK, BOINC is very reliable at showing when it sends reports.

It is interesting to note that other projects do not seem to have this vexing problem... I only see it talked about here on a routine basis... Of course, in fairness, I haven't checked out ALL the projects' fora...

---

I have found these errors here as well :)
But I only get them on one of my 4 computers.
I have 2 linux that keep on doing there thing w/o erors in my lan
also a win 98se system keeps on going with out errors
it is my winxp doing 1.8 ghz. I have tryed all I could think to do and
just detatched all project from it as rosetta@home was also
getting the errors:(

It is running the factory mem 256meg i have got 2 1 gig cards coming
I'll give it another try after those are installed.
Not sure what version of boinc it was as I have uninstalled it now.

Doug

---

This dosn't have anything to do with validation errors but want to pass along that I had a power supply problem and then some software/bios problems with the same computer. There were only six work units there that had not uploaded due to the maintenance period. So there will be some "client detached" messages. But after checking the computer on the web site; don't know how there are more than the six of the client detached on work units. Unless its because I reinstalled the boinc software and the other units that had been uploaded is being also shown as "client detached" message.
If anyone knows the reason, please post it. I've done this many times in the past and this the first time this has come up. Sorry to all who has this on their work unit.

bj

---

I have found these errors here as well :)
But I only get them on one of my 4 computers.
I have 2 linux that keep on doing there thing w/o erors in my lan
also a win 98se system keeps on going with out errors
it is my winxp doing 1.8 ghz. I have tryed all I could think to do and
just detatched all project from it as rosetta@home was also
getting the errors:(

It is running the factory mem 256meg i have got 2 1 gig cards coming
I'll give it another try after those are installed.
Not sure what version of boinc it was as I have uninstalled it now.

Doug

well my debugging I have given that computer a (work) preferance setting
that way I can change the prefs it uses only.
I did rename the program files\\boinc directory then reinstall boink
still waiting for an error pkt.

---

I believe the cause was the purple report less than 20 seconds after the green upload completed. AFAIK, BOINC is very reliable at showing when it sends reports.

It is interesting to note that other projects do not seem to have this vexing problem... I only see it talked about here on a routine basis... Of course, in fairness, I haven't checked out ALL the projects' fora...

Brian, good to see you again :)

No, the validate errors seem to be a SETI only phenomenon. Something that has been cooked up special for their dedicated contributors. The guys that run the project have a difficult time with this one, and have not been able to completely fix the issues. From my understanding of the problem, it is caused by the huge amount of traffic on the servers. Best way to fix this in my opinion is for 1/2 of the SETI crunchers to leave and crunch for other projects. :)


Crunch all you want, they will make more (validation errors).

---

more here

http://setiathome.berkeley.edu/result.php?resultid=706291640
http://setiathome.berkeley.edu/result.php?resultid=706333989
http://setiathome.berkeley.edu/result.php?resultid=706377222
http://setiathome.berkeley.edu/result.php?resultid=707837629
http://setiathome.berkeley.edu/result.php?resultid=707970077


thank you les ( greenfinger )

I've got two WUs that failed with a validate error:

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

For me, that's nearly 12 hours wasted unless there is retrospective crediting.

---

I've got two WUs that failed with a validate error:

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

For me, that's nearly 12 hours wasted unless there is retrospective crediting.

I haven't seen anything to suggest that the corrective script is not still being run on a daily basis. If you don't get the credits, then let us know as it will be of interest to many.

F.

---

Here is my validate error: http://setiathome.berkeley.edu/result.php?resultid=749593643

---

Here is my validate error: http://setiathome.berkeley.edu/result.php?resultid=749593643

That's an odd one, as you partner MrBlue has -9 overflow, in fact it looks like that's all he gets, for all his results, on his computer.

I'd say you were the one that's correct and his should be the erroneous result.

Here is my validate error: http://setiathome.berkeley.edu/result.php?resultid=749593643

That's an odd one, as you partner MrBlue has -9 overflow, in fact it looks like that's all he gets, for all his results, on his computer.

I'd say you were the one that's correct and his should be the erroneous result.

Hope you are right. Thanks Winterknight.

---

Here is my validate error: http://setiathome.berkeley.edu/result.php?resultid=749593643

That's an odd one, as you partner MrBlue has -9 overflow, in fact it looks like that's all he gets, for all his results, on his computer.

I'd say you were the one that's correct and his should be the erroneous result.

Unfortunately the "Validate error" means the result file couldn't be found, though I agree the values reported to the Scheduler look good. I think it will take two more results to reach a consensus. With luck, Eric's script to fix validate errors will be able to grant credit for 749593643 after that.

                                                                Joe

SOME MORE HERE
http://setiathome.berkeley.edu/result.php?resultid=742566844
http://setiathome.berkeley.edu/result.php?resultid=740560307
http://setiathome.berkeley.edu/result.php?resultid=740284266
http://setiathome.berkeley.edu/result.php?resultid=740284254
http://setiathome.berkeley.edu/result.php?resultid=740284144
http://setiathome.berkeley.edu/result.php?resultid=740284138

thank you les ( greenfinger )

I've got two WUs that failed with a validate error:

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

For me, that's nearly 12 hours wasted unless there is retrospective crediting.

I've had six of these in total now. None of them (including those in my original post) have as yet been granted any credit.

---

And I have had six 'validate error' results in the past 24 hours. Two of them were later resolved and credit is pending, the other four remain in limbo.

Does it do any good to post WU ID numbers here?

---

I think regular readers know my take on this thread:

• 'Validate error' (and we're not talking about anything else here, like computation errors) tends only to happen if you try to "report" a result too soon after "uploading" it.
  
• 'Reporting too soon' can happen sporadically to anyone, but is endemic to BOINC v5.10.(<=13) with a connect interval of zero, or with certain third-party 'optimised' BOINC clients.
  
• The staff run a manual script once every 24 hours or so, to correct as many of these errors as they can.
  
• The script does not parse this thread looking for result ID numbers! It works directly on the underlying database at Berkeley.
  

Having said all that, why did one of my hosts (host 3150564) - only - get 14 validate errors overnight? It's running the same version of BOINC, on the same venue preference settings, as other hosts, but it's the only one with the errors.

The machine is a remote server, so I'll have to fire up the VPN and take a look. I'll let you know if I find anything interesting.

Well, I found the reason:

Lots of

[error] Error on file upload: no command

in the message log. (first occurrence 2008-02-14 23:58:24 - UTC)

Since each one is followed by

[file_xfer] Permanently failed upload of xxxxx
Giving up on upload of xxxxx: server rejected file

of course validation will fail - there's nothing to validate.

But the question remains: why did this only happen to one computer? BOINC was still running OK, and uploading results to other projects. Still, I've restarted it just to be on the safe side. Wait and see.

I think regular readers know my take on this thread:

• 'Validate error' (and we're not talking about anything else here, like computation errors) tends only to happen if you try to "report" a result too soon after "uploading" it.
  
• 'Reporting too soon' can happen sporadically to anyone, but is endemic to BOINC v5.10.(<=13) with a connect interval of zero, or with certain third-party 'optimised' BOINC clients.
  
• The staff run a manual script once every 24 hours or so, to correct as many of these errors as they can.
  
• The script does not parse this thread looking for result ID numbers! It works directly on the underlying database at Berkeley.
  

Having said all that, why did one of my hosts (host 3150564) - only - get 14 validate errors overnight? It's running the same version of BOINC, on the same venue preference settings, as other hosts, but it's the only one with the errors.

The machine is a remote server, so I'll have to fire up the VPN and take a look. I'll let you know if I find anything interesting.

I just got 5 days' of work/time wasted on validate errors. Does not feel good, that is for sure. I did report all of them on time, I think.

---

Well, I found the reason:

Lots of

[error] Error on file upload: no command

in the message log. (first occurrence 2008-02-14 23:58:24 - UTC)

Since each one is followed by

[file_xfer] Permanently failed upload of xxxxx
Giving up on upload of xxxxx: server rejected file

of course validation will fail - there's nothing to validate.

But the question remains: why did this only happen to one computer? BOINC was still running OK, and uploading results to other projects. Still, I've restarted it just to be on the safe side. Wait and see.

I'm 'happy' that I'm not the only one with this 'no command' errors..

I thought I'm something special..
And have a PC problem..


It's a stock or OCed PC?


So I think it's not a problem with the PCs, more with Berkeley..
So if, then this 'no command' errors must be fix with the script too!

---