AstroPulse errors - Reporting

Message boards : Number crunching : AstroPulse errors - Reporting
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 . . . 14 · Next

AuthorMessage
Larry

Send message
Joined: 8 Jul 08
Posts: 11
Credit: 692,410
RAC: 0
United States
Message 800039 - Posted: 20 Aug 2008, 4:28:40 UTC - in response to Message 799825.  

Does anyone have an idea as to why this AP unit returned a compute error?
http://setiathome.berkeley.edu/result.php?resultid=946854005

Thanks.


Try going to your results and click on the Work Unit ID and see if anyone else is having a problem with it. I found one the other day where 5 of 6 machines had returned a compute error. The 6th was still crunching. I suspect that the WU had an error in it. This was a MB work unit not an AP. I don't know how long S@H will continue to try on this.

Of course if you computer crashed while running the WU that may have caused an issue.

Larry
ID: 800039 · Report as offensive
Wandering Willie
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 136
Credit: 2,127,073
RAC: 0
United Kingdom
Message 800069 - Posted: 20 Aug 2008, 9:13:16 UTC
Last modified: 20 Aug 2008, 9:24:42 UTC

This is a problem over here that WU's get purged after a couple of days.

Perhaps this should be altered for a perod of time.

Is a validated 719.06 0.00 credit claimed/granted accepted as valid and purged never to be seen again???

Michael.
ID: 800069 · Report as offensive
W-K 666 Project Donor
Volunteer tester

Send message
Joined: 18 May 99
Posts: 19214
Credit: 40,757,560
RAC: 67
United Kingdom
Message 800070 - Posted: 20 Aug 2008, 9:32:42 UTC - in response to Message 800069.  

This is a problem over here that WU's get purged after a couple of days.

Perhaps this should be altered for a perod of time.

Is a validated 719.06 0.00 credit claimed/granted accepted as valid and purged never to be seen again???

Michael.

They get transfered to another database 24hrs after validation because of limited disc space. Full disc space is one of the reasons for the latest server problems.
ID: 800070 · Report as offensive
Urs Echternacht
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 692
Credit: 135,197,781
RAC: 211
Germany
Message 800088 - Posted: 20 Aug 2008, 12:28:33 UTC - in response to Message 800069.  

...
Is a validated 719.06 0.00 credit claimed/granted accepted as valid and purged never to be seen again???

No, to see that happen this result for the work_unit would have to be validated invalid and two other returned results for this work_unit would have to be validated valid before the work_unit is purged.
_\|/_
U r s
ID: 800088 · Report as offensive
MarkJ Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 08
Posts: 1139
Credit: 80,854,192
RAC: 5
Australia
Message 800093 - Posted: 20 Aug 2008, 12:50:27 UTC - in response to Message 799901.  

Finished an Astropulse crunch.
940322137 309888091 3 Aug 2008 16:52:28 UTC 5 Aug 2008 23:41:36 UTC Over Success Done 168,830.40 719.06 0.00

719.06 credits requested
0.00 credits given

That was alot of CPU time to get squat. :-(

Next time I see an astropulse work item, I'll be sure to cancel/abort it.




Agreed. My computer worked an entire week during which time I'd get at least 300 per day. The 700 or so I got really was not adequate. I'll be canceling the unit the same next time I see an Astropulse WU if this is not quickly addressed.


You can tell Seti not to send you Astropulse work units...

    1. Go to your account on the S@H web site.
    2. Click on the "Seti@home preferences" link.
    3. Scroll down and click on the "Edit Seti@home preferences" link.
    4. In the "Run only selected applications" section, uncheck the box next to Astropulse.
    5. Click the "Update preferences" button.



BOINC blog
ID: 800093 · Report as offensive
Wandering Willie
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 136
Credit: 2,127,073
RAC: 0
United Kingdom
Message 800096 - Posted: 20 Aug 2008, 12:59:24 UTC - in response to Message 800093.  

Finished an Astropulse crunch.
940322137 309888091 3 Aug 2008 16:52:28 UTC 5 Aug 2008 23:41:36 UTC Over Success Done 168,830.40 719.06 0.00

719.06 credits requested
0.00 credits given

That was alot of CPU time to get squat. :-(

Next time I see an astropulse work item, I'll be sure to cancel/abort it.




Agreed. My computer worked an entire week during which time I'd get at least 300 per day. The 700 or so I got really was not adequate. I'll be canceling the unit the same next time I see an Astropulse WU if this is not quickly addressed.


You can tell Seti not to send you Astropulse work units...

    1. Go to your account on the S@H web site.
    2. Click on the "Seti@home preferences" link.
    3. Scroll down and click on the "Edit Seti@home preferences" link.
    4. In the "Run only selected applications" section, uncheck the box next to Astropulse.
    5. Click the "Update preferences" button.





My point was did your wing person return with the same result.

I have seen instances of this over on Beta But you can go back a fair way to look at results to check. I did have an instance myself and posted.

It was queried and adjusted.

Michael.
ID: 800096 · Report as offensive
DJStarfox

Send message
Joined: 23 May 01
Posts: 1066
Credit: 1,226,053
RAC: 2
United States
Message 800443 - Posted: 21 Aug 2008, 16:16:06 UTC - in response to Message 799634.  
Last modified: 21 Aug 2008, 16:22:18 UTC

To make DCF work as well as it can, the project needs to get the raw estimates for all work in line. From reported data here it looks like the AP estimate needs to be scaled up, but the most that can be expected is scaling to approximately match stock setiathome_enhanced. Those running optimized s_e will continue to have a significant mismatch unless optimized versions of AstroPulse can be produced which achieve similar speed improvements.


All you can do is calibrate the scaling to the stock apps. The guys running optimized apps should be smart enough to know the est. completion times will be off. :)

That said, my 1st AP WU since reattaching to SETI says it will take 92 hours on a 3.0GHz E8400. That seems a bit high compared to the others on the forum. I'll wait until it reports OK before talking anymore about this.


My first AP task completed OK. Total CPU time was 134653.8. Claimed credit was 727.72. My current DCP for SETI 0.860610. Is this approximately correct credit?

Oh, I should also point out that BOINC thought that AP task would take 90 hours upon download, but it only took 37 to finish.
ID: 800443 · Report as offensive
Profile SATAN
Avatar

Send message
Joined: 27 Aug 06
Posts: 835
Credit: 2,129,006
RAC: 0
United Kingdom
Message 800694 - Posted: 22 Aug 2008, 5:57:27 UTC

process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1152
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1280
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1408
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1536
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1664
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1792
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1920
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
SIGABRT: abort called

Crashed executable name: astropulse_4.35_i686-apple-darwin
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.5.4 build 9E17
Fri Aug 22 06:26:24 2008

sh: /usr/bin/atos: No such file or directory
0 0x0004e931 1 0x00042f12 2 0x95a6a09b 3 0xffffffff 4 0x95ae2ec2 5 0x95af247f 6 0x92bc1005 7 0x92bbf10c 8 0x92bbf14b 9 0x92bbf261 10 0x92bbf5d8 11 0x00026fe3 12 0x00028837 13 0x0002bd55 14 0x0002cf49 15 0x000185bf 16 0x0003a9f4 17 0x00037e76 18 0x00031421 19 0x00034768 20 0x00002736
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x95a31e62 ecx: 0xbfffd2ac edx: 0x959fd4a6
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffd2e8 esp: 0xbfffd2ac
ss: 0x0000001f efl: 0x00000206 eip: 0x959fd4a6 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0xeafff /Library/Application Support/BOINC Data/slots/8/../../projects/setiathome.berkeley.edu/astropulse_4.35_i686-apple-darwin
0x9126d000 - 0x91271fff /usr/lib/system/libmathCommon.A.dylib
0x92b79000 - 0x92bd6fff /usr/lib/libstdc++.6.dylib
0x93b78000 - 0x93b7ffff /usr/lib/libgcc_s.1.dylib
0x959fc000 - 0x95b5cfff /usr/lib/libSystem.B.dylib


Exiting...

</stderr_txt>

Got the same error on me mac pro.
ID: 800694 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 800704 - Posted: 22 Aug 2008, 6:20:14 UTC - in response to Message 800694.  

process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1152
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1280
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1408
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1536
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1664
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1792
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1920
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
SIGABRT: abort called

Crashed executable name: astropulse_4.35_i686-apple-darwin
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.5.4 build 9E17
Fri Aug 22 06:26:24 2008

sh: /usr/bin/atos: No such file or directory
0 0x0004e931 1 0x00042f12 2 0x95a6a09b 3 0xffffffff 4 0x95ae2ec2 5 0x95af247f 6 0x92bc1005 7 0x92bbf10c 8 0x92bbf14b 9 0x92bbf261 10 0x92bbf5d8 11 0x00026fe3 12 0x00028837 13 0x0002bd55 14 0x0002cf49 15 0x000185bf 16 0x0003a9f4 17 0x00037e76 18 0x00031421 19 0x00034768 20 0x00002736
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x95a31e62 ecx: 0xbfffd2ac edx: 0x959fd4a6
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffd2e8 esp: 0xbfffd2ac
ss: 0x0000001f efl: 0x00000206 eip: 0x959fd4a6 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0xeafff /Library/Application Support/BOINC Data/slots/8/../../projects/setiathome.berkeley.edu/astropulse_4.35_i686-apple-darwin
0x9126d000 - 0x91271fff /usr/lib/system/libmathCommon.A.dylib
0x92b79000 - 0x92bd6fff /usr/lib/libstdc++.6.dylib
0x93b78000 - 0x93b7ffff /usr/lib/libgcc_s.1.dylib
0x959fc000 - 0x95b5cfff /usr/lib/libSystem.B.dylib


Exiting...

</stderr_txt>

Got the same error on me mac pro.


From farther up in the thread

Looks like you got bitten by the same bug as me, I lost an AP unit as well when it was suspended.

Try turning on the "Leave Application in Memory" option.


We have to either let them run through without interruption or try the leave in memory option.


ID: 800704 · Report as offensive
Profile SATAN
Avatar

Send message
Joined: 27 Aug 06
Posts: 835
Credit: 2,129,006
RAC: 0
United Kingdom
Message 800757 - Posted: 22 Aug 2008, 11:47:29 UTC

Was going to ask you if leaving in memory worked. Obviously it does, so will do that from now on.
ID: 800757 · Report as offensive
Profile arkayn
Volunteer tester
Avatar

Send message
Joined: 14 May 99
Posts: 4438
Credit: 55,006,323
RAC: 0
United States
Message 800913 - Posted: 22 Aug 2008, 20:05:43 UTC - in response to Message 800757.  

Was going to ask you if leaving in memory worked. Obviously it does, so will do that from now on.


To a point, Dotsch posted this above as well.

In very few circumstances the MacOS application crashs with these error messages on PPC and Intel. With he preferences option "leave application in memory while supspended" it looks better and the application crashs not so often. But it could also happens...
I will contact Eric about this issue.


ID: 800913 · Report as offensive
Profile SATAN
Avatar

Send message
Joined: 27 Aug 06
Posts: 835
Credit: 2,129,006
RAC: 0
United Kingdom
Message 801006 - Posted: 22 Aug 2008, 22:10:37 UTC

Thanks for the info and advice arkayn, but I just had 3 units have there own compute error's. Not going to bother with Ap until things become a little more stable.

Hat's of to Dotsch though for getting an app that does work.
ID: 801006 · Report as offensive
Dave
Volunteer tester
Avatar

Send message
Joined: 3 Aug 08
Posts: 16
Credit: 622,564
RAC: 0
United States
Message 801089 - Posted: 23 Aug 2008, 1:56:17 UTC - in response to Message 799845.  

Looks like you got bitten by the same bug as me, I lost an AP unit as well when it was suspended.

Try turning on the "Leave Application in Memory" option.


My first Astropulse unit has just crashed too. Intel Mac. Task result

As with others below (or above, depending which way you like your threads), I had suspended it while running other things and it crashed immediately upon resumption.

When I have used 'Leave Application in Memory' in the past, I have had trouble with tasks not releasing the CPU and seeming to get stuck in a full power loop, busily calculating nothing. Task progress was not incrementing but Hardware Monitor showed the processor(s) still steaming away at 100%.

I think I'll wait until a real fix is forthcoming.


Well I am having fun watching my second Astropulse run.
#ap_06fe08ac_B0_P1_00324_20080813_29361.wu_0
Original CPU estimate was 142 hours.
Currently 61 hours complete, progress is 20.497% and CPU estimate to completion is now another 146 hours.
Interesting, so I will let it finish and have another completed AP unit for discussion purposes.
I run with "leave app in memory" and have my second CPU crunching at the moment.
When the second CPU finishes crunching its units, I will watch the time estimates to see if there is a significant change in the AP unit.

Running on an AuthenticAMD AMD Turion(tm) 64 X2 Mobile Technology TL-58 [x86 Family 15 Model 104 Stepping 1] with Microsoft Windows Vista
Home Premium x86 Editon

ID: 801089 · Report as offensive
Dave
Volunteer tester
Avatar

Send message
Joined: 3 Aug 08
Posts: 16
Credit: 622,564
RAC: 0
United States
Message 801296 - Posted: 23 Aug 2008, 16:16:53 UTC - in response to Message 801089.  

Looks like you got bitten by the same bug as me, I lost an AP unit as well when it was suspended.

Try turning on the "Leave Application in Memory" option.


My first Astropulse unit has just crashed too. Intel Mac. Task result

As with others below (or above, depending which way you like your threads), I had suspended it while running other things and it crashed immediately upon resumption.

When I have used 'Leave Application in Memory' in the past, I have had trouble with tasks not releasing the CPU and seeming to get stuck in a full power loop, busily calculating nothing. Task progress was not incrementing but Hardware Monitor showed the processor(s) still steaming away at 100%.

I think I'll wait until a real fix is forthcoming.


Well I am having fun watching my second Astropulse run.
#ap_06fe08ac_B0_P1_00324_20080813_29361.wu_0
Original CPU estimate was 142 hours.
Currently 61 hours complete, progress is 20.497% and CPU estimate to completion is now another 146 hours.
Interesting, so I will let it finish and have another completed AP unit for discussion purposes.
I run with "leave app in memory" and have my second CPU crunching at the moment.
When the second CPU finishes crunching its units, I will watch the time estimates to see if there is a significant change in the AP unit.

Running on an AuthenticAMD AMD Turion(tm) 64 X2 Mobile Technology TL-58 [x86 Family 15 Model 104 Stepping 1] with Microsoft Windows Vista
Home Premium x86 Editon



Update:
75:25 hours running
25.288% progress complete
141:24 left to completion
ID: 801296 · Report as offensive
Profile dgkenny
Avatar

Send message
Joined: 22 Jun 99
Posts: 1
Credit: 81,580,813
RAC: 15
United States
Message 801479 - Posted: 24 Aug 2008, 0:09:17 UTC

These are the results of a recent Astropulse unit:

Astropulse unit ID: ap_01mr08ab_B5_P0_00342_20080806_05267.wu

Task ID's: 945557526 and 945557525; claimed credit: 714.61 (each); granted credit: 0.00 (each)

Another task ID failed with an error on the same unit. The task has been assigned again.

I have seen similar results on another Astropulse unit, but cannot remember which one.

I hope they fix this soon.

Dennis
ID: 801479 · Report as offensive
Dave
Volunteer tester
Avatar

Send message
Joined: 3 Aug 08
Posts: 16
Credit: 622,564
RAC: 0
United States
Message 801570 - Posted: 24 Aug 2008, 7:00:47 UTC - in response to Message 801296.  

Looks like you got bitten by the same bug as me, I lost an AP unit as well when it was suspended.

Try turning on the "Leave Application in Memory" option.


My first Astropulse unit has just crashed too. Intel Mac. Task result

As with others below (or above, depending which way you like your threads), I had suspended it while running other things and it crashed immediately upon resumption.

When I have used 'Leave Application in Memory' in the past, I have had trouble with tasks not releasing the CPU and seeming to get stuck in a full power loop, busily calculating nothing. Task progress was not incrementing but Hardware Monitor showed the processor(s) still steaming away at 100%.

I think I'll wait until a real fix is forthcoming.


Well I am having fun watching my second Astropulse run.
#ap_06fe08ac_B0_P1_00324_20080813_29361.wu_0
Original CPU estimate was 142 hours.
Currently 61 hours complete, progress is 20.497% and CPU estimate to completion is now another 146 hours.
Interesting, so I will let it finish and have another completed AP unit for discussion purposes.
I run with "leave app in memory" and have my second CPU crunching at the moment.
When the second CPU finishes crunching its units, I will watch the time estimates to see if there is a significant change in the AP unit.

Running on an AuthenticAMD AMD Turion(tm) 64 X2 Mobile Technology TL-58 [x86 Family 15 Model 104 Stepping 1] with Microsoft Windows Vista
Home Premium x86 Editon



Update:
75:25 hours running
25.288% progress complete
141:24 left to completion


Update 2:
87:10 hours running
29.000% progress complete
137:51 left to completion
ID: 801570 · Report as offensive
Wandering Willie
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 136
Credit: 2,127,073
RAC: 0
United Kingdom
Message 801595 - Posted: 24 Aug 2008, 10:40:23 UTC

Just got this error message on an Astropulse



962089549
Name ap_04jl08ac_B4_P0_00409_20080823_15578.wu_1
Workunit 319820996
Created 23 Aug 2008 17:34:41 UTC
Sent 23 Aug 2008 21:48:32 UTC
Received 24 Aug 2008 9:09:23 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -226 (0xffffffffffffff1e)
Computer ID 3738375
Report deadline 22 Sep 2008 21:48:32 UTC
CPU time 9373.603
stderr out <core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
too many exit(0)s
</message>
<stderr_txt>

Michael
ID: 801595 · Report as offensive
Profile Fred J. Verster
Volunteer tester
Avatar

Send message
Joined: 21 Apr 04
Posts: 3252
Credit: 31,903,643
RAC: 0
Netherlands
Message 801643 - Posted: 24 Aug 2008, 15:19:51 UTC
Last modified: 24 Aug 2008, 15:42:01 UTC

So far i've had about 7 or 8 AP units, that i'm aware off, should look @ my results, but to less time.
1 or 2 errored out, the others took about 22 - 30 hours on a QX9650 @ 3500MHz, running UBUNTU 8.04.
The credit claim was about 720.
WU
Result
ID: 801643 · Report as offensive
David Kirkby

Send message
Joined: 3 Apr 99
Posts: 6
Credit: 13,332,091
RAC: 36
United Kingdom
Message 801647 - Posted: 24 Aug 2008, 15:56:34 UTC

Task ID 945888297
Name ap_04jl08aa_B6_P1_00079_20080807_20336.wu_1
Workunit 312521251
Created 7 Aug 2008 10:04:45 UTC
Sent 7 Aug 2008 14:10:34 UTC
Received 24 Aug 2008 15:44:07 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 2101539
Report deadline 6 Sep 2008 14:10:34 UTC
CPU time 451160.1
stderr out <core_client_version>6.2.14</core_client_version>
<![CDATA[
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1152
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1152
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1280
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1408
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1408
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1536
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1664
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1792
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1920
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2176
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2304
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2432
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2560
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2688
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2816
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2816
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2944
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3072
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3200
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3328
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3456
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3584
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3712
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3840
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3968
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4096
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4224
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4352
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4480
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4608
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4736
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4864
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4992
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 4992
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5120
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5248
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5376
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5504
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5632
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5760
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 5888
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6016
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6144
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6272
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6400
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6528
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6656
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6784
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 6912
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7040
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7168
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7296
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7424
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7552
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7552
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7552
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7680
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7808
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 7936
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8064
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8192
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8320
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8448
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8576
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8704
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8832
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 8960
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9088
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9216
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9216
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9344
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9472
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9600
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9728
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9856
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 9984
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10112
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10240
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10368
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10496
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10496
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10624
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10752
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10880
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10880
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 10880
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11008
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11136
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11264
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11392
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11520
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11648
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11776
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11904
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 11904
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12032
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12160
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12288
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12416
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12416
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12544
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12544
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12672
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12800
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 12928
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13056
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13184
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13312
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13440
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13440
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13568
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13696
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13824
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13824
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 13952
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14080
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14208
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14336
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14464
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14592
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14720
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14848
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14976
called boinc_finish

</stderr_txt>
]]>

Validate state Valid
Claimed credit 714.397767358686
Granted credit 0
application version 4.35


HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS

120 odd hours for nothing. Until astropulse is sorted it will be aborted on my comps. Dayoff
ID: 801647 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 801649 - Posted: 24 Aug 2008, 16:11:12 UTC - in response to Message 801647.  

Task ID 945888297
Name ap_04jl08aa_B6_P1_00079_20080807_20336.wu_1
Workunit 312521251
Created 7 Aug 2008 10:04:45 UTC
Sent 7 Aug 2008 14:10:34 UTC
Received 24 Aug 2008 15:44:07 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 2101539
Report deadline 6 Sep 2008 14:10:34 UTC
CPU time 451160.1
stderr out <core_client_version>6.2.14</core_client_version>
<![CDATA[
<stderr_txt>
SNIP
</stderr_txt>
]]>

Validate state Valid
Claimed credit 714.397767358686
Granted credit 0
application version 4.35


HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS

120 odd hours for nothing. Until astropulse is sorted it will be aborted on my comps. Dayoff


Give it time and Eric will probably manually grant you Credit.

Claggy
ID: 801649 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 . . . 14 · Next

Message boards : Number crunching : AstroPulse errors - Reporting


 
©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.