Validate errors [pls post here] [CLOSED]

Not really.

There last two GR tasks your machine reported (before you started to abort these) apparently were found valid:

248004433 105444542 18 Sep 2011 14:49:42 UTC 24 Sep 2011 13:58:05 UTC Completed and validated 33,260.54 31,957.26 225.88 337.00 Gamma-ray pulsar search #1 v0.23
248004357 105444507 18 Sep 2011 14:48:34 UTC 24 Sep 2011 13:58:05 UTC Completed and validated 33,327.46 31,983.75 226.07 337.00 Gamma-ray pulsar search #1 v0.23

So from my side it looks like the problem has vanished.

If you don't want to receive GR tasks at all anymore, I suggest you opt out of that application in your Einstein@home preferences, instead of manually aborting these.

BM

I waiting few days for resolve the "validate" problem but when got new BRP4 WU's from server and successfully computed its, finally all WU's stil have this error.

249504492 106115310 27 Sep 2011 7:56:25 UTC 27 Sep 2011 10:00:40 UTC Validate error 1,783.80 649.05 4.34 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249495409 106111161 27 Sep 2011 6:34:15 UTC 27 Sep 2011 8:16:14 UTC Validate error 1,746.22 622.75 4.16 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249488553 106107986 27 Sep 2011 5:09:58 UTC 27 Sep 2011 7:02:51 UTC Validate error 1,833.17 728.42 4.87 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249484737 106106347 27 Sep 2011 4:17:01 UTC 27 Sep 2011 6:05:55 UTC Validate error 1,775.58 661.53 4.42 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249482997 106105578 27 Sep 2011 3:52:38 UTC 27 Sep 2011 6:05:55 UTC Validate error 1,817.39 707.73 4.73 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249481597 106104975 27 Sep 2011 3:29:33 UTC 27 Sep 2011 5:09:58 UTC Validate error 1,833.42 727.00 4.86 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249477127 106102851 27 Sep 2011 3:01:01 UTC 27 Sep 2011 4:43:22 UTC Validate error 1,825.09 717.50 4.79 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249474629 106101686 27 Sep 2011 2:33:13 UTC 27 Sep 2011 4:16:58 UTC Validate error 1,766.20 638.97 4.27 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249472709 106100857 27 Sep 2011 2:04:24 UTC 27 Sep 2011 3:29:32 UTC Validate error 1,768.61 649.44 4.34 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249470657 106099972 27 Sep 2011 1:37:33 UTC 27 Sep 2011 3:01:01 UTC Validate error 1,791.31 679.67 4.54 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249467145 105479733 27 Sep 2011 1:08:57 UTC 27 Sep 2011 2:33:09 UTC Validate error 1,844.31 738.09 4.93 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249460198 106095330 27 Sep 2011 0:24:07 UTC 27 Sep 2011 1:37:29 UTC Validate error 1,832.33 727.28 4.86 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)
249459937 106065918 27 Sep 2011 0:24:07 UTC 27 Sep 2011 1:08:57 UTC Validate error 1,753.41 605.38 4.04 --- Binary Radio Pulsar Search (Arecibo) v1.00 (BRP3cuda32)

So I must waiting for new BOINC manager ?

That depends on what you're trying to do.
The cc_config.xml file needs to be in the BOINC Data directory, not in the project directory. It's the core client configuration file, not the science application configuration file.

Then it needs to be made in plain text, not with an XML editor, as the XML used to this time is written specifically for BOINC; it's not real XML.

And then, anything to do with the upload certificates needs to be set on the project server, not on the client. So whatever it is you're trying to set with those certificates cannot be set through a cc_config.xml file. Added to that, the upload certificates are already disabled on Einstein.

That explains things. But you misread. The post I quoted there says that project admins need to add this to their config.xml file. It doesn't say anything about the cc_config.xml file.

As I said, it's not something that one can set through the client (the BOINC running on your computer), as both the upload certificates and the validator that does the validating and thus the validation errors, runs on the servers at the project. So it's something they would have to fix.

And as you can see from a post made by Oliver Bock, in the same thread, they have disabled the upload certificates already. Plus this was only a problem if you run the pre-alpha BOINC versions 6.13, not when you run 6.12s as you do.

So in short:
- Upload certificates --> project server thing. They have to fix this, not you.
- Validate errors --> project server thing. They have to fix this, not you.

You can remove the cc_config.xml file from your BOINC Data directory.
In case you ever want to learn what switches are correctly used on the cc_config.xml file, then look in this FAQ (pointing there as the BOINC domain is down at the moment).