The "BOINC API library" Bruce wrote about is that part of BOINC that gets linked into the App. So you don't need a new BOINC Core Client, you just need to download an install the new App, version 0.11, from the Test App page.
I think "The BOINC Monitor app" you were talking about is part of the "BOINC Stat Viewer"? Sorry, I'm not familiar with the various Add-ons and have to admit that I have no idea what exactly this "Checking" status means. Can anyone else help out?
You are correct I am running BOINC Stat Viewer to monitor the completions times and progress on each WU. While most of this is availble in BOINC Manager, Stat Viewer will hold a snapshat for a few min so I can take a look at things that are transient.
The Checking message usually appears for a second or two when a BOINC application switches. Usually this only lasts for however long it takes to start processing the WU. For it to hold that status for hours on a stuck E@H WU, I figure it might be a clue to the programmers as to where it is hung.
I hope the ERROR 15 message in the WU files from the last one that stuck is even more helpful. I wish there was a Debuger that I could turn on to capture just what is going on to help these guys out. I for one am mort interested in the D.P. concept than the actual project science itself. So I relly am willing to help these guys as much as I can.
Regards
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Hm. Did you check the md5 sum of the package you downloaded? To me this "Checking" seems like the usual checking of the signature of the App. But as anonymous Apps doesn't have a signature, well, I don't really know what it's doing there.
You should be able to find and start the Activity Monitor (in /Applications/Utilities). Select the process you're interested in, click "inspect", then "sample". It should give you a "call stack" and a clue of what it's doing.
Activity monitor is also running (I am not as interested in credits as what is going on). I'll try your suggestion. I still have one WU sitting here that I have not been told to abort yet. I am certain if i let E@H take a look at that WU it will puck again and i can dump the stats you mentioned.
Thanks
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Is there some way to reset the WUs I already have downloaded so that the system thinks they are fresh, and then allow the 011 APP to have a crack at them?
Regards
phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
clock_sleep_trap 34
__spin_lock_relinquish 20
__spin_lock 14
Sample analysis of process 727 written to file /dev/stdout
Sampling process 727 each 10 msecs 100 times
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Yep. This is the freeze we expected with the 0.08 App, actually in __vfprintf().
You can do the following:
- Stop the BOINC client.
- Open the einstein project folder (where you put the files from the test package in)
- Delete the einstein_0.08_powerpc-apple-darwin App.
- Make a copy of the einstein_0.11_powerpc-apple-darwin App and name it einstein_0.08_powerpc-apple-darwin
- Start the client again.
He will actually use the 0.11 App (though running as 0.08) to finish the result.
The "BOINC API library" Bruce
)
The "BOINC API library" Bruce wrote about is that part of BOINC that gets linked into the App. So you don't need a new BOINC Core Client, you just need to download an install the new App, version 0.11, from the Test App page.
BM
BM
Ok thanks. I already did
)
Ok thanks. I already did that on the PowerBook and it looks like it is running very well.
Regards
phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Phil, I think "The BOINC
)
Phil,
I think "The BOINC Monitor app" you were talking about is part of the "BOINC Stat Viewer"? Sorry, I'm not familiar with the various Add-ons and have to admit that I have no idea what exactly this "Checking" status means. Can anyone else help out?
BM
BM
Bernd- You are correct I
)
Bernd-
You are correct I am running BOINC Stat Viewer to monitor the completions times and progress on each WU. While most of this is availble in BOINC Manager, Stat Viewer will hold a snapshat for a few min so I can take a look at things that are transient.
The Checking message usually appears for a second or two when a BOINC application switches. Usually this only lasts for however long it takes to start processing the WU. For it to hold that status for hours on a stuck E@H WU, I figure it might be a clue to the programmers as to where it is hung.
I hope the ERROR 15 message in the WU files from the last one that stuck is even more helpful. I wish there was a Debuger that I could turn on to capture just what is going on to help these guys out. I for one am mort interested in the D.P. concept than the actual project science itself. So I relly am willing to help these guys as much as I can.
Regards
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Hm. Did you check the md5 sum
)
Hm. Did you check the md5 sum of the package you downloaded? To me this "Checking" seems like the usual checking of the signature of the App. But as anonymous Apps doesn't have a signature, well, I don't really know what it's doing there.
You should be able to find and start the Activity Monitor (in /Applications/Utilities). Select the process you're interested in, click "inspect", then "sample". It should give you a "call stack" and a clue of what it's doing.
BM
BM
Activity monitor is also
)
Activity monitor is also running (I am not as interested in credits as what is going on). I'll try your suggestion. I still have one WU sitting here that I have not been told to abort yet. I am certain if i let E@H take a look at that WU it will puck again and i can dump the stats you mentioned.
Thanks
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Is there some way to reset
)
Is there some way to reset the WUs I already have downloaded so that the system thinks they are fresh, and then allow the 011 APP to have a crack at them?
Regards
phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Here is a dump of the
)
Here is a dump of the Activity monitor sample;
All of the lines are indented down to clock_sleep_trap then they come back out to the margin (just in case format is important).
2005-08-03 19:06:16.419 sample[766] Couldn't start c++filt for C++ name demangling
Analysis of sampling pid 727 every 10.000000 milliseconds
Call graph:
34 Thread_0e0b
34 _dyld_start
34 _start
34 main
34 _Z24boinc_init_graphics_implPFvvEP16BOINC_MAIN_STATE
34 boinc_init_options_graphics_impl
34 _Z24xwin_graphics_event_loopv
34 sleep
34 nanosleep
34 clock_sleep_trap
34 clock_sleep_trap
34 Thread_0f03
34 _pthread_body
34 _Z6foobarPv
34 worker
34 boincmain
34 InitFStat
34 LALInitBarycenter
34 fscanf
34 __svfscanf
34 strtod
34 __pow5mult_D2A
34 __spin_unlock
34 _sigtramp
34 _Z12worker_timeri
34 _Z19update_app_progressdddd
34 sprintf
34 __vfprintf
34 __dtoa
34 __d2b_D2A
34 __Balloc_D2A
20 __spin_lock_relinquish
20 __spin_lock_relinquish
14 __spin_lock
14 __spin_lock
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
clock_sleep_trap 34
__spin_lock_relinquish 20
__spin_lock 14
Sample analysis of process 727 written to file /dev/stdout
Sampling process 727 each 10 msecs 100 times
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.
Yep. This is the freeze we
)
Yep. This is the freeze we expected with the 0.08 App, actually in __vfprintf().
You can do the following:
- Stop the BOINC client.
- Open the einstein project folder (where you put the files from the test package in)
- Delete the einstein_0.08_powerpc-apple-darwin App.
- Make a copy of the einstein_0.11_powerpc-apple-darwin App and name it einstein_0.08_powerpc-apple-darwin
- Start the client again.
He will actually use the 0.11 App (though running as 0.08) to finish the result.
BM
BM
Thanks Bernd. consider it
)
Thanks Bernd. consider it done.
Phil
We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.