Bug 539994 - boinc-client SIGABRT when trying to attach project
Summary: boinc-client SIGABRT when trying to attach project
Keywords:
Status: CLOSED DUPLICATE of bug 547860
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: 12
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Milos Jakubicek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-21 21:26 UTC by Dominic Hopf
Modified: 2009-12-22 11:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-22 01:23:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output of boinc when trying to attach a project (15.22 KB, text/plain)
2009-11-21 21:26 UTC, Dominic Hopf
no flags Details
output in the messages tab of boincmgr (3.33 KB, text/plain)
2009-12-21 23:56 UTC, Dominic Hopf
no flags Details

Description Dominic Hopf 2009-11-21 21:26:14 UTC
Created attachment 372797 [details]
output of boinc when trying to attach a project

I'm using a fresh install of Fedora 12 (Constantine) and just wanted to reconfigure my boinc-client for worldcommunitygrid.org. Unfortunately, when trying to attach the project, boinc quits with a SIGABRT every time (so, the issue is fully reproducable) and shows the attached output.

Comment 1 Milos Jakubicek 2009-11-21 22:25:57 UTC
I'll look at this during the next week, currently I have no F12 available because of travelling.

Comment 2 Riku Seppala 2009-12-11 16:24:15 UTC
Update to latest upstream?

Comment 3 Dominic Hopf 2009-12-12 03:00:20 UTC
Current installed versions are:
boinc-client-6.6.37-4.r18632svn.fc12.x86_64
boinc-manager-6.6.37-4.r18632svn.fc12.x86_64

This seems to be the same version as when the crash occurred, according to the backtrace. I've tried again today to attach the project according to the instructions at [1]. Special difference to my first tries is: There are different ways described at [2], the first crashing tries were according to the old way (not sure if I did everything correctly anyway) and finally attaching the project via command line. This was, when boinc-client crashed as described above.
With my tries to reproduce this concerning the instruction at [1] and current way to set up boinc (in fact, just do the /usr/sbin/usermod -G boinc -a username) and then just starting the BOINC Manager from XFCE Menu everything worked without any problem.

I'll give this another try from command line the next days to try reproducing the crash.

Riku is right anyway since the BOINC Manager tells me "A new version of BOINC (6.10.17) is available for your computer."

[1] http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora
[2] http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora#Set_up_your_accounts

Comment 4 Riku Seppala 2009-12-20 10:30:59 UTC
http://boinc.berkeley.edu/trac/wiki/VersionHistory

Looks like there have been several versions released after 6.6.37.

Comment 5 Milos Jakubicek 2009-12-20 11:10:09 UTC
Sorry for the delay, there seem to be several issues after upgrading to F12, I'll release an update in a few days.

Comment 6 Milos Jakubicek 2009-12-21 23:04:51 UTC
I just made some fresh installs of BOINC on F12, attaching to World Community Grid works without problems.

Can you still reproduce this problem?

Looking into your log: where did you modify your boinc data directory? Are you sure it is writable for boinc?

Comment 7 Dominic Hopf 2009-12-21 23:55:50 UTC
I unfortunately can not reproduce the crash mentioned above which caused this bug report. I'm facing problems running boinc anyway. I deleted any configuration and started fresh again, installing boinc-client, then using boincmgr to attach the worldcommuntiygrid project. The messages tab in boincmgr shows the attached output then.

Comment 8 Dominic Hopf 2009-12-21 23:56:43 UTC
Created attachment 379741 [details]
output in the messages tab of boincmgr

Comment 9 Milos Jakubicek 2009-12-22 00:23:07 UTC
Ah...I guess I know where the problem is: do you have the package "ca-certificates" installed? If no, does installing this package solve the problem?

The certificates were formerly packaged as part of curl (requires by boinc) but after they have been split up into the ca-certificates package, there might be an additional requires missing.

Comment 10 Milos Jakubicek 2009-12-22 00:37:23 UTC
Mhm...ignore my previous post, I just managed to reproduce your problem with ca-certificates installed. I'll get back when I find out what's going wrong.

Comment 11 Milos Jakubicek 2009-12-22 01:07:57 UTC
Quoting relevant debugging output:

22-Dec-2009 01:44:05 [---] [http_debug] HTTP_OP::init_post(): https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  About to connect() to grid.worldcommunitygrid.org port 443 (#0)
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:    Trying 198.20.8.241...
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  Connected to grid.worldcommunitygrid.org (198.20.8.241) port 443 (#0)
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  Initializing NSS with certpath: /etc/pki/nssdb
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:    CAfile: /etc/pki/tls/certs/ca-bundle.crt
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:    CApath: none
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  Bad certificate received. Subject = 'CN=grid.worldcommunitygrid.org,OU="Sea Blue, Inc.",O="Sea Blue, Inc.",L=Jasper,ST=GEORGIA,C=US', Issuer = 'CN=Entrust.net Secure Server Certification Authority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US'
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  NSS error -8182
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  Expire cleared
22-Dec-2009 01:44:06 [---] [http_debug] [ID#1] Info:  Closing connection #0
22-Dec-2009 01:44:06 [---] [http_debug] HTTP error: Peer certificate cannot be authenticated with known CA certificates
22-Dec-2009 01:44:10 [World Community Grid] Scheduler request failed: Peer certificate cannot be authenticated with known CA certificates

Since "openssl s_client -host grid.worldcommunitygrid.org -port 443" works fine, I suspect this to be a NSS problem.

Comment 12 Milos Jakubicek 2009-12-22 01:22:01 UTC
This is indeed a NSS problem (bug 547860), a temporary workaround:

As root, run:

1) setup-nsssysinit.sh off

2) service boinc-client restart

Comment 13 Milos Jakubicek 2009-12-22 01:23:47 UTC

*** This bug has been marked as a duplicate of bug 547860 ***

Comment 14 Dominic Hopf 2009-12-22 11:06:13 UTC
This indeed solved it. Thanks very much for your support!


Note You need to log in before you can comment on or make changes to this bug.