Version-Release number of selected component: systemd-197-1.fc18.2 Additional info: backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: read_secpar executable: /usr/lib/systemd/systemd-journald kernel: 3.8.8-202.fc18.x86_64 uid: 0 ureports_counter: 1 var_log_messages: Apr 28 23:09:00 segulix kernel: [173797.838903] systemd-journal[464]: segfault at 737562640033 ip 00007feb9ab9d940 sp 00007fffc6874958 error 4 in systemd-journald[7feb9ab97000+2c000] Truncated backtrace: Thread no. 1 (5 frames) #0 read_secpar at src/journal/fsprg.c:331 #1 FSPRG_GetEpoch at src/journal/fsprg.c:333 #2 journal_file_fsprg_need_evolve at src/journal/journal-authenticate.c:133 #3 journal_file_maybe_append_tag at src/journal/journal-authenticate.c:217 #4 server_maybe_append_tags at src/journal/journald-server.c:1450
Created attachment 741284 [details] File: backtrace
Created attachment 741285 [details] File: cgroup
Created attachment 741286 [details] File: core_backtrace
Created attachment 741287 [details] File: dso_list
Created attachment 741288 [details] File: environ
Created attachment 741289 [details] File: limits
Created attachment 741290 [details] File: maps
Created attachment 741291 [details] File: open_fds
Created attachment 741292 [details] File: proc_pid_status
I'm pretty sure that this is a duplicate, because of the tell-tale sign: both runtime and system journals are closed, and no fds are open, so there is no journal file to do operations on. *** This bug has been marked as a duplicate of bug 890463 ***