Does not yield anything useful, at least not that I am able to find.

This is a brand new install of BOINC 7.0.29 on a brand new Fedora 18 distro running off an SSD.

Nothing has been added or changed from the stock 7.0.29 client.

I do not understand where the error messages that I see are coming from. What file is being examined to make these error messages appear??

I am perfectly willing to edit the offending information out of the file(s), if someone can tell me which file(s) are at fault. I think that I can find them IF I CAN GET SOMEONE TO TELL ME WHAT THE FILENAME(S) ARE.


I see nothing in the FAQ that applies to the question I am asking. I have no idea whether this is a BOINC 7.0.29 problem, a file somewhere in the BOINC 7.0.29 directories, or a BAM! problem. I do not believe that this is a BAM! problem, BUT WHERE DO I GO FROM HERE TO GET A SOLUTION!!

Back in Ubuntu with BOINC 7.0.28 and Nvidia 313.26 drivers. BAM! is working fine.

So this may well have been a 'feature/bug' if BOINC 7.0.29 that prevented proper communication between BOINC and BAM!

Now back in Fedora 18. OpenCL is now enabled, it is a bit complicated with 64bit Linux OS to make this happen.

However, BOINC 7.0.29 still refuses to connect to BAM!

This is a brand new install of BOINC on a freshly formatted disc.

The ONLY thing I touched was cc_config.xml to add Report Results Immediately, I mean it, this is the ONLY modification of a stock BOINC 7.0.29

NO other files have been Added, Edited, or Deleted

In the absence of anything useful from Willy on this topic (yes to him it is a recurring issue, but not to me, and the previous problems did not seem to have a bearing on my issue), I filed a Bug Report with Red Hat/Fedora explaining the issue to them and pointing out that in Ubuntu, BOINC 7.0.27 (an Ubutu team port) and 7.0.28 (straight download from Berkeley) do not have this problem.

The OS is installed on a freshly formatted disk, BOINC 7.0.29.2 is freshly installed using 'yum install boinc-client boinc-manager'

I was able to develop solutions to issues that Nvidia has with 64 bit Linux that prevented OpenCL/GL apps from running on Fedora and also reported that to them so that this problem may not plague us in the future (at least until we get well past the most recent release for Windows and Unix)

Found part of the answer at bugzilla.redhat.com. This appears to be a recurrent problem with BOINC Manager code. i find evidence of exactly the same issue with BOINC 6.10.58 on Fedora 15 almost 2 years ago. Fedora support went in at that time to correct the BOINC Manager source code, recompile, and post a revised executable.

I have read comments by Willy that indicate that this is an OS problem. Well it appears rarely on Windoze, so it may well appear that way to him. yet the real issue is in the BOINC code, not in the Operating System.

The responsibility for a fix belongs to the BOINC/Fedora support teams, NOT WITH Willy.

I am relatively new to Fedora so my exposure to this issue is EXTREMELY recent, and i had NO KNOWLEDGE of what came before UNTIL TODAY!!

There are two problems reported when BOINC tries to connect to BAM! I have not yet found an answer for the second problem yet.