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
Created attachment 1518365 [details] File: backtrace
Created attachment 1518366 [details] File: cgroup
Created attachment 1518367 [details] File: core_backtrace
Created attachment 1518368 [details] File: cpuinfo
Created attachment 1518369 [details] File: dso_list
Created attachment 1518370 [details] File: environ
Created attachment 1518371 [details] File: limits
Created attachment 1518372 [details] File: machineid
Created attachment 1518373 [details] File: maps
Created attachment 1518374 [details] File: mountinfo
Created attachment 1518375 [details] File: open_fds
Created attachment 1518376 [details] File: proc_pid_status
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.
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
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.
Created attachment 1520273 [details] valgrind output 3 Another older valgrind output, invalid read on SIGHUP.
Created attachment 1520274 [details] valgrind output 4 Same as before, Invalid read on SIGHUP.
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.
*** Bug 1659482 has been marked as a duplicate of this bug. ***
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.
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.