Computation errors on Seti Enhanced

Message boards : Number crunching : Computation errors on Seti Enhanced
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 15 · 16 · 17 · 18 · 19 · 20 · 21 . . . 22 · Next

AuthorMessage
Profile Paul Mauer

Send message
Joined: 13 Apr 06
Posts: 13
Credit: 2,704,488
RAC: 0
United States
Message 343834 - Posted: 21 Jun 2006, 1:30:25 UTC

Does anyone know what this error means?

6/20/2006 6:28:26 PM|SETI@home|Unrecoverable error for result 05ap99ab.20895.16000.459664.3.0_5 (The system cannot find the path specified. (0x3) - exit code 3 (0x3))

ID: 343834 · Report as offensive
Profile Clyde C. Phillips, III

Send message
Joined: 2 Aug 00
Posts: 1851
Credit: 5,955,047
RAC: 0
United States
Message 344588 - Posted: 21 Jun 2006, 17:44:53 UTC

After about a week that was free of errors, one, a 50-minute one, popped up yesterday as a client error, compute error, cant find path, exit 0x3, invalid error. The others got credit.
ID: 344588 · Report as offensive
HFB1217
Avatar

Send message
Joined: 25 Dec 05
Posts: 102
Credit: 9,424,572
RAC: 0
United States
Message 345679 - Posted: 22 Jun 2006, 20:25:35 UTC

340936029 81669793 12 Jun 2006 12:44:08 UTC 22 Jun 2006 20:13:54 UTC Over Client error Compute error 17,719.34 58.76 ---

6/22/2006 4:13:07 PM|SETI@home|Unrecoverable error for result 21fe99ab.27562.29234.661080.3.104_0 (The system cannot find the path specified. (0x3) - exit code 3 (0x3))


C++ Error from a new WU dated 12th of June


Third one this month!!
ID: 345679 · Report as offensive
HFB1217
Avatar

Send message
Joined: 25 Dec 05
Posts: 102
Credit: 9,424,572
RAC: 0
United States
Message 345680 - Posted: 22 Jun 2006, 20:25:43 UTC

340936029 81669793 12 Jun 2006 12:44:08 UTC 22 Jun 2006 20:13:54 UTC Over Client error Compute error 17,719.34 58.76 ---

6/22/2006 4:13:07 PM|SETI@home|Unrecoverable error for result 21fe99ab.27562.29234.661080.3.104_0 (The system cannot find the path specified. (0x3) - exit code 3 (0x3))


C++ Error from a new WU dated 12th of June


Third one this month!!
ID: 345680 · Report as offensive
Domestos

Send message
Joined: 31 Dec 00
Posts: 79
Credit: 7,422,705
RAC: 0
United Kingdom
Message 346330 - Posted: 23 Jun 2006, 8:32:34 UTC
Last modified: 23 Jun 2006, 8:34:04 UTC

At first I though this was a one-off on one of my Athlon xp 3.0 ghz machines , but it is not.

It has happened again , but this time on my P4 3ghz machine ( just now )

( athlon was running one unit as they do it was harder to see )

I shall describe the P4 symptoms for both :

Got up this morning and checked on progress of the crunching and noticed one of the 2 units my P4 was working on was taking rather a long time.

Oh My !!! one of those really long turn-around times .... I thought ...

made a cup of coffee and came back to the P4 and looked more closely ...

The unit was on something like 84% but that was static , while the time USED annd the time to COMPLETION were stil counting ... realising this was what happened on one of my other PCs , I turned OFF BOINC.

Waited a moment ...then switched back on BOINC ....and the offending unit seemed to reset itself as the time USED went to 7 hours + and it continued to finish the unit as NORMAL.

I think this is the Offending Unit :

WORK UNIT 82718281
RESULT ID 345290045

( the only other returned so far today from the P4 is the following one that seems to be as interesting !!!)

WORK UNIT 82759477
RESULT ID 345458362

COMPUTER ID 2220237


Any Idea's as to why this happens ??

I mean 12 HOURS WASTED is not fun :(

Especially a second time on a completely different machine


Thanks , Chris


ID: 346330 · Report as offensive
Profile Dr. C.E.T.I.
Avatar

Send message
Joined: 29 Feb 00
Posts: 16019
Credit: 794,685
RAC: 0
United States
Message 346511 - Posted: 23 Jun 2006, 13:55:18 UTC
Last modified: 23 Jun 2006, 14:04:38 UTC

Q/ does anybody know why these 3 are 'pending' - the first units i started w/ yesterday . . . whereas all other units are credited almost immediately

< i just started up again w/ my new box and these are virtually the first three units finished . . .


pending . . .
> 18mr99ab.11394.1984.422146.3.147_2
345218148 2488176 21 Jun 2006 23:50:55 UTC 22 Jun 2006 10:08:41 UTC Over Success Done 24,806.02 67.24 pending
> 18mr99ab.11394.2032.103400.3.235_3
345221340 2488176 22 Jun 2006 0:03:08 UTC 22 Jun 2006 23:21:42 UTC Over Success Done 27,804.25 67.24 pending
> 26mr99aa.3842.16626.292318.3.143_0
345221345 2488176 22 Jun 2006 0:03:08 UTC 22 Jun 2006 14:12:59 UTC Over Success Done 16,606.95 34.26 pending

credited . . .
< 345221325 82701316 22 Jun 2006 0:03:08 UTC 23 Jun 2006 10:40:02 UTC Over Success Done 16,590.11 34.26 34.26
< 345221361 82701334 22 Jun 2006 0:03:08 UTC 23 Jun 2006 10:13:45 UTC Over Success Done 16,596.08 34.27 34.27

richard
ID: 346511 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13736
Credit: 208,696,464
RAC: 304
Australia
Message 347008 - Posted: 23 Jun 2006, 23:28:26 UTC - in response to Message 346511.  

Q/ does anybody know why these 3 are 'pending'

Only 2 results have been returned, a minimum of 3 are required before credit is granted.
Grant
Darwin NT
ID: 347008 · Report as offensive
Profile Dr. C.E.T.I.
Avatar

Send message
Joined: 29 Feb 00
Posts: 16019
Credit: 794,685
RAC: 0
United States
Message 347478 - Posted: 24 Jun 2006, 12:29:40 UTC

rcvd credit for the first unit today ;_)
this is the first time - since crunchin (Feb 29 2000) that i have received actual credit for credit 'claimed'
thankz 4 the responses all . . .
ID: 347478 · Report as offensive
Profile The MariahNet Network
Avatar

Send message
Joined: 14 Jul 99
Posts: 173
Credit: 2,469,357
RAC: 0
United States
Message 347946 - Posted: 24 Jun 2006, 23:38:06 UTC

ID: 347946 · Report as offensive
Stick Project Donor
Volunteer tester

Send message
Joined: 26 Feb 00
Posts: 100
Credit: 5,283,449
RAC: 5
United States
Message 348013 - Posted: 25 Jun 2006, 1:22:22 UTC
Last modified: 25 Jun 2006, 1:26:16 UTC

Not an error - but I think that there probably should have been one - on this result. This is the Workunit. Compare the CPU times. I don't think my computer could have really completed the WU in 1,036.57 seconds. On the second thought, maybe I should post my app on the new optimized app thread. ;-)
ID: 348013 · Report as offensive
Odysseus
Volunteer tester
Avatar

Send message
Joined: 26 Jul 99
Posts: 1808
Credit: 6,701,347
RAC: 6
Canada
Message 348099 - Posted: 25 Jun 2006, 4:45:03 UTC - in response to Message 348013.  

Not an error - but I think that there probably should have been one - on this result. This is the Workunit. Compare the CPU times. I don't think my computer could have really completed the WU in 1,036.57 seconds. On the second thought, maybe I should post my app on the new optimized app thread. ;-)

Your calibrating BOINC client adjusted that time; it reported a “real” time of 1975 s. Still awfully short, though! There may have been a glitch that caused the progress timer to zero out only that long before the end of a normal crunching period. I notice the result was received about a day and a half after it was sent to you.
ID: 348099 · Report as offensive
Stick Project Donor
Volunteer tester

Send message
Joined: 26 Feb 00
Posts: 100
Credit: 5,283,449
RAC: 5
United States
Message 348434 - Posted: 25 Jun 2006, 17:00:17 UTC - in response to Message 348099.  

Odysseus,

Your "glitch" theory is probably right. Thanks for the reply!

Stick

Not an error - but I think that there probably should have been one - on this result. This is the Workunit. Compare the CPU times. I don't think my computer could have really completed the WU in 1,036.57 seconds. On the second thought, maybe I should post my app on the new optimized app thread. ;-)

Your calibrating BOINC client adjusted that time; it reported a “real” time of 1975 s. Still awfully short, though! There may have been a glitch that caused the progress timer to zero out only that long before the end of a normal crunching period. I notice the result was received about a day and a half after it was sent to you.


ID: 348434 · Report as offensive
HFB1217
Avatar

Send message
Joined: 25 Dec 05
Posts: 102
Credit: 9,424,572
RAC: 0
United States
Message 348475 - Posted: 25 Jun 2006, 17:58:40 UTC
Last modified: 25 Jun 2006, 17:59:22 UTC

Another two 0x3 C++ Errors today.


6/25/2006 9:24:04 AM|SETI@home|Unrecoverable error for result 05ap99ab.20895.28818.429840.3.8_1 ( - exit code -1073741819 (0xc0000005))


------------------------------------------------------------------------------

6/25/2006 1:46:29 PM|SETI@home|Unrecoverable error for result 05ap99ab.20895.28818.429840.3.5_3 (The system cannot find the path specified. (0x3) - exit code 3 (0x3))
ID: 348475 · Report as offensive
Stick Project Donor
Volunteer tester

Send message
Joined: 26 Feb 00
Posts: 100
Credit: 5,283,449
RAC: 5
United States
Message 348690 - Posted: 26 Jun 2006, 0:57:25 UTC - in response to Message 348434.  
Last modified: 26 Jun 2006, 1:00:57 UTC

I got another one (two in a row). But it's not doing it on any other projects (including Seti Beta). Maybe a glitch w/Trux but it's obviously repeatable. Also, I am sure I restarted BOINC (and the computer) between the first and second instance.

Odysseus,

Your "glitch" theory is probably right. Thanks for the reply!

Stick

Not an error - but I think that there probably should have been one - on this result. This is the Workunit. Compare the CPU times. I don't think my computer could have really completed the WU in 1,036.57 seconds. On the second thought, maybe I should post my app on the new optimized app thread. ;-)

Your calibrating BOINC client adjusted that time; it reported a “real” time of 1975 s. Still awfully short, though! There may have been a glitch that caused the progress timer to zero out only that long before the end of a normal crunching period. I notice the result was received about a day and a half after it was sent to you.



ID: 348690 · Report as offensive
Profile Clyde C. Phillips, III

Send message
Joined: 2 Aug 00
Posts: 1851
Credit: 5,955,047
RAC: 0
United States
Message 349275 - Posted: 26 Jun 2006, 18:05:33 UTC

Another client error, cant find path, exit 0x3, good for almost eight hours
ID: 349275 · Report as offensive
angler

Send message
Joined: 19 Oct 00
Posts: 33
Credit: 880,214
RAC: 0
United States
Message 349648 - Posted: 27 Jun 2006, 3:44:43 UTC

http://setiathome.berkeley.edu/result.php?resultid=346629005

massive output
ID: 349648 · Report as offensive
Profile Chet Laughlin

Send message
Joined: 3 May 01
Posts: 24
Credit: 12,717,961
RAC: 0
United States
Message 350180 - Posted: 27 Jun 2006, 15:48:10 UTC

6/27/2006 6:39:41 AM|SETI@home|Unrecoverable error for result 05ap99ab.20895.25504.409648.3.101_1 ( - exit code -1073741819 (0xc0000005))

8 hours 13 minutes before this error on 2.X GHZ CPU.
Chet Laughlin

ID: 350180 · Report as offensive
Profile AKH54
Avatar

Send message
Joined: 28 May 99
Posts: 45
Credit: 2,671,324
RAC: 0
United Kingdom
Message 350750 - Posted: 28 Jun 2006, 8:07:43 UTC

28/06/2006 03:44:25|SETI@home|Unrecoverable error for result 01ap99ab.20150.14513.311076.3.61_1 ( - exit code -1073741819 (0xc0000005))

8 hrs 20 min wasted

2.6 Ghz Dell
Alan
ID: 350750 · Report as offensive
Profile Chet Laughlin

Send message
Joined: 3 May 01
Posts: 24
Credit: 12,717,961
RAC: 0
United States
Message 351338 - Posted: 28 Jun 2006, 23:58:05 UTC


My settings are set for use less than 100GB of disk space...

6/28/2006 10:15:20 AM|SETI@home|Starting task 02ap99aa.3558.15553.404820.3.135_3 using setiathome_enhanced version 515
6/28/2006 4:47:02 PM|SETI@home|Aborting task 18mr99ab.11394.25170.642322.3.212_0: exceeded disk limit: 9531255.000000 > 500000.000000
6/28/2006 4:47:02 PM|SETI@home|Unrecoverable error for result 18mr99ab.11394.25170.642322.3.212_0 (Maximum disk usage exceeded)

Chet Laughlin

ID: 351338 · Report as offensive
Profile KWSN Ekky Ekky Ekky
Avatar

Send message
Joined: 25 May 99
Posts: 944
Credit: 52,956,491
RAC: 67
United Kingdom
Message 351882 - Posted: 29 Jun 2006, 13:26:44 UTC

Now what's going on? Two results running and hours and hours wasted. I claim exactly the same credit as others but get an error message! This cannot be "my fault" it has to be the damn program. This simply is not good enough and I should respectfully like some sort of answer, please.

This is just what was happening a few weeks ago and it was SETI's fault then too:

Result ID 347620252
Name 08ap99aa.18923.3841.92308.3.122_2
Workunit 83277710
Created 27 Jun 2006 5:48:09 UTC
Sent 28 Jun 2006 4:58:48 UTC
Received 29 Jun 2006 11:07:54 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741819 (0xc0000005)
Computer ID 1240160
Report deadline 30 Jul 2006 23:23:37 UTC
CPU time 82095.328125
stderr out

<core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
ar=0.341840 NumCfft=82955 NumGauss= 573836394 NumPulse= 109933858175 NumTriplet= 9533352001536


**********
**********

BOINC Windows Runtime Debugger Version 5.5.0


Dump Timestamp : 06/29/06 10:58:24
SymInitialize(): GetLastError = 3221225495
Debugger Engine : 4.0.5.0
Symbol Search Path:


SymEnumerateModules64(): GetLastError = 6


*** Dump of the Graphics thread (ea4): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 6552500224.000000, User Time: 128651558912.000000, Wait Time: 9583042.000000

- Registers -
eax=01c69b62 ebx=0022fdb0 ecx=0022f78c edx=8f8293bc esi=0022fdb0 edi=00000000
eip=7c90eb94 esp=0022fca4 ebp=0022fcc8
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
SymFromAddr(): GetLastError = '6' Address = '7c90eb94'
SymGetModuleInfo(): GetLastError = '6' Address = '7c90eb94'
0022fcc8 00458554 0022fdb0 00000000 00000000 00000000 !+0x0
SymFromAddr(): GetLastError = '6' Address = '00458554'
SymGetLineFromAddr(): GetLastError = '6' Address = '00458554'
SymGetModuleInfo(): GetLastError = '6' Address = '00458554'
0022ff78 004011e7 00000001 00a80ac0 00a80210 00538000 !+0x0
SymFromAddr(): GetLastError = '6' Address = '004011e7'
SymGetLineFromAddr(): GetLastError = '6' Address = '004011e7'
SymGetModuleInfo(): GetLastError = '6' Address = '004011e7'
0022ffb0 00401258 00000002 00000009 0022fff0 7c816d4f !+0x0
SymFromAddr(): GetLastError = '6' Address = '00401258'
SymGetLineFromAddr(): GetLastError = '6' Address = '00401258'
SymGetModuleInfo(): GetLastError = '6' Address = '00401258'
0022ffc0 7c816d4f 00000000 00000063 7ffdf000 c03b29f8 !+0x0
SymFromAddr(): GetLastError = '6' Address = '7c816d4f'
SymGetLineFromAddr(): GetLastError = '6' Address = '7c816d4f'
SymGetModuleInfo(): GetLastError = '6' Address = '7c816d4f'
0022fff0 00000000 00401240 00000000 78746341 00000020 !+0x0

*** Dump of the Worker thread (43c): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 204687504.000000, User Time: 685554401280.000000, Wait Time: 9583039.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x094AF99E write attempt to address 0x00000001

- Registers -
eax=00000001 ebx=094af090 ecx=094af99c edx=474e5543 esi=00a94eec edi=00a94ec0
eip=094af99e esp=094af068 ebp=094af0a4
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202

- Callstack -
ChildEBP RetAddr Args to Child
SymFromAddr(): GetLastError = '6' Address = '094af99e'
SymGetModuleInfo(): GetLastError = '6' Address = '094af99e'
094af0a4 004c7e85 00a94ec0 ffffffff 00000034 0040553b !+0x0
SymFromAddr(): GetLastError = '6' Address = '004c7e85'
SymGetLineFromAddr(): GetLastError = '6' Address = '004c7e85'
SymGetModuleInfo(): GetLastError = '6' Address = '004c7e85'
094af0b4 0040553b 00a94ee0 00534c7c 004e4f10 004c825b !+0x0
SymFromAddr(): GetLastError = '6' Address = '0040553b'
SymGetLineFromAddr(): GetLastError = '6' Address = '0040553b'
SymGetModuleInfo(): GetLastError = '6' Address = '0040553b'
094af0b8 00a94ee0 00534c7c 004e4f10 004c825b 094af0e4 !+0x0
SymFromAddr(): GetLastError = '6' Address = '00a94ee0'
SymGetLineFromAddr(): GetLastError = '6' Address = '00a94ee0'
SymGetModuleInfo(): GetLastError = '6' Address = '00a94ee0'
094af0bc 00534c7c 004e4f10 004c825b 094af0e4 005253d4 !+0x0
SymFromAddr(): GetLastError = '6' Address = '00534c7c'
SymGetLineFromAddr(): GetLastError = '6' Address = '00534c7c'
SymGetModuleInfo(): GetLastError = '6' Address = '00534c7c'
094af0c0 004e4f10 004c825b 094af0e4 005253d4 00000000 !+0x0
SymFromAddr(): GetLastError = '6' Address = '004e4f10'
SymGetLineFromAddr(): GetLastError = '6' Address = '004e4f10'
SymGetModuleInfo(): GetLastError = '6' Address = '004e4f10'
094af0c4 004c825b 094af0e4 005253d4 00000000 00000000 !+0x0
SymFromAddr(): GetLastError = '6' Address = '004c825b'
SymGetLineFromAddr(): GetLastError = '6' Address = '004c825b'
SymGetModuleInfo(): GetLastError = '6' Address = '004c825b'
094af0c8 094af0e4 005253d4 00000000 00000000 00000001 !+0x0
SymFromAddr(): GetLastError = '6' Address = '094af0e4'
SymGetLineFromAddr(): GetLastError = '6' Address = '094af0e4'
SymGetModuleInfo(): GetLastError = '6' Address = '094af0e4'
094af0cc 005253d4 00000000 00000000 00000001 00a94e50 !+0x0
SymFromAddr(): GetLastError = '6' Address = '005253d4'
SymGetLineFromAddr(): GetLastError = '6' Address = '005253d4'
SymGetModuleInfo(): GetLastError = '6' Address = '005253d4'
094af0e4 00000000 77c61aa0 094af134 77c2c2cd 00000004 !+0x0

*** Dump of the Timer thread (b94): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 9583016.000000

- Registers -
eax=00000001 ebx=00000000 ecx=000000bf edx=00000000 esi=00000001 edi=08fa4654
eip=7c90eb94 esp=096aff08 ebp=096affb4
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000296

- Callstack -
ChildEBP RetAddr Args to Child
SymFromAddr(): GetLastError = '6' Address = '7c90eb94'
SymGetModuleInfo(): GetLastError = '6' Address = '7c90eb94'
096affb4 7c80b50b 00000000 08fa4654 7ffdf000 00000000 !+0x0
SymFromAddr(): GetLastError = '6' Address = '7c80b50b'
SymGetLineFromAddr(): GetLastError = '6' Address = '7c80b50b'
SymGetModuleInfo(): GetLastError = '6' Address = '7c80b50b'
096affec 00000000 76b5aee7 00000000 00000000 00000008 !+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name : setiathome_enhanced version 5.15 [workunit: 08ap99aa.18923.3841.92308.3.122]
Window Class : BOINC_app
Window Process ID: e4c
Window Thread ID : ea4

Exiting...

</stderr_txt>

Validate state Invalid
Claimed credit 75.9019932465236
Granted credit 0
application version 5.15



ID: 351882 · Report as offensive
Previous · 1 . . . 15 · 16 · 17 · 18 · 19 · 20 · 21 . . . 22 · Next

Message boards : Number crunching : Computation errors on Seti Enhanced


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.