[Bug 159135] Re: boinc unable to connect to World Community Grid because of missing ca-bundle.crt file

berg berg.foss at gmail.com
Thu Mar 20 23:13:04 UTC 2008


the solution seems enable cacert provider at /etc/ca-certificates.conf and executing
 update-ca-certificates command like said BrodocK  at his comment:

https://bugs.launchpad.net/ubuntu/+source/ca-
certificates/+bug/153625/comments/5


The Boinc site ( http://boinc.berkeley.edu/trac/wiki/ErrorReference ) said:


/*
Scheduler request failed: problem with the SSL CA cert (path? access rights?)

This is a known problem with some ported BOINC releases, especially
certain Linux x64 ports. The reason for the error is that a file (ca-
bundle.crt) was omitted from the release.

If you see this error message in your message log, then you probably
need to apply this fix.

   1. Determine your BOINC data directory. Check the beginning of your
message log. There will be a line near the beginning like this:

       08/06/2007 13:18:00||Data directory: C:\Program Files\BOINC

   2. Download the missing file. - make sure you name the file ca-bundle.crt.
   3. Place the file in your BOINC data directory.
   4. Restart BOINC. The way you do this will depend on your installation. 

Why does this problem only affect WCG, and not other BOINC projects?This
is because WCG is (at the time of writing) the only BOINC project that
requires a secure connection to the server. Other projects permit
falling back to an insecure connection.

 */

The missing file ( I think) is a generated ( update-ca-certificates )
ca-certicate.crt build from many (all ?) providers enabled ( /etc/ca-
certificates.conf )

REFERENCES: 
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/153625
http://boinc.berkeley.edu/trac/wiki/ErrorReference
https://bugs.launchpad.net/ubuntu/+source/esniper/+bug/164264
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/159135

-- 
boinc unable to connect to World Community Grid because of missing ca-bundle.crt file
https://bugs.launchpad.net/bugs/159135
You received this bug notification because you are a member of Debian
BOINC Maintainers, which is subscribed to boinc in ubuntu.



More information about the pkg-boinc-devel mailing list