Crash in journal_file_move_to_object

Similar reports
Problem #268
Component
systemd
Last affected version
0:219-78.el7_9.9
Executable
/usr/lib/systemd/systemd-journald
Error name
SIGABRT 6
First occurrence
2021-03-04
Last occurrence
2024-11-03
Unique reports
44
Quality
-26

Statistics

Operating system Unique / Total count
CentOS 7 44 / 1,443
Operating system Count
CentOS 7 1,443
Architecture Count
x86_64 1,443
Related packages Count
systemd 1,454
 0:219-62.el7 1,263
 0:219-78.el7_9.3 48
 0:219-78.el7_9.7 27
 0:219-78.el7_9.5 16
 0:219-67.el7_7.2 13
 0:219-78.el7_9.9 11
 0:219-73.el7_8.9 11
 0:219-62.el7_6.5 10
 0:219-57.el7 10
 0:219-78.el7 9
 0:219-62.el7_6.9 9
 0:219-57.el7_5.3 7
 0:219-67.el7_7.4 5
 0:219-30.el7 4
 0:219-62.el7_6.6 4
 0:219-78.el7_9.2 4
 0:219-62.el7_6.2 1
 0:219-42.el7 1
 0:219-67.el7_7.3 1
libgcc 1,451
 0:4.8.5-44.el7 1,284
 0:4.8.5-36.el7 89
 0:4.8.5-39.el7 53
 0:4.8.5-36.el7_6.1 7
 0:4.8.5-28.el7_5.1 7
 0:4.8.5-36.el7_6.2 5
 0:4.8.5-11.el7 4
 0:4.8.5-28.el7 1
 0:4.8.5-16.el7 1
libattr 1,448
 0:2.4.46-13.el7 1,442
 0:2.4.46-12.el7 6
Show more… (10)
lz4 1,448
 0:1.7.5-2.el7 1,303
 0:1.8.3-1.el7 113
 0:1.7.5-3.el7 32
glibc 1,447
 0:2.17-292.el7 1,190
 0:2.17-260.el7 90
 0:2.17-326.el7_9 50
 0:2.17-324.el7_9 36
 0:2.17-317.el7 18
 0:2.17-307.el7.1 18
 0:2.17-325.el7_9 9
 0:2.17-222.el7 9
 0:2.17-260.el7_6.6 9
 0:2.17-260.el7_6.4 6
 0:2.17-323.el7_9 5
 0:2.17-260.el7_6.5 4
 0:2.17-260.el7_6.3 1
 0:2.17-326.el7_9.3 1
 0:2.17-196.el7 1
libgcrypt 1,447
 0:1.5.3-14.el7 1,438
 0:1.5.3-13.el7_3.1 5
 0:1.5.3-12.el7_1.1 4
libacl 1,447
 0:2.2.51-14.el7 1,317
 0:2.2.51-15.el7 120
 0:2.2.51-12.el7 10
pcre 1,447
 0:8.32-17.el7 1,437
 0:8.32-15.el7_2.1 9
 0:8.39-2.el7.centos.fuzzyrpm 1
libselinux 1,446
 0:2.5-14.1.el7 1,313
 0:2.5-15.el7 120
 0:2.5-12.el7 9
 0:2.5-6.el7 4
xz-libs 1,443
 0:5.2.2-1.el7 1,395
 0:5.2.2-2.el7_9 48
libgpg-error 1,443
 0:1.12-3.el7 1,442
 0:1.31-1.el7.fuzzyrpm 1
libv4l 1
 0:1.10.0-1.el7.centos.fuzzyrpm 1
libjpeg-turbo 1
 0:2.0.4-1.el7.fuzzyrpm 1

Packages names with count less than the total count of reports are most probably not the cause of the problem.

History

Daily:

Weekly:

Monthly:

History

Daily:

Weekly:

Monthly:


Backtrace

Frame # Function Binary Source or offset Line
1
journal_file_move_to_object
/usr/lib/systemd/systemd-journald 0x14792
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
2
link_entry_into_array
/usr/lib/systemd/systemd-journald 0x15d28
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
3
journal_file_append_entry_internal
/usr/lib/systemd/systemd-journald 0x161ae
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
4
journal_file_append_entry
/usr/lib/systemd/systemd-journald 0x16ffa
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
5
dispatch_message_real
/usr/lib/systemd/systemd-journald 0xc208
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
6
server_dispatch_message
/usr/lib/systemd/systemd-journald 0xea9f
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
7
stdout_stream_log
/usr/lib/systemd/systemd-journald 0x371d6
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
8
stdout_stream_line
/usr/lib/systemd/systemd-journald 0x37685
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
9
stdout_stream_scan
/usr/lib/systemd/systemd-journald 0x37be3
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
10
stdout_stream_process
/usr/lib/systemd/systemd-journald 0x37f32
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
11
source_dispatch
/usr/lib/systemd/systemd-journald 0x24ca0
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
12
sd_event_dispatch
/usr/lib/systemd/systemd-journald 0x25a6a
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-
13
main
/usr/lib/systemd/systemd-journald 0x6c7d
Build id: 877e8b8ffb24bf1a371e55967ba4208fb4f758a9 		-