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: 13
Posts: 13   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 3075 times and has 12 replies Next Thread
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Possible Bad Type B WU: ts01_a047_pe0000

This WU errored out 19 minutes into the run. It was resent out 2 more times and errored out again. It is currently in-process with the 3rd replacement wingmen and my original wingman.
<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x008E848A read attempt to address 0x460907DC
(plus more)

Would the server keep resending forever if it keeps erroring out?

Cheers coffee
----------------------------------------

[Apr 9, 2010 2:48:20 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: Possible Bad Type B WU: ts01_a047_pe0000

No, after about 5 to 6 errors, the workunit will be canceled. Sometimes, also these units get server aborted.
[Apr 9, 2010 2:55:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
PinQuin
Advanced Cruncher
Germany
Joined: Dec 3, 2009
Post Count: 55
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
confused Possible Bad Type B WU: ts01_a477_pe0000

https://secure.worldcommunitygrid.org/ms/devi...s.do?workunitId=140632118

Same failure at different (Linux?)clients:
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)
</message>
<stderr_txt>
Calling gridPlatform.init()
INFO: No state to restore. Start from the beginning.
Calling gridPlatform.init()
At line 595 of file dynio.f
Fortran runtime error: End of file

</stderr_txt>
]]>



Kind regards,
Pin
----------------------------------------
----------------------------------------
[Edit 2 times, last edit by PinQuin at Apr 10, 2010 10:13:20 AM]
[Apr 10, 2010 7:11:02 AM]   Link   Report threatening or abusive post: please login first  Go to top 
roundup
Veteran Cruncher
Switzerland
Joined: Jul 25, 2006
Post Count: 834
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Possible Bad Type B WU: ts01_a047_pe0000

There are some more of possibly bad units around:
ts01_ c290_ pe0000_ 0-- Error
ts01_ b192_ pe0000_ 0-- Error

The logs look like this:
>>

<core_client_version>6.6.36</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x008E848A read attempt to address 0x19A08068

Engaging BOINC Windows Runtime Debugger...
<<
[Apr 10, 2010 7:36:47 AM]   Link   Report threatening or abusive post: please login first  Go to top 
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Re: Possible Bad Type B WU: ts01_a047_pe0000

Another to add to the list: ts01_ c183_ pe0000

Win 7 64 bit C2D Quad. Normally runs error free errored out 5.4 hrs into WU.

Result Log:
-----------
Result Name: ts01_ c183_ pe0000_ 0--

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x008E848A read attempt to address 0x2423367C

Engaging BOINC Windows Runtime Debugger...

The initial wingman now shows same error and two repair jobs in progress:
ts01_ c183_ pe0000_ 3-- - In Progress 4/10/10 06:59:14 4/13/10 02:11:14 0.00 0.0 / 0.0
ts01_ c183_ pe0000_ 2-- - In Progress 4/9/10 20:58:53 4/12/10 16:10:53 0.00 0.0 / 0.0
ts01_ c183_ pe0000_ 0-- 617 Error 4/9/10 08:35:14 4/9/10 20:58:48 5.40 101.9 / 0.0 <-------Mine
ts01_ c183_ pe0000_ 1-- 617 Error 4/9/10 08:35:13 4/10/10 06:59:12 4.75 131.8 / 0.0
----------------------------------------
Bill P

[Apr 10, 2010 8:46:08 AM]   Link   Report threatening or abusive post: please login first  Go to top 
widdershins
Veteran Cruncher
Scotland
Joined: Apr 30, 2007
Post Count: 674
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Possible Bad Type B WU: ts01_a047_pe0000

Add ts01_ c282_ pe0000_ 0-- to the list.

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
process exited with code 29 (0x1d, -227)
</message>
<stderr_txt>
Calling gridPlatform.init()
INFO: No state to restore. Start from the beginning.
CHARGE OUTSIDE INNER GSBP REGION
Encountered error. Exiting.

</stderr_txt>
]]>

Two wingmen errored out also with same message, two resends still out there.
[Apr 10, 2010 9:00:01 AM]   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: Possible Bad Type B WU: ts01_a047_pe0000

Project Name: Discovering Dengue Drugs - Together - Phase 2
Created: 09/04/10
Name: ts01_b252_pe0000
Minimum Quorum: 2
Replication: 2



Result Name App Version Number Status Sent Time Time Due /
Return Time CPU Time (hours) Claimed/ Granted BOINC Credit
ts01_ b252_ pe0000_ 5-- - In Progress 12/04/10 15:53:16 15/04/10 11:05:16 0.00 0.0 / 0.0
ts01_ b252_ pe0000_ 4-- 617 Error 12/04/10 02:31:49 12/04/10 15:53:02 10.90 138.8 / 0.0
ts01_ b252_ pe0000_ 3-- 617 Pending Validation 10/04/10 15:33:49 11/04/10 03:55:19 7.29 164.5 / 0.0
ts01_ b252_ pe0000_ 2-- 617 Error 10/04/10 03:04:25 10/04/10 15:32:42 5.15 110.6 / 0.0
ts01_ b252_ pe0000_ 1-- 617 Error 09/04/10 06:16:01 10/04/10 01:55:22 7.05 145.8 / 0.0
ts01_ b252_ pe0000_ 0-- 617 Error 09/04/10 06:15:59 12/04/10 01:05:36 12.56 200.4 / 0.0

Just picked up the above,would like some advice please to crunch or not.
First reaction is to abort rather than waste 6/10 hours on it
The error=<core_client_version>6.6.38</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.
CHARGE OUTSIDE INNER GSBP REGION
Encountered error. Exiting.
Thanks
Chris
----------------------------------------
[Edit 1 times, last edit by Former Member at Apr 12, 2010 4:32:46 PM]
[Apr 12, 2010 4:29:15 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: Possible Bad Type B WU: ts01_a047_pe0000

Well, one of the WU's has gone into PV status... what's the other error messages saying????
----------------------------------------

[Apr 12, 2010 4:32:25 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: Possible Bad Type B WU: ts01_a047_pe0000

Hi thanks for the reply gb
the error
<core_client_version>6.6.38</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.
CHARGE OUTSIDE INNER GSBP REGION
Encountered error. Exiting.

My guess is that the one pass is a linux box the failures windows and i''m using windows
Tough call ,abort and it will pass to another,but when it errors I believe another copy will still be sent out>
Chris
[Apr 12, 2010 4:43:01 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: Possible Bad Type B WU: ts01_a047_pe0000

My guess is that the one pass is a linux box the failures windows and i''m using windows

This is not possible. All replication copies of a wu go always to the same OS. The descission is made with the very first distribution of a wu. If it is snagged by a linux box, also all other replication will be sent to linux only. Same with Windows and Mac OS.
[Apr 12, 2010 4:47:26 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 13   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread