Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 119
Posts: 119   Pages: 12   [ Previous Page | 3 4 5 6 7 8 9 10 11 12 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 13099 times and has 118 replies Next Thread
GIBA
Ace Cruncher
Joined: Apr 25, 2005
Post Count: 5374
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

These were not late, they were PV, with wingman "Waiting to be sent"


agree.
----------------------------------------
Cheers ! GIB@ peace coffee
Join BRASIL - BRAZIL@GRID team and be very happy !
http://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=DF99KT5DN1

[Nov 4, 2010 8:36:19 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

Let me explain... An incomplete quorum Pending Validation result can't pass through the validator. What the techs do is kick them into a Too Late state, though they aren't. This allows, similar to the ''Error'' results, to run a script to allocate the credit without there being quorum.

Capice... Yes/No?

Note that standard BOINC policy is that Error/Too Late are worth squad in credit, so the techs devised a scheme around that and grant credit for time/results/points.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Nov 4, 2010 9:09:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
GIBA
Ace Cruncher
Joined: Apr 25, 2005
Post Count: 5374
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

Ok Sekerob, I understood your coment since you posted, but agree with Fredski that not appear be right due exactly by the explanation posted by him.

Maybe, due the many situations faced by all of us that we saw this year (just to take a sample), with WU's in Beta's and in production releases distributed, WCG tech team could use a new status term that allow all, at a glance, to know that any specific WU returned will have a special treatment (due a sort of problems...).

I don't have idea what could be the best term to define this new term status suggested. Today I saw that "other" status was used to define cancelled WU's which wasn't distributed, after the issue identified in this DDDT2 wave.

Just an idea. Thank you anyway.
----------------------------------------
Cheers ! GIB@ peace coffee
Join BRASIL - BRAZIL@GRID team and be very happy !
http://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=DF99KT5DN1

[Nov 4, 2010 9:23:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

After another look, I see that the few I had, have been given credit.
[Nov 4, 2010 9:28:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
cw64
Advanced Cruncher
Joined: Oct 6, 2007
Post Count: 120
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

Let me explain... An incomplete quorum Pending Validation result can't pass through the validator. What the techs do is kick them into a Too Late state, though they aren't. This allows, similar to the ''Error'' results, to run a script to allocate the credit without there being quorum.

Capice... Yes/No?

Note that standard BOINC policy is that Error/Too Late are worth squad in credit, so the techs devised a scheme around that and grant credit for time/results/points.


What about the actual result? Does it get trashed?
----------------------------------------

[Nov 18, 2010 1:10:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JSYKES
Senior Cruncher
Joined: Apr 28, 2007
Post Count: 200
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

DDDT2 units seem to be rare commodities at the moment - and then you get one - another potential hour or two to the total and another WU processed - excellent - and then after an hour it errors-out...... Looking at the unit log, all three instances issued have run to error - and there are two more lined up for issue but appear to be being held.....why are two more lined up for issue?? If it has run to error 3 times - isn't that enough evidence that it is a bad unit, why waste more time??

ts05_a148_sqa007

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
Bad LAMBDA value
Encountered error. Exiting.
----------------------------------------

[Dec 4, 2010 9:30:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
BladeD
Ace Cruncher
USA
Joined: Nov 17, 2004
Post Count: 28976
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

After another look, I see that the few I had, have been given credit.

Me too! laughing
----------------------------------------
[Dec 5, 2010 7:46:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

Summing it up on 36 received for this Dec.2, 2010 run:

ts01/ts02 - 100% valid or pv (24 total)
ts05 - 25% valid (3 of 12), 4 outright error, 5 aborted by user (moi) based on result error by wingman

Those that need wingman, with clean logs, to include ts05!:

ts05_ a313_ pla007_ 0-- 1292373 Pending Validation 3-12-10 03:24:15 5-12-10 13:31:39 4.68 84.8 / 0.0
ts02_ a176_ se0000_ 0-- 1292373 Pending Validation 2-12-10 23:38:20 4-12-10 19:52:49 4.84 88.2 / 0.0
ts01_ c296_ se0000_ 1-- 1292373 Pending Validation 2-12-10 22:12:30 3-12-10 17:02:33 4.92 89.7 / 0.0
ts01_ c297_ se0000_ 0-- 1292373 Pending Validation 2-12-10 22:12:30 3-12-10 14:42:54 4.84 88.2 / 0.0
ts01_ b390_ se0000_ 1-- 95711 Pending Validation 2-12-10 21:36:57 5-12-10 00:40:51 6.90 69.2 / 0.0
ts01_ b249_ se0000_ 1-- 1292373 Pending Validation 2-12-10 21:10:45 3-12-10 12:14:30 4.83 88.1 / 0.0
ts01_ b206_ se0000_ 0-- 95711 Pending Validation 2-12-10 21:06:33 3-12-10 15:01:42 6.85 68.7 / 0.0

One thing was consistent: If there was a fail, it was same for both copies, and always right at point of completion.

--//--
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Dec 5, 2010 2:33:18 PM]   Link   Report threatening or abusive post: please login first  Go to top 
nanoprobe
Master Cruncher
Classified
Joined: Aug 29, 2008
Post Count: 2998
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures


One thing was consistent: If there was a fail, it was same for both copies, and always right at point of completion.

I had many that failed right at the start and not at point of completion, like the one below. sad


Result Name App Version Number Status Sent Time Time Due /
Return Time CPU Time (hours) Claimed/ Granted BOINC Credit
ts05_ a320_ pcb008_ 2-- 617 Error 12/3/10 03:28:36 12/3/10 16:47:50 0.00 0.0 / 0.0
ts05_ a320_ pcb008_ 1-- 617 Error 12/3/10 03:07:06 12/3/10 12:22:34 0.00 0.0 / 0.0
ts05_ a320_ pcb008_ 0-- 617 Error 12/3/10 03:06:46 12/3/10 03:20:57 0.00 0.0 / 0.0
ts05_ a320_ pcb008_ 3-- - Waiting to be sent — — 0.00 0.0 / 0.0
ts05_ a320_ pcb008_ 4-- - Waiting to be sent — — 0.00 0.0 / 0.0
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.


[Dec 5, 2010 9:15:37 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Hypernova
Master Cruncher
Audaces Fortuna Juvat ! Vaud - Switzerland
Joined: Dec 16, 2008
Post Count: 1908
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Wu Failures

It is frustrating when you get so little of this project, that is three or four WU's once in a month and then half of them errors out.

Two last examples. One from Saturn device:

Result Name: ts05_ a141_ pr34b0_ 1--

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
riture impossible sur le piphique spifi (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
INFO: No state to restore. Start from the beginning.
Encountered error. Exiting.

</stderr_txt>
]]>


and from Pluto device:

Result Name: ts05_ a146_ pqa009_ 1--

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
riture impossible sur le piphique spifi (0x1d) - exit code 29 (0x1d)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
Encountered error. Exiting.

</stderr_txt>
]]>


One is IP at the moment and the other one has Validated.
If anybody has an idea what these errors mean. My understanding is that one phrase is in french but the text is truncated and would mean:

riture impossible sur le piphique spifi


Correction:
"Ecriture impossible sur le périphérique specifié"

Translation in English:
"Writing impossible on the specified peripheral."

So any ideas? sad
----------------------------------------

----------------------------------------
[Edit 2 times, last edit by Hypernova at Dec 6, 2010 7:18:56 AM]
[Dec 6, 2010 7:17:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 119   Pages: 12   [ Previous Page | 3 4 5 6 7 8 9 10 11 12 | Next Page ]
[ Jump to Last Post ]
Post new Thread