Bug 1663470 - [abrt] systemd: log_assert_failed_realm(): systemd-resolved killed by SIGABRT
Summary: [abrt] systemd: log_assert_failed_realm(): systemd-resolved killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7655b67d63d5eebabe13a440c1f...
: 1659482 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 12:42 UTC by Markus Linnala
Modified: 2019-11-27 23:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 23:25:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.55 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: cgroup (338 bytes, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: core_backtrace (3.89 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: cpuinfo (1.11 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: dso_list (4.22 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: environ (376 bytes, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: limits (1.29 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: machineid (135 bytes, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: maps (24.79 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: mountinfo (7.35 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: open_fds (2.87 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
File: proc_pid_status (1.30 KB, text/plain)
2019-01-04 12:42 UTC, Markus Linnala
no flags Details
valgrind output (510.96 KB, text/plain)
2019-01-09 15:10 UTC, Markus Linnala
no flags Details
valgrind output 2 (30.45 KB, text/plain)
2019-01-13 13:52 UTC, Markus Linnala
no flags Details
valgrind output 3 (30.86 KB, text/plain)
2019-01-13 13:55 UTC, Markus Linnala
no flags Details
valgrind output 4 (32.34 KB, text/plain)
2019-01-13 13:56 UTC, Markus Linnala
no flags Details

Description Markus Linnala 2019-01-04 12:42:31 UTC
Description of problem:
I guess this happened during normal operations.

Version-Release number of selected component:
systemd-239-7.git3bf819c.fc29

Additional info:
reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-resolved
crash_function: log_assert_failed_realm
executable:     /usr/lib/systemd/systemd-resolved
journald_cursor: s=544034b2a6964136b4b7a2c763d36f2e;i=40ae0a;b=c9738592323a4c0eb0d1742a988eeae8;m=19a0e4d43;t=57e75e6af485d;x=a2e2e7149684a8a4
kernel:         4.19.10-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            982

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 log_assert_failed_realm at ../src/basic/log.c:805
 #3 dns_packet_unref at ../src/resolve/resolved-dns-packet.c:194
 #4 dns_transaction_free at ../src/resolve/resolved-dns-transaction.c:87
 #5 dns_transaction_gc at ../src/resolve/resolved-dns-transaction.c:147
 #7 dns_transaction_complete at ../src/resolve/resolved-dns-transaction.c:366
 #8 on_transaction_stream_error at ../src/resolve/resolved-dns-transaction.c:473
 #9 on_stream_complete at ../src/resolve/resolved-dns-transaction.c:543
 #10 dns_stream_complete at ../src/resolve/resolved-dns-stream.c:62
 #11 source_dispatch at ../src/libsystemd/sd-event/sd-event.c:3111
 #12 sd_event_dispatch at ../src/libsystemd/sd-event/sd-event.c:3516

Comment 1 Markus Linnala 2019-01-04 12:42:36 UTC
Created attachment 1518365 [details]
File: backtrace

Comment 2 Markus Linnala 2019-01-04 12:42:39 UTC
Created attachment 1518366 [details]
File: cgroup

Comment 3 Markus Linnala 2019-01-04 12:42:41 UTC
Created attachment 1518367 [details]
File: core_backtrace

Comment 4 Markus Linnala 2019-01-04 12:42:43 UTC
Created attachment 1518368 [details]
File: cpuinfo

Comment 5 Markus Linnala 2019-01-04 12:42:44 UTC
Created attachment 1518369 [details]
File: dso_list

Comment 6 Markus Linnala 2019-01-04 12:42:45 UTC
Created attachment 1518370 [details]
File: environ

Comment 7 Markus Linnala 2019-01-04 12:42:47 UTC
Created attachment 1518371 [details]
File: limits

Comment 8 Markus Linnala 2019-01-04 12:42:48 UTC
Created attachment 1518372 [details]
File: machineid

Comment 9 Markus Linnala 2019-01-04 12:42:50 UTC
Created attachment 1518373 [details]
File: maps

Comment 10 Markus Linnala 2019-01-04 12:42:51 UTC
Created attachment 1518374 [details]
File: mountinfo

Comment 11 Markus Linnala 2019-01-04 12:42:53 UTC
Created attachment 1518375 [details]
File: open_fds

Comment 12 Markus Linnala 2019-01-04 12:42:54 UTC
Created attachment 1518376 [details]
File: proc_pid_status

Comment 13 Zbigniew Jędrzejewski-Szmek 2019-01-04 13:38:53 UTC
This is a memory corruption issue, so the backtrace is not particularly relevant, the error happens long before that.
https://github.com/systemd/systemd/pull/11055 might fix this.

Comment 14 Markus Linnala 2019-01-09 15:10:54 UTC
Created attachment 1519521 [details]
valgrind output

I ran systemd-resolved under valgrind and got another crash after some days. I've attached last part of the log as I hope it can add info about bad memory allocations.

$ rpm -qf /usr/lib/systemd/systemd-resolved
systemd-239-7.git3bf819c.fc29.x86_64

Comment 15 Markus Linnala 2019-01-13 13:52:22 UTC
Created attachment 1520272 [details]
valgrind output 2

Another valgrind output,

systemd-239-7.git3bf819c.fc29.x86_64

another Invalid read location too. I've since updated to newer 

systemd-239-8.gite339eae.fc29.x86_64

so we shall see if there is some help there.

Comment 16 Markus Linnala 2019-01-13 13:55:13 UTC
Created attachment 1520273 [details]
valgrind output 3

Another older valgrind output, invalid read on SIGHUP.

Comment 17 Markus Linnala 2019-01-13 13:56:46 UTC
Created attachment 1520274 [details]
valgrind output 4

Same as before, Invalid read on SIGHUP.

Comment 18 Zbigniew Jędrzejewski-Szmek 2019-09-12 13:18:52 UTC
Hi Markus, did you see those crashes with systedm-241 in F30 or higher?
https://github.com/systemd/systemd/pull/11055 wasn't backported to systemd 239 / Fedora 29.

Comment 19 Zbigniew Jędrzejewski-Szmek 2019-09-12 16:01:51 UTC
*** Bug 1659482 has been marked as a duplicate of this bug. ***

Comment 20 Ben Cotton 2019-10-31 18:50:46 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 21 Ben Cotton 2019-11-27 23:25:07 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.