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: 18
Posts: 18   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3472 times and has 17 replies Next Thread
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

Regression to some forgotton rule? Think to have seen cases of the deadline being computed on the reissued result i.e. 3 days becomes at 33% 1 day, becomes at 33%, 8 hours, but that's been a while ago when the first reissue was still at 20%. And there is this xxx margin granted based on device history.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Apr 17, 2009 11:06:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
TBirdTheYuri
Advanced Cruncher
France
Joined: Mar 5, 2006
Post Count: 115
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

I have this for the "Too late" Beta Unit:

INFO: No state to restore. Start from the beginning. No heartbeat from core client for 30 sec - exiting called boinc_finish

[Apr 17, 2009 11:36:59 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

Sek,
It's what I am thinking of. That's why I would like to see if the timing of this WU allows to consider this flaw or if we have to look for something else.
It will have to be the repair of a repair of a repair!

Cheers. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Apr 17, 2009 11:40:28 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

TBird' it's not this info I would like to see, it is what you see when you click on the name of the WU.

Cheers. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Apr 17, 2009 11:43:48 AM]   Link   Report threatening or abusive post: please login first  Go to top 
TBirdTheYuri
Advanced Cruncher
France
Joined: Mar 5, 2006
Post Count: 115
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
smile Re: Delay to send Beta Units too short

Sorry.
If I click on name of this unit I have on screen a list of replicated units (See below) :


Nom du projet: Beta
Créé le :: 15/04/09
Nom: BETA_CMD2_0001-MOL2AA.clustersOccur-PRDX6.clustersOccur_0
Quorum minimum: 2
Réplication initiale: 3

And my unit :
BETA_ CMD2_ 0001-MOL2AA.clustersOccur-PRDX6.clustersOccur_ 0_ 4-- Trop tard 16/04/09 02:23:05 16/04/09 13:25:22 10,59 177,3 / 0,0


(I'im french : "Trop tard" = "Too late"). Times are UTC
[Apr 17, 2009 12:14:26 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

I'im french

Parfait, moi aussi! smile
Ce qu'on voudrait voir c'est toutes les lignes de toutes les copies (pas seulement la tienne) afin de vérifier si c'est l'enchaînement des envois qui explique ton délai top court.
Même si les techs peuvent voir ce détail (mais pas nous les CAs ni les autres lecteurs du forum), une fois que cette WU aura été purgée de la database le détail pourra ainsi toujours être vu ici.
_____________________
Fine, me too. smile
What we want to see is all the lines of all copies (not only yours) in order to check if it is the distribution timing which explains your too short deadline.
Even if the techs can see these details (but neither us CAs nor the other readers of the forum), once this WU will have been purged from the database the detail will still be visible here.
_____________________

Merci d'avance pour ton aide. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Apr 17, 2009 1:25:20 PM]   Link   Report threatening or abusive post: please login first  Go to top 
TBirdTheYuri
Advanced Cruncher
France
Joined: Mar 5, 2006
Post Count: 115
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
smile Re: Delay to send Beta Units too short

LOL. C'est la première fois que je trouve un Français ici, je ne le savais pas, ils sont si rares dans le coin que je ne prend même pas le temps de vérifier tongue

Alors l'enchaînement est le suivant :
Envoi / Retour / temps CPU / Etat
16/04/09 13:27:54 / 17/04/09 06:10:09 / 16,66 / Erreur
16/04/09 02:23:05 / 16/04/09 13:25:22 / 10,59 / Trop tard
15/04/09 22:36:45 / 16/04/09 13:10:23 / 14,26 / Erreur
15/04/09 15:38:07 / 16/04/09 02:23:00 / 7,90 / Erreur
15/04/09 15:38:01 / 15/04/09 22:35:18 / 0,95 / Aborted
15/04/09 15:37:56 / 16/04/09 13:38:50 / 10,32 / Erreur
[Apr 17, 2009 2:26:40 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Delay to send Beta Units too short

Il est vrai que je n'ai pas souvent l'occasion de poster en français en dehors du fil de l'équipe, mais je porte mon "certificat d'origine" depuis le début. smile

Back to your case now.
Copy / Envoi  / Retour / temps CPU / Etat
_5 / 16/04/09 13:27:54 / 17/04/09 06:10:09 / 16,66 / Erreur
_4 / 16/04/09 02:23:05 / 16/04/09 13:25:22 / 10,59 / Trop tard
_3 / 15/04/09 22:36:45 / 16/04/09 13:10:23 / 14,26 / Erreur
_2 / 15/04/09 15:38:07 / 16/04/09 02:23:00 / 7,90 / Erreur
_1 / 15/04/09 15:38:01 / 15/04/09 22:35:18 / 0,95 / Aborted
_0 / 15/04/09 15:37:56 / 16/04/09 13:38:50 / 10,32 / Erreur
It seems that your copy (4) follows the Error of copy 2 which is an initial distribution, therefore a cascade of repair WUs is not the right explanation. We will definitely need to catch the attention of some tech to this case.
Copy 3 follows the abortion of copy 1.
And copy 5 seems to follow yours, which is even stranger.

Thanks for your reporting. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Apr 17, 2009 3:48:46 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 18   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread