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: 38
Posts: 38   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 246549 times and has 37 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: DDDT2 Type C -- Possible bad batches

It looks like the Server Aborts have begun:


Project Name: Discovering Dengue Drugs - Together - Phase 2
Created: 4/10/10
Name: ts06_b007_pr23b0
Minimum Quorum: 2
Replication: 2



Result Name App Version Number Status Sent Time Time Due /
Return Time CPU Time (hours) Claimed/ Granted BOINC Credit
ts06_ b007_ pr23b0_ 6-- 617 Server Aborted 4/12/10 07:59:27 4/12/10 10:31:35 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 5-- 617 Error 4/12/10 07:48:20 4/12/10 09:03:54 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 4-- 617 Error 4/12/10 03:58:14 4/12/10 07:59:21 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 3-- 617 Error 4/11/10 14:43:49 4/12/10 03:52:20 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 2-- 617 Error 4/10/10 17:23:33 4/11/10 14:43:44 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 1-- 617 Error 4/10/10 16:35:56 4/10/10 17:23:26 0.00 0.0 / 0.0
ts06_ b007_ pr23b0_ 0-- 617 Error 4/10/10 16:35:55 4/12/10 07:43:08 0.00 0.0 / 0.0
[Apr 12, 2010 1:50:08 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 Type C -- Possible bad batches

No, this is the "normal" server abort, after 5 or 6 returned errors. This already happened yesterday for some wu's:
ts06_ b012_ pr23a1_ 6--  617 Error  11.04.10 09:26:51 11.04.10 19:44:52  0.00 0.0 / 0.0 
ts06_ b012_ pr23a1_ 5-- 617 Server Aborted 11.04.10 06:38:39 11.04.10 22:52:01 0.00 0.0 / 0.0
ts06_ b012_ pr23a1_ 4-- 617 Error 10.04.10 23:59:05 11.04.10 09:26:51 0.00 0.0 / 0.0
ts06_ b012_ pr23a1_ 3-- 617 Error 10.04.10 17:35:29 11.04.10 06:26:04 0.00 0.0 / 0.0
ts06_ b012_ pr23a1_ 2-- 617 Error 10.04.10 16:49:40 10.04.10 23:59:02 0.00 0.0 / 0.0
ts06_ b012_ pr23a1_ 1-- 617 Error 10.04.10 16:40:35 10.04.10 17:35:26 0.00 0.0 / 0.0
ts06_ b012_ pr23a1_ 0-- 617 Error 10.04.10 16:40:34 10.04.10 16:43:21 0.00 0.0 / 0.0

And I still receive replication copies of wu's of this specific batch... sad
[Apr 12, 2010 2:28:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Type C -- Possible bad batches

MacDitch, remember to use the update command after you run a few other tasks, to report completed tasks. Not that I would expect a series of successive downpours any time soon; given so many task failures.
[Apr 12, 2010 6:51:48 PM]   Link   Report threatening or abusive post: please login first  Go to top 
gb009761
Master Cruncher
Scotland
Joined: Apr 6, 2005
Post Count: 2982
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Type C -- Possible bad batches

And still these toxic 'ts06_*_pr*' jobs are filtering through.

I've just picked up a 'retread' that (hopefully), I'm going to keep 'Ready to start' until it get's Server Aborted...
----------------------------------------

[Apr 13, 2010 3:40:19 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 Type C -- Possible bad batches

Why have the errors all of these errors which include miscalculation and unable to write to disk? I have not seen this on other projects. Also, I have not gotten enough WUs to provide execution time of more than a day and a half, and yet I see others with more than 180 days.
[Apr 13, 2010 5:24:38 PM]   Link   Report threatening or abusive post: please login first  Go to top 
pramo
Veteran Cruncher
USA
Joined: Dec 14, 2005
Post Count: 704
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Type C -- Possible bad batches

4/13/2010 5:46:09 PM World Community Grid Starting ts06_a007_pr67b1_3
4/13/2010 5:46:09 PM World Community Grid Starting task ts06_a007_pr67b1_3 using dddt2 version 617

4/13/2010 7:04:48 PM World Community Grid Computation for task ts06_a007_pr67b1_3 finished
4/13/2010 7:04:48 PM World Community Grid Output file ts06_a007_pr67b1_3_0 for task ts06_a007_pr67b1_3 absent
4/13/2010 7:04:48 PM World Community Grid Output file ts06_a007_pr67b1_3_1 for task ts06_a007_pr67b1_3 absent
Computation error and Windows error message that's been posted before
----------------------------------------

[Apr 13, 2010 11:10:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
gb009761
Master Cruncher
Scotland
Joined: Apr 6, 2005
Post Count: 2982
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT2 Type C -- Possible bad batches

Well, I've just picked up and returned yet another toxic ts06_*_pr* wu (I hope that by returning 2 in the last 24 hrs - albeit, with 4 valid inbetween, doesn't negatively affect my computers reliability). I'd like to be in the running for the forthcoming Type "A" shower...

One thing that I did notice, was that these fails cause havoc with the computers processing - in that until the box with the error message "wcg_dddt2_charmm_6.17_windows_intelx86 has encountered a problem and needs to close. We are sorry for the inconvenience." is physically closed, 1 core is taken out of circulation...

Thus, people who are running these toxic WU's remotely, may have all their cores taken out of use due to this error...
----------------------------------------

[Apr 14, 2010 3:34:32 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 Type C -- Possible bad batches

Can't say I share that experience. The 3 or 4 pr that passed by here of the last ts test all cleared by themselves, but yes, if having encountered this, only run DDDT2 on directly accessible machines and for those lucky, use BOINCTasks as it will color hung, slow tasks red at a specifiable percent.

As for the 'reliable'', well there's an FAQ how to know if out or in. A solidly running device has no issue to get back in real quick.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Apr 14, 2010 3:44:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 38   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread