Description of problem:

I've seen in multiple cases certmonger aborting with core dump lately.

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

certmonger-0.61-3.el6.x86_64

How reproducible:

I cannot reproduce it in deterministic fashion on minimal setup but I've seen it multiple times in large setup.

Steps to Reproduce:
1. Have certmonger running, do something.

Actual results:

Certmonger coredumps.

Expected results:

Certmonger does not coredump.

Additional info:

The backtrace is

Core was generated by `/usr/sbin/certmonger -S -p /var/run/certmonger.pid'.
Program terminated with signal 6, Aborted.
#0  0x00007fd94caac925 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0  0x00007fd94caac925 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007fd94caae105 in abort () at abort.c:92
#2  0x00007fd94efa7af5 in _dbus_abort () at dbus-sysdeps.c:88
#3  0x00007fd94efa39a5 in _dbus_warn_check_failed (
    format=0x7fd94efb0c80 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283
#4  0x00007fd94ef8aaa3 in dbus_connection_get_is_connected (connection=0x0) at dbus-connection.c:2876
#5  0x0000000000415a0a in cm_tdbus_reconnect (ec=0x9cb3b0, timer=<value optimized out>, current_time=..., pvt=0x9cd750) at tdbus.c:463
#6  0x00007fd94eb6fc91 in tevent_common_loop_timer_delay (ev=0x9cb3b0) at ../tevent_timed.c:341
#7  0x00007fd94eb70cbb in epoll_event_loop_once (ev=0x9cb3b0, location=<value optimized out>) at ../tevent_epoll.c:916
#8  0x00007fd94eb6f2e6 in std_event_loop_once (ev=0x9cb3b0, location=0x42ab1c "main.c:287") at ../tevent_standard.c:112
#9  0x00007fd94eb6b49d in _tevent_loop_once (ev=0x9cb3b0, location=0x42ab1c "main.c:287") at ../tevent.c:530
#10 0x00000000004075bd in main (argc=<value optimized out>, argv=0x7fff48661d88) at main.c:287
(gdb) quit