| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Scheduler request failed: problem with the SSL CA cert (path? access rights?) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The post's subject is part of the group of messages that I have pasted at the very bottom of this post.
I have two Linux machines here one RH Fedora 6 and one Fedora 7, both have boinc 5.8.11. Both have been running as a service (one a year, the other 4 weeks) and the GUI manager works on both. I have been able to attach to Seti and Predictor projects without a hitch. I also can run the command line tool to get various displays and things. Both of them have the same problem. I bashed away at various items in https://secure.worldcommunitygrid.org/forums/wcg/viewthread?thread=15177 and have not found a resolution as of yet. The big ones in the old post seemed to focus on: 1. The certificate file was included with my installation file and is in the same dir as the boinc executables. I tried replacing it with no joy (they looked to be the same and I didn't expect this to work). 2. The xml file for the project shows my account key as the <authenticator> after the attempted attach. It is the same account key that was emailed to me when I first signed up with WCG using a Windows machine some time ago (the WinXP machine is and has been working for some time). Thanks, Mac Here are the messages from the attempt attach: Thu 19 Jul 2007 02:24:06 PM CDT||Fetching configuration file from http://www.worldcommunitygrid.org/get_project_config.php Thu 19 Jul 2007 02:24:37 PM CDT|World Community Grid|Master file download succeeded Thu 19 Jul 2007 02:24:42 PM CDT|World Community Grid|Sending scheduler request: Project initialization Thu 19 Jul 2007 02:24:42 PM CDT|World Community Grid|Requesting 1 seconds of new work Thu 19 Jul 2007 02:24:48 PM CDT||Project communication failed: attempting access to reference site Thu 19 Jul 2007 02:24:48 PM CDT|World Community Grid|Scheduler request failed: problem with the SSL CA cert (path? access rights?) Thu 19 Jul 2007 02:24:48 PM CDT|World Community Grid|Deferring communication for 1 min 0 sec Thu 19 Jul 2007 02:24:48 PM CDT|World Community Grid|Reason: scheduler request failed Thu 19 Jul 2007 02:24:54 PM CDT||Access to reference site succeeded - project servers may be temporarily down. Thu 19 Jul 2007 02:25:49 PM CDT|World Community Grid|Sending scheduler request: Project initialization Thu 19 Jul 2007 02:25:49 PM CDT|World Community Grid|Requesting 1 seconds of new work Thu 19 Jul 2007 02:25:51 PM CDT||Project communication failed: attempting access to reference site Thu 19 Jul 2007 02:25:51 PM CDT|World Community Grid|Scheduler request failed: problem with the SSL CA cert (path? access rights?) Thu 19 Jul 2007 02:25:51 PM CDT|World Community Grid|Deferring communication for 1 min 0 sec Thu 19 Jul 2007 02:25:51 PM CDT|World Community Grid|Reason: scheduler request failed Thu 19 Jul 2007 02:25:52 PM CDT||Access to reference site succeeded - project servers may be temporarily down. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Please read the FAQ: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=14222
----------------------------------------edit: note that the ca-bundle.crt file needs to be in the data directory, NOT the executable directory. The data directory is listed at agent startup (top of the log). [Edit 1 times, last edit by Former Member at Jul 19, 2007 10:19:53 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You know, I noticed that post linked out of the long-winded one I referenced. I even "read" it. I saw it early in the search and didn't connect it with what I was seeing for files.
And it just didn't sink in .... DATA directory! Give me a dope slap and send me on my way. Thanks for being merciful. Just as a small suggestion. I went back thru register/download/install pages on the main site. I didn't see the cert file mentioned. Could help, maybe? Maybe a permanent read-only post on how to install boinc and/or attach to WCG with a mention of the cert file by file name and the error message text as a "you will get this if you don't" sort of help. Then it could searched for and be all together. Anyway, thanks. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you get BOINC from an official source (WCG or Berkeley) then the file is included already. This problem so far is mostly with 3rd party ports, where the port maintainer has never attached to WCG.
The whole issue has been fixed for the next version of BOINC. Glad you got your problem fixed. The other thread you were referencing had a multiplicity of problems apart from this one. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Actually, I did get the Boinc package from the Boinc site. It did include the cert file as part of the package. It's just that there isn't anywhere (except for searching posts) that tells a person what to do with the file. So, I just left it with the executables for a year plus. And the other projects that don't SSL don't care.
If you mean the issue has been fixed in the next version cause the cert file is included in the BOinc package, it didn't help me. I'd still suggest further documentation with the install page and in the forum. If you mean that it's fixed in the next version cause it's handled in a much more transparent fashion, yippee! Just trying to be helpful by making sure it's clear for the next poor sod like me :) Thanks again. Mac |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
No, it's fixed in the next version in a much more opaque fashion....
----------------------------------------we worked out a source tweak that means all those 3rd party ports don't need to include the file (it's packaged with libCurl instead). Here's the bug link: http://boinc.berkeley.edu/trac/ticket/326 Your situation is a little different. Few people are capable of setting up BOINC correctly as a service just using the official package, as you did. But hopefully the official package will be improved soon also - a hassle-free installation is near the top of the priority list at the moment, and Linux installation is particularly painful right now. I expect BOINC will merge their installer package with some of the better ports. sudo apt-get install boinc-client is a much easier way of installing BOINC that the trouble you must have gone to. [Edit 1 times, last edit by Former Member at Jul 19, 2007 11:55:27 PM] |
||
|
|
|