Hi Jimmy, as Charlie said in your other thread, BOINC 6.12 is no longer updated, so anything happening in it won't be followed up on.

All concentration is on BOINC 7 (latest at time of posting this is 7.0.12), so if you want to try if you can get similar results there, then the developers will be thrilled... and not, of course, as it means more bugs to squash. ;-)

My concerns are the several other issues you have raised, such as the md5 errors, spontaneous restarts, etc.

set the coproc_debug flag in your cc_config.xml file

<coproc_debug>
Show details of coprocessor (GPU) scheduling. List-add.png New in 6.3

My concerns are the several other issues you have raised, such as the md5 errors, spontaneous restarts, etc.

Hi Jimmy G,

The application that was restarting appears to be the BOINC Client, not the BOINC Manager (which is just the user interface to the Client). But since there was no crash report in stderrdae.txt, I don't have any idea why it restarted itself.

I have forwarded the information you sent me to David Anderson. He is the person who has been working on the BOINC scheduler. I really know very little about that aspect of BOINC. I am hoping he can help you figure this out.

Cheers,
--Charlie

Not without sending along your complete BOINC Data directory. It isn't just copying the tasks along to another computer, it requires an attachment to that project, entries made in the client_state.xml file etc.

LOL

You got mice in there, ey? :-)

let me know what I can do for you folks before I pull the pin!

Tell us how to get to your bank-account. ;-)

No problem. I think Charlie said he wants the stdoutdae.txt not stderr.txt.

...but no...

stderr.txt

...perhaps this file needs to be manually created and placed in this folder like the cc_config.xml had to be...?

No. The stderr.txt file is created by the project's science app in whatever slots directory the task has been assigned to. When the task finishes, the stderr.txt file is uploaded to the project server and kept as part of the task details on the project website. To view the task details and stderr.txt, go to the project website, click Your Account -> View Computers on this account. Locate the computer in question from the list of your computers, in the left-hand column click Tasks to see the list of tasks recently issued to that computer. In the left-hand column click "show names". Now from the Event Log you quoted earlier the task for which Charlie wants to see the stderr.txt is named "nbody-Plum_Embedded_5557114_1". Locate that name in the left-hand column and click it to see the details and the stderr.txt for that task. The text below the Stderr Output title is the stderr.txt plus a few extra lines.

Task details are not kept forever if you can't find nbody-Plum_Embedded_5557114_1 in the list it may already be deleted from the list. Or it may be on the next page so look for the "Next 20" link to get to the next page of the list.

Sorry. I meant to ask you for the stderrdae.txt file.

Cheers,
--Charlie

getaddrinfo: No such file or directory
getaddrinfo: No such file or directory
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation_0.82_x86_64-apple-darwin
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
getaddrinfo: Bad file descriptor
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
getaddrinfo: Bad file descriptor
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
getaddrinfo: Bad file descriptor
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
getaddrinfo: Bad file descriptor
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108
md5_file: can't open projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_0.84_x86_64-apple-darwin__mt
md5_file: Too many open files
error: verify_file: md5_file error -108

Like I said, I'll be happy to send along the important files on this and run a more thorough debugging routine for you folks (if there is one and someone can supply me with code and instructions!

Thanks for the report. Regarding issue 2, it looks like the BOINC Client crashed (not the BOINC Manager). The Manager automatically restarts the Client if this happens. Of particular interest would be an excerpt from the stderr.txt file from several minutes before the errors until the time of the restart (about 12:20 through 12:22 on 14-Jan-2012.) With luck, it might contain a crash log.

You can copy and paste these into either a response on this thread or a private message to me.

Also, it might be helpful to know which version of Mac OS X you are running.

Thanks in advance.

Cheers,
--Charlie

SIGPIPE: write on a pipe with no reader
kill: kill: kill: kill: 6107875164kill: kill: kill: : 7937975125: 5916585982No such process
: : : No such process
No such process
: 77498No such process
No such process
: No such process
No such process
SIGBUS: bus error

Crashed executable name: BOINCManager
built using BOINC library version 6.12.35
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.6.8 build 10K549
Wed Oct 26 07:27:42 2011

14-Jan-2012 12:20:32 [Milkyway@Home] Computation for task nbody-Plum_Embedded_5557114_1 finished
14-Jan-2012 12:20:32 [Milkyway@Home] [task] result state=FILES_UPLOADING for nbody-Plum_Embedded_5557114_1 from CS::app_finished
14-Jan-2012 12:20:32 [Milkyway@Home] [task] result state=FILES_UPLOADED for nbody-Plum_Embedded_5557114_1 from CS::update_results
14-Jan-2012 12:20:32 [Milkyway@Home] Failed to open init file slots/7/init_data.xml
14-Jan-2012 12:20:32 [Milkyway@Home] Signature verification error for milkyway_nbody_0.84_x86_64-apple-darwin__mt
14-Jan-2012 12:20:32 [Milkyway@Home] [task] result state=COMPUTE_ERROR for nbody-Plum_Embedded_4665316_1 from CS::report_result_error
14-Jan-2012 12:20:32 [Milkyway@Home] [task] couldn't start app: Can't write init file: -108
14-Jan-2012 12:20:32 [Milkyway@Home] [task] task_state=COULDNT_START for nbody-Plum_Embedded_4665316_1 from start
14-Jan-2012 12:20:32 [Milkyway@Home] [task] task_state=COULDNT_START for nbody-Plum_Embedded_4665316_1 from resume_or_start1
14-Jan-2012 12:20:32 [---] Can't open client_state_next.xml: fopen() failed
14-Jan-2012 12:20:32 [---] Couldn't write state file: fopen() failed; giving up
14-Jan-2012 12:21:37 [---] Starting BOINC client version 6.12.35 for x86_64-apple-darwin
14-Jan-2012 12:21:37 [---] log flags: file_xfer, sched_ops, task, task_debug
14-Jan-2012 12:21:37 [---] Libraries: libcurl/7.19.7 OpenSSL/0.9.7l zlib/1.2.3 c-ares/1.6.0
14-Jan-2012 12:21:37 [---] Data directory: /Library/Application Support/BOINC Data
14-Jan-2012 12:21:37 [---] Processor: 8 GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz [x86 Family 6 Model 42 Stepping 7]

Jimmy, the developers ask you to run with a debug option on.
To do so, use any clear text editor to make a file called cc_config.xml in your BOINC Data directory (default in OS X at /Library/Applications Support/BOINC/

In it add the following lines:

<cc_config>
<log_flags>
<task_debug>1</task_debug>
</log_flags>
</cc_config>