Bug 1163541

Summary: [abrt] certmonger: _dbus_abort(): getcert killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jamie Lennox <jlennox>
Component: certmongerAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: mharmsen, nalin, nkinder
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9393dd5660399c1cfb115e1e037baddbc7b02d31
Whiteboard: abrt_hash:71ccd99a21b239270e6c6c849330d4cb9f680231
Fixed In Version: certmonger-0.76.8-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-17 01:28:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jamie Lennox 2014-11-13 01:33:20 UTC
Description of problem:
Running getcert status after installing.

Version-Release number of selected component:
certmonger-0.75.14-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        getcert status
crash_function: _dbus_abort
executable:     /usr/bin/getcert
kernel:         3.16.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 _dbus_abort at dbus-sysdeps.c:94
 #3 _dbus_warn_check_failed at dbus-internals.c:290
 #4 dbus_message_new_method_call at dbus-message.c:1263
 #5 prep_req at getcert.c:279
 #6 query_rep at getcert.c:358
 #7 status at getcert.c:3058
 #9 _start

Comment 1 Jamie Lennox 2014-11-13 01:33:29 UTC
Created attachment 956894 [details]
File: backtrace

Comment 2 Jamie Lennox 2014-11-13 01:33:32 UTC
Created attachment 956895 [details]
File: cgroup

Comment 3 Jamie Lennox 2014-11-13 01:33:35 UTC
Created attachment 956896 [details]
File: core_backtrace

Comment 4 Jamie Lennox 2014-11-13 01:33:38 UTC
Created attachment 956897 [details]
File: dso_list

Comment 5 Jamie Lennox 2014-11-13 01:33:41 UTC
Created attachment 956898 [details]
File: environ

Comment 6 Jamie Lennox 2014-11-13 01:33:44 UTC
Created attachment 956899 [details]
File: limits

Comment 7 Jamie Lennox 2014-11-13 01:33:48 UTC
Created attachment 956900 [details]
File: maps

Comment 8 Jamie Lennox 2014-11-13 01:33:49 UTC
Created attachment 956901 [details]
File: open_fds

Comment 9 Jamie Lennox 2014-11-13 01:33:52 UTC
Created attachment 956902 [details]
File: proc_pid_status

Comment 10 Jamie Lennox 2014-11-13 01:33:58 UTC
Created attachment 956903 [details]
File: var_log_messages

Comment 11 Jamie Lennox 2014-11-13 01:35:11 UTC
Description of problem:

On a new Fedora 20 (cloud) virtual machine, with a fresh install of certmaster and certmonger calling getcert status and certmaster-getcert status results in a failures with message:


process 25227: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1262.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

Version-Release number of selected component (if applicable):

certmonger-0.75.14-1.fc20.x86_64
certmaster-0.28-7.fc20.noarch
dbus-libs-1.6.12-9.fc20.x86_64
dbus-1.6.12-9.fc20.x86_64

How reproducible:

It failed on my personal machine and so i tried it from scratch on an up to date vm image and got the same problem.

Steps to Reproduce:
1. sudo yum install certmonger certmaster
2. sudo systemctl start certmaster
3. sudo systemctl start certmonger
4. sudo getcert status

Actual results:

process 25227: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1262.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

Expected results:

A status output, in this case it's probably empty. 

Additional info:

Comment 12 Jamie Lennox 2014-11-13 01:35:57 UTC
*** Bug 1163539 has been marked as a duplicate of this bug. ***

Comment 13 Nalin Dahyabhai 2014-11-13 16:00:51 UTC
The command was incorrectly assuming that information for locating the particular request would be specified, and what you're seeing is what would happen when that assumption was proved wrong.

It should be fixed in 0.76 and later.  If you can verify that the current test update (https://admin.fedoraproject.org/updates/certmonger-0.76.7-1.fc20) fixes it, I'd appreciate it.

Thanks!

Comment 14 Jamie Lennox 2014-11-17 01:28:21 UTC
Ok, that fixes the crash. 

Ideally it would produce a usage message, like for example if you do getcert request with no arguments it prints the arguments it expects. I was obviously using the command incorrectly (and it's not what i wanted anyway) but the message doesn't give me any further details on what i should do.

Comment 15 Nalin Dahyabhai 2014-11-17 19:23:41 UTC
(In reply to Jamie Lennox from comment #14)
> Ok, that fixes the crash. 
> 
> Ideally it would produce a usage message, like for example if you do getcert
> request with no arguments it prints the arguments it expects.

Agreed, and that'd be consistent with other commands like "list", too.  This'll be fixed in 0.76.8 and later.

Comment 16 Fedora Update System 2014-11-18 17:04:44 UTC
certmonger-0.76.8-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2014-14948/certmonger-0.76.8-1.fc20

Comment 17 Fedora Update System 2014-12-03 01:02:51 UTC
certmonger-0.76.8-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.