systemd-journald dumps core *very* often. After it does that, all kinds of services start to fail. This really quickly takes out any active GDM session. After everything fails, even console login is a problem. Feb 19 08:15:02 bkor systemd[1]: systemd-journald.service: main process exited, code=dumped, status=11 a bit later everything starts failing: Feb 19 08:37:48 bkor NetworkManager[15580]: <warn> disconnected by the system bus. Feb 19 08:37:48 bkor NetworkManager[15580]: <info> caught signal 15, shutting down normally. Feb 19 08:37:48 bkor NetworkManager[15580]: <warn> quit request received, terminating... Feb 19 08:37:48 bkor systemd[1]: accounts-daemon.service: main process exited, code=exited, status=1 Feb 19 08:37:48 bkor systemd[1]: Unit accounts-daemon.service entered failed state. Feb 19 08:37:48 bkor systemd[1]: systemd-logind.service: main process exited, code=exited, status=1 Feb 19 08:37:48 bkor systemd[1]: Unit systemd-logind.service entered failed state. GDM starts crashing, etc. I was logged in, but I guess I was thrown back to GDM. Stacktrace (core file is in: /var/lib/systemd/coredump/core.systemd-journald): $ gdb --core=core.systemd-journald /lib/systemd/systemd-journald GNU gdb (GDB) 7.3.50.20110722-4.mga2 (Mageia release 2) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /lib/systemd/systemd-journald...Reading symbols from /usr/lib/debug/lib/systemd/systemd-journald.debug...done. done. warning: core file may not match specified executable file. [New LWP 9736] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/lib/systemd/systemd-journald'. Program terminated with signal 11, Segmentation fault. #0 journal_file_append_entry (f=0x19db610, ts=0x7fffdfa3dc00, iovec=<optimized out>, n_iovec=20, seqnum=0x7fffdfa3e0b0, ret=0x0, offset=0x0) at src/journal/journal-file.c:1029 1029 xor_hash ^= le64toh(o->data.hash); (gdb) thread apply all bt Thread 1 (Thread 0x7f7784754740 (LWP 9736)): #0 journal_file_append_entry (f=0x19db610, ts=0x7fffdfa3dc00, iovec=<optimized out>, n_iovec=20, seqnum=0x7fffdfa3e0b0, ret=0x0, offset=0x0) at src/journal/journal-file.c:1029 #1 0x000000000040722c in dispatch_message_real (s=0x7fffdfa3e080, iovec=0x7fffdfa3de40, n=20, m=23, ucred=<optimized out>, tv=<optimized out>) at src/journal/journald.c:589 #2 0x00000000004048a1 in process_syslog_message (tv=0x7fffdfa3eaf0, ucred=0x7fffdfa3eb10, buf=0x19d99ab "pam_tcb(crond:session): Session closed for olav", s=0x7fffdfa3e080) at src/journal/journald.c:1057 #3 process_event (ev=0x7fffdfa3e010, s=0x7fffdfa3e080) at src/journal/journald.c:2162 #4 main (argc=<optimized out>, argv=<optimized out>) at src/journal/journald.c:2706
Assignee: bugsquad => mageia
*** Bug 4602 has been marked as a duplicate of this bug. ***
CC: (none) => eeeemail
Blocks: (none) => 2120Source RPM: (none) => systemd
According to Kay upstream, there are a couple people reporting this but so far no full fix, tho' this result might be helpful to point in the right direction....
Do you want more similar stacktraces? It crashes at least once per day, requiring a restart. Just now: (gdb) thread apply all bt Thread 1 (Thread 0x7f495805e740 (LWP 325)): #0 journal_file_append_entry (f=0xc8acc0, ts=0x7fff280d9690, iovec=<optimized out>, n_iovec=18, seqnum=0x7fff280d9b40, ret=0x0, offset=0x0) at src/journal/journal-file.c:1029 #1 0x000000000040722c in dispatch_message_real (s=0x7fff280d9b10, iovec=0x7fff280d98d0, n=18, m=23, ucred=<optimized out>, tv=<optimized out>) at src/journal/journald.c:589 #2 0x00000000004048a1 in process_syslog_message (tv=0x7fff280da580, ucred=0x7fff280da5a0, buf=0xc7d1f1 "input_userauth_request: invalid user root [preauth]", s=0x7fff280d9b10) at src/journal/journald.c:1057 #3 process_event (ev=0x7fff280d9aa0, s=0x7fff280d9b10) at src/journal/journald.c:2162 #4 main (argc=<optimized out>, argv=<optimized out>) at src/journal/journald.c:2706
finally something not related for users.. postfix thing. Also, it just made GDM exist. I could still login again this time. Thread 1 (Thread 0x7f26ed93c740 (LWP 336)): #0 journal_file_append_entry (f=0x15b7dc0, ts=0x7fff138247a0, iovec=<optimized out>, n_iovec=18, seqnum=0x7fff13824c50, ret=0x0, offset=0x0) at src/journal/journal-file.c:1029 #1 0x000000000040722c in dispatch_message_real (s=0x7fff13824c20, iovec=0x7fff138249e0, n=18, m=23, ucred=<optimized out>, tv=<optimized out>) at src/journal/journald.c:589 #2 0x00000000004048a1 in process_syslog_message (tv=0x7fff13825690, ucred=0x7fff138256b0, buf=0x15a51fa "4686A50093F: client=menubar.gnome.org[209.132.180.169]", s=0x7fff13824c20) at src/journal/journald.c:1057 #3 process_event (ev=0x7fff13824bb0, s=0x7fff13824c20) at src/journal/journald.c:2162 #4 main (argc=<optimized out>, argv=<optimized out>) at src/journal/journald.c:2706
A new backtrace! This could be bogus due to new systemd (meaning: -debug symbols do not match the crash). Thread 1 (LWP 322): #0 0x000000000040d99c in journal_file_link_entry_item (i=<optimized out>, offset=9964672, o=0x1811220, f=0x7fff38a0f5c0) at src/journal/journal-file.c:890 #1 journal_file_link_entry (offset=9964672, o=0xf, f=0x7fff38a0f5c0) at src/journal/journal-file.c:933 #2 journal_file_append_entry_internal (f=0x7fff38a0f5c0, ts=<optimized out>, xor_hash=<optimized out>, items=<optimized out>, n_items=<optimized out>, seqnum=<optimized out>, ret=0x5822468, offset=0xd9da1909ddb3030b) at src/journal/journal-file.c:970 #3 0x22dd2bd17d45e480 in ?? () #4 0x0000000005822468 in ?? () #5 0xd9da1909ddb3030b in ?? () #6 0x0000000001810d30 in ?? () #7 0x4632a8157847f138 in ?? () #8 0x0000000001810d78 in ?? () #9 0xd4cd91af1fc546a2 in ?? () #10 0x0000000001810dc0 in ?? () #11 0x5f9f085f88ae7eab in ?? () #12 0x0000000001810e10 in ?? () #13 0x115eb79fa4cd5582 in ?? () #14 0x0000000001810e70 in ?? () #15 0x1056308b4e872a52 in ?? () #16 0x0000000001810ee0 in ?? () #17 0x94cba6ed682b6175 in ?? () #18 0x0000000001810f48 in ?? () #19 0x309fa50de8ec2b8d in ?? () #20 0x0000000000000012 in ?? () #21 0x0000000000410888 in cg_get_by_pid (controller=<optimized out>, pid=<optimized out>, path=<optimized out>) at src/cgroup-util.c:841 #22 0x00007fff38a0f710 in ?? () #23 0x00000000004108cd in cg_get_by_pid (controller=0x1810f48 <Address 0x1810f48 out of bounds>, pid=<optimized out>, path=0x309fa50de8ec2b8d) at src/cgroup-util.c:809 #24 0x0000000000000000 in ?? ()
Should hopefully be fixed in latest systemd. Please reopen (or just moan upstream!) if this reoccurs.
Status: NEW => RESOLVEDResolution: (none) => FIXED