Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Okay, system completely locked a short while ago. Contents from journalctl -xef (note- most of this was in red font, so it was BAD) and of course, when I went to see what process 16831 had closed so I do not know what it was:

Apr 08 13:53:13 localhost.localdomain systemd-coredump[18900]: Process 16831 (sssd_kcm) of user 0 dumped core.

                                                           Stack trace of thread 16831:
                                                           #0  0x00007f52e377f750 raise (libc.so.6)
                                                           #1  0x00007f52e3780d31 abort (libc.so.6)
                                                           #2  0x00007f52e3f933ac talloc_abort (libtalloc.so.2)
                                                           #3  0x00007f52e3f92e58 _talloc_free (libtalloc.so.2)
                                                           #4  0x0000555e823a43bb schedule_fd_processing (sssd_kcm)
                                                           #5  0x00007f52e837b02c update_timer (libcurl.so.4)
                                                           #6  0x00007f52e837c9e4 curl_multi_add_handle (libcurl.so.4)
                                                           #7  0x0000555e823a4c43 tcurl_request_send (sssd_kcm)
                                                           #8  0x0000555e823a5508 tcurl_http_send (sssd_kcm)
                                                           #9  0x0000555e823974a9 sec_list_send (sssd_kcm)
                                                           #10 0x0000555e8239796f ccdb_sec_list_send (sssd_kcm)
                                                           #11 0x0000555e823925a2 kcm_ccdb_list_send (sssd_kcm)
                                                           #12 0x0000555e8239d18e kcm_op_get_cache_uuid_list_send (sssd_kcm)
                                                           #13 0x0000555e8239b6f3 kcm_cmd_queue_done (sssd_kcm)
                                                           #14 0x00007f52e41a99c4 tevent_common_loop_immediate (libtevent.so.0)
                                                           #15 0x00007f52e41ae54b epoll_event_loop_once (libtevent.so.0)
                                                           #16 0x00007f52e41acba7 std_event_loop_once (libtevent.so.0)
                                                           #17 0x00007f52e41a8fed _tevent_loop_once (libtevent.so.0)
                                                           #18 0x00007f52e41a920b tevent_common_loop_wait (libtevent.so.0)
                                                           #19 0x00007f52e41acb47 std_event_loop_wait (libtevent.so.0)
                                                           #20 0x00007f52e7cf3763 server_loop (libsss_util.so)
                                                           #21 0x0000555e8238fa97 main (sssd_kcm)
                                                           #22 0x00007f52e376bfea __libc_start_main (libc.so.6)
                                                           #23 0x0000555e8238fc5a _start (sssd_kcm)

-- Subject: Process 16831 (sssd_kcm) dumped core -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Documentation: man:core(5)

-- Process 16831 (sssd_kcm) crashed and dumped core.

-- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Apr 08 13:53:13 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-18877-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'