Just Reported 7 wu's got credit for 4 and three had this same message any one got any ideas???

Task ID 12752348
Name ps_s21_10_1598_1235787177_0
Workunit 12443549
Created 28 Feb 2009 2:12:59 UTC
Sent 28 Feb 2009 2:14:03 UTC
Received 28 Feb 2009 10:02:35 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 21898
Report deadline 3 Mar 2009 2:14:03 UTC
CPU time 1450.188
stderr out <core_client_version>6.4.6</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz (2 cores/threads) 1.66677 GHz (477ms)

WU completed. It took 1450.19 seconds CPU time and 1471.34 seconds wall clock time @ 1.66678 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 4.00614209266257
Granted credit 0
application version 0.19

---

Insta-purge makes it difficult to catch zero results.. but I saw at least one as well:

Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 29070
Report deadline 3 Mar 2009 9:26:42 UTC
CPU time 403.2314
stderr out

<core_client_version>6.6.10</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 cores/threads) 2.39993 GHz (468ms)

WU completed. It took 403.231 seconds CPU time and 403.905 seconds wall clock time @ 2.39996 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 1.75290696144102
Granted credit 0

---

Lovely greetings, Cori

Just had one myself

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=12666556

stderr out <core_client_version>6.6.11</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz (4 cores/threads) 2.86366 GHz (450ms)

WU completed. It took 441.313 seconds CPU time and 465.731 seconds wall clock time @ 2.86368 GHz.

</stderr_txt>
]]>
Validate state Invalid
Claimed credit 2.26277234252794
Granted credit 0
application version 0.19

Gday cori,
Maybe Travis when he's back on deck might shed some light on whether it's a problem or not.....

---

Gday cori,
Maybe Travis when he's back on deck might shed some light on whether it's a problem or not.....

Hi Glenn,
I hope so, too! ;-)))


EDIT:
Got the next one...

Task ID 12985902
Name ps_s79_10_163287_1235813123_0
Workunit 12673666
Created 28 Feb 2009 9:25:28 UTC
Sent 28 Feb 2009 9:26:42 UTC
Received 28 Feb 2009 10:21:55 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 29070
Report deadline 3 Mar 2009 9:26:42 UTC
CPU time 402.9662
stderr out

<core_client_version>6.6.10</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 cores/threads) 2.39992 GHz (466ms)

WU completed. It took 402.966 seconds CPU time and 403.544 seconds wall clock time @ 2.39996 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 1.75175409753663
Granted credit 0
application version 0.19

---

Lovely greetings, Cori

Gday cori,
Maybe Travis when he's back on deck might shed some light on whether it's a problem or not.....

Hi Glenn,
I hope so, too! ;-)))


EDIT:
Got the next one...

Task ID 12985902
Name ps_s79_10_163287_1235813123_0
Workunit 12673666
Created 28 Feb 2009 9:25:28 UTC
Sent 28 Feb 2009 9:26:42 UTC
Received 28 Feb 2009 10:21:55 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 29070
Report deadline 3 Mar 2009 9:26:42 UTC
CPU time 402.9662
stderr out

<core_client_version>6.6.10</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 cores/threads) 2.39992 GHz (466ms)

WU completed. It took 402.966 seconds CPU time and 403.544 seconds wall clock time @ 2.39996 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 1.75175409753663
Granted credit 0
application version 0.19

EDIT2:
And another one, grrrr.... ;-(
Couldn't catch the stderr anymore but it must have been similar.
Also I am noticing I'm getting these "Zeros" on all my comps now.
Not every WU fails but it seems the failures are getting worse.

---

Lovely greetings, Cori

Its only just started to happen in the last 3-4hrs but the last wu i managed to get a look it validated no problem?? So who knows maybe its because I use my lappy at the same time bionic is running...

---

WHY? IMHO, new code of assimilator/validator.

I've been debugging the new code for the assimilator/validator which lets us do some validation of workunits to keep our searches from getting screwed up by invalid results. This has caused the server to crash quite a few times this evening, so that might be causing a lot of the lack of work.

http://milkyway.cs.rpi.edu/milkyway/forum_reply.php?thread=669&post=13221#13221

Ahhh..... could be thats the problem...Just got 10 new tasks so work isnt an issue. Hopefully you can get on top of the problem good luck better you than me...:))

---

WHY? IMHO, new code of assimilator/validator...

Hm, but does that explain why the same type of WU (for example s79) is successful one time and fails the next time (maybe even on the same computer)?

Anyway I'll better set MW to NNW for a while now. ;-)

---

Lovely greetings, Cori

Already did that.. have to see how this plays out..

It seems the scheduler is working report 2 get 2 new things are looking up:))

---

I've been getting the Invalid Results across my Pharm too since I don't know when ??? Haven't been paying much attention until I read this Thread ...

I've seen some too. How many I can't say.

---

Calm Chaos Forum...Join Calm Chaos Now

Although I only started crunching yesterday, it seems approximately 20% of units are giving invalid results.

The latest of mine gave this output file:

13100011
Name ps_s20_10_276033_1235824656_0
Workunit 12786412
Created 28 Feb 2009 12:37:40 UTC
Sent 28 Feb 2009 12:38:39 UTC
Received 28 Feb 2009 15:22:16 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 52343
Report deadline 3 Mar 2009 12:38:39 UTC
CPU time 1025.5
stderr out
<core_client_version>6.2.18</core_client_version>
<![CDATA[
<stderr_txt>
called boinc_finish

</stderr_txt>
]]>
Validate state Invalid
Claimed credit 8.22933575814657
Granted credit 0
application version 0.18

Looks like these are the new ps_x_10 units that Travis put into work last night. This should go in that 'topic'.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

It looks like there was a problem with the outlier detection I turned on last night. It should be fixed now.

---

On my side I have not seen failed workunits during the last time.

Before I was seeing about 10% failing

Thanks for the info Travis

---

An other completed but 0 credit.

Task ID 13999811
Name ps_s22_11_90612_1235948692_0
Workunit 13656491
Created 1 Mar 2009 23:04:56 UTC
Sent 1 Mar 2009 23:06:25 UTC
Received 2 Mar 2009 1:32:16 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 42030
Report deadline 4 Mar 2009 23:06:25 UTC
CPU time 1628.188
stderr out

<core_client_version>6.1.0</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Intel(R) Pentium(R) D CPU 3.00GHz (2 cores/threads) 3.00676 GHz (744ms)

WU completed. It took 1628.19 seconds CPU time and 1635.68 seconds wall clock time @ 3.00685 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 5.83756219190251
Granted credit 0
application version 0.19

Got another invalid wu heres the output....

Task ID 21190736
Name ps_s21_12_97_1236789611_0
Workunit 20729076
Created 11 Mar 2009 16:40:16 UTC
Sent 11 Mar 2009 16:47:06 UTC
Received 12 Mar 2009 2:52:37 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 21898
Report deadline 14 Mar 2009 16:47:06 UTC
CPU time 2953.141
stderr out <core_client_version>6.4.6</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home version 0.19 by Gipsel
CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz (2 cores/threads) 1.66678 GHz (514ms)

WU completed. It took 2953.14 seconds CPU time and 3050.98 seconds wall clock time @ 1.66678 GHz.

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 7.8103524526523
Granted credit 0
application version 0.19

---