Crash in journal_file_find_data_object_with_hash

Similar reports
Problem #496609
Component
systemd
Last affected version
0:219-78.el7_9.9.tuxcare.els1
Executable
/usr/lib/systemd/systemd-journald
Error name
SIGABRT 6
First occurrence
2021-03-05
Last occurrence
2026-11-17
Unique reports
69
Quality
-18

Statistics

Operating system Unique / Total count
CentOS 7 69 / 6,413
Operating system Count
CentOS 7 6,413
Architecture Count
x86_64 6,413
Related packages Count
systemd 6,433
 0:219-62.el7 1,914
 0:219-78.el7_9.3 987
 0:219-78.el7_9.7 848
 0:219-78.el7_9.9 586
 0:219-78.el7_9.5 402
 0:219-67.el7_7.4 309
 0:219-67.el7_7.2 268
 0:219-78.el7 232
 0:219-73.el7_8.9 116
 0:219-78.el7_9.2 110
 0:219-62.el7_6.6 90
 0:219-57.el7 78
 0:219-57.el7_5.1 71
 0:219-67.el7_7.1 56
 0:219-73.el7_8.8 55
 0:219-62.el7_6.9 48
 0:219-67.el7 46
 0:219-73.el7.1 46
 0:219-57.el7_5.3 42
 0:219-62.el7_6.5 34
 0:219-67.el7_7.3 34
 0:219-73.el7_8.6 27
 0:219-62.el7_6.7 21
 0:219-73.el7_8.5 5
 0:219-62.el7_6.3 5
 0:219-78.el7_9.9.tuxcare.els1 2
 0:219-62.el7_6.2 1
libattr 6,172
 0:2.4.46-13.el7 6,113
 0:2.4.46-12.el7 59
libacl 6,143
 0:2.2.51-15.el7 3,326
 0:2.2.51-14.el7 2,807
 0:2.2.51-12.el7 10
Show more… (15)
libselinux 6,126
 0:2.5-15.el7 3,410
 0:2.5-14.1.el7 2,572
 0:2.5-12.el7 144
lz4 6,125
 0:1.8.3-1.el7 3,101
 0:1.7.5-2.el7 2,344
 0:1.7.5-3.el7 675
 0:1.8.3-1.el7_7 3
 0:1.8.3-1.el7.tuxcare.els1 2
glibc 6,124
 0:2.17-292.el7 1,970
 0:2.17-326.el7_9 1,425
 0:2.17-325.el7_9 600
 0:2.17-324.el7_9 459
 0:2.17-323.el7_9 317
 0:2.17-317.el7 266
 0:2.17-326.el7_9.3 248
 0:2.17-307.el7.1 233
 0:2.17-260.el7 211
 0:2.17-222.el7 170
 0:2.17-260.el7_6.5 91
 0:2.17-260.el7_6.6 62
 0:2.17-260.el7_6.3 24
 0:2.17-322.el7_9 23
 0:2.17-260.el7_6.4 18
 0:2.17-326.el7_9.3.tuxcare.els1 2
 0:2.22-3.fc23 2
 0:2.28-225.el8 1
 0:2.17-196.el7 1
 0:2.17-196.el7_4.2 1
xz-libs 6,124
 0:5.2.2-1.el7 4,510
 0:5.2.2-2.el7_9 1,614
libgcrypt 6,116
 0:1.5.3-14.el7 6,108
 0:1.5.6-1.0.cf.rhel7 4
 0:1.5.3-14.el7.tuxcare.els1 2
 0:1.5.3-12.el7_1.1 2
libgpg-error 6,115
 0:1.12-3.el7 6,111
 0:1.42-3.0.cf.rhel7 4
libgcc 6,109
 0:4.8.5-44.el7 5,029
 0:4.8.5-39.el7 508
 0:4.8.5-36.el7 209
 0:4.8.5-36.el7_6.2 154
 0:4.8.5-28.el7_5.1 132
 0:4.8.5-36.el7_6.1 30
 0:4.8.5-28.el7 28
 0:4.8.5-44.0.3.el7 15
 0:5.1.1-4.fc23 2
 0:8.5.0-4.el8_5 1
 0:4.8.5-16.el7_4.2 1
pcre 5,992
 0:8.32-17.el7 5,991
 0:8.32-15.el7_2.1 1
pam 4
 0:1.1.8-23.el7 2
 0:1.1.8-22.el7 2
audit-libs 4
 0:2.8.5-4.el7 2
 0:2.8.1-3.el7 2
CylancePROTECT 4
 0:3.0.1005-735 4
gcc 2
 0:5.4.0-1.el7 2
libcap-ng 2
 0:0.7.5-4.el7 2
libstdc++ 2
 0:4.8.5-44.el7 2
intel-inspector-2019-cli 1
 0:2019.5-602103 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_find_data_object_with_hash
/usr/lib/systemd/systemd-journald 0x151c0
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
2
journal_file_append_data
/usr/lib/systemd/systemd-journald 0x1547c
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
3
journal_file_append_entry
/usr/lib/systemd/systemd-journald 0x16f5c
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
4
dispatch_message_real
/usr/lib/systemd/systemd-journald 0xc208
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
5
server_dispatch_message
/usr/lib/systemd/systemd-journald 0xea9f
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
6
server_read_dev_kmsg
/usr/lib/systemd/systemd-journald 0x75ea
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
7
source_dispatch
/usr/lib/systemd/systemd-journald 0x24c80
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
8
sd_event_dispatch
/usr/lib/systemd/systemd-journald 0x25a4a
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-
9
main
/usr/lib/systemd/systemd-journald 0x6c7d
Build id: d2cb77d5e2c12b1097dcd4cbdd2af0e88efe2317
-