Description of problem: While applying queued updates this error was reported: Cleanup : btrfs-progs-0.20.rc1.20130917git194aa4a-1.fc19.x86_64 202/203 Cleanup : mesa-libxatracker-9.2.3-1.20131114.fc19.x86_64 203/203 Unexpected error CalledProcessError: Command '/bin/systemctl start certmonger.service' returned non-zero exit status 1 Verifying : ibus-gtk2-1.5.4-2.fc19.x86_64 1/203 Verifying : nspr-4.10.2-1.fc19.x86_64 2/203 Verifying : mesa-libglapi-9.2.4-1.20131128.fc19.x86_64 3/203 Version-Release number of selected component: certmonger-0.67-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/sbin/certmonger -S -p /var/run/certmonger.pid -n crash_function: strcmp executable: /usr/sbin/certmonger kernel: 3.11.8-200.fc19.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 strcmp at ../sysdeps/x86_64/strcmp.S:212 #1 cm_store_get_all_entries at store-files.c:1321 #2 cm_init at cm.c:85
Created attachment 836454 [details] File: backtrace
Created attachment 836455 [details] File: cgroup
Created attachment 836456 [details] File: core_backtrace
Created attachment 836457 [details] File: dso_list
Created attachment 836458 [details] File: environ
Created attachment 836459 [details] File: exploitable
Created attachment 836460 [details] File: limits
Created attachment 836461 [details] File: maps
Created attachment 836462 [details] File: open_fds
Created attachment 836463 [details] File: proc_pid_status
Created attachment 836464 [details] File: var_log_messages
After rebooting the service fails to start: [dean@ipa1 ~]$ systemctl status certmonger.service certmonger.service - Certificate monitoring and PKI enrollment Loaded: loaded (/usr/lib/systemd/system/certmonger.service; enabled) Active: failed (Result: core-dump) since Fri 2013-12-13 12:47:43 CST; 1min 49s ago Process: 564 ExecStart=/usr/sbin/certmonger -S -p /var/run/certmonger.pid -n $OPTS (code=dumped, signal=SEGV) [dean@ipa1 ~]$
Apparently certmonger has not changed as it was installed from the fedora repository. However, I know that freeipa-server was updated during this batch. [dean@ipa1 ~]$ yum list installed certmonger* Loaded plugins: langpacks, refresh-packagekit Installed Packages certmonger.x86_64 0.67-1.fc19 @local-fedora [dean@ipa1 ~]$ yum list installed freeipa-server* Loaded plugins: langpacks, refresh-packagekit Installed Packages freeipa-server.x86_64 3.3.3-2.fc19 @local-updates [dean@ipa1 ~]$
This should be fixed by commit 7b6165792f782f1be25823dc618e0b9a659116db in the run-up to 0.69. I'll prep a test update.
certmonger-0.69-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/certmonger-0.69-1.fc19
certmonger-0.69-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/certmonger-0.69-1.fc20
certmonger-0.69-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/certmonger-0.69-1.fc18
Package certmonger-0.69-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing certmonger-0.69-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23360/certmonger-0.69-1.fc20 then log in and leave karma (feedback).
The Fedora 19 package has been updated and certmonger now starts. Thank you.
certmonger-0.70-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
certmonger-0.71.2-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/certmonger-0.71.2-1.fc19
certmonger-0.71.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/certmonger-0.71.2-1.fc20
certmonger-0.71.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
certmonger-0.71.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.