Version-Release number of selected component: rsyslog-7.4.2-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /sbin/rsyslogd -n crash_function: journal_file_move_to_object executable: /usr/sbin/rsyslogd kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #0 journal_file_move_to_object at ../src/journal/journal-file.c:439 #1 generic_array_get at ../src/journal/journal-file.c:1454 #2 journal_file_next_entry at ../src/journal/journal-file.c:1991 #3 next_with_matches at ../src/journal/sd-journal.c:814 #4 next_beyond_location at ../src/journal/sd-journal.c:836 #5 real_journal_next at ../src/journal/sd-journal.c:895 #6 sd_journal_next at ../src/journal/sd-journal.c:931 #7 runInput at imjournal.c:533 #8 thrdStarter at ../threads.c:212
Created attachment 858554 [details] File: backtrace
Created attachment 858555 [details] File: cgroup
Created attachment 858556 [details] File: core_backtrace
Created attachment 858557 [details] File: dso_list
Created attachment 858558 [details] File: environ
Created attachment 858559 [details] File: exploitable
Created attachment 858560 [details] File: limits
Created attachment 858561 [details] File: maps
Created attachment 858562 [details] File: open_fds
Created attachment 858563 [details] File: proc_pid_status
Created attachment 858564 [details] File: var_log_messages
Given that rsyslog calls a function that takes a single opaque argument [1], I'm inclined to think this is a bug in systemd. [1] sd_journal_next(sd_journal* j);
This range seems to be mapped. Is is possible that the file (/var/log/journal/c83a8a098011452b87b04623eed08648/system~) has been modified at the same time by something else? Alternatively, was the system under memory pressure?
I wasn't fiddling with files in var log (so it would have had to have been a different program if that is the case). Also, the system has 4GB so it shouldn't have that much memory pressure.
*** Bug 1062892 has been marked as a duplicate of this bug. ***
*** Bug 1089103 has been marked as a duplicate of this bug. ***
*** Bug 1105881 has been marked as a duplicate of this bug. ***
*** Bug 974331 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1047625 ***
*** Bug 1177933 has been marked as a duplicate of this bug. ***
*** Bug 1163636 has been marked as a duplicate of this bug. ***