Why does certmonger Segfault when started?
Issue
- Why does certmonger Segfault when started?
- There are quite a few of the following messages observed in
/var/log/messages:
kernel: sbridge: HANDLING MCE MEMORY ERROR
kernel: CPU 0: Machine Check Exception: 0 Bank 5: 8c00004000010091
kernel: TSC 0 ADDR 132c8c0 MISC 20404c4c86 PROCESSOR 0:206d7 TIME 1402299473 SOCKET 0 APIC 0
kernel: EDAC MC0: CE row 1, channel 0, label "CPU_SrcID#0_Channel#1_DIMM#0": 1 Unknown error(s): memory read on FATAL area : cpu=0 Err=0001:0091 (ch=1), addr = 0x0132c8c0 => socket=0, Channel=1(mask=2), rank=1
- All memory modules (except Main Board) were repaired immediately by the engineer. Afterwards when checking mcelog, there are no hardware errors observed but
certmongerfails to start and displays the following error:
"Starting certmonger: /bin/bash: line 1: 3181 Segmentation fault /usr/sbin/certmonger -S -p /var/run/certmonger.pid
[FAILED]"
Environment
- Red Hat Enterprise Linux 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
