subject:"\[Touch\-packages\] \[Bug 1809438\] Re\: systemd\-resolved segfaults"

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2021-06-30 Thread Dan Streetman

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2021-02-19 Thread Danny Brugman

I seem to be affected by the same issue. I get regular DNS query time-
outs coinciding with a lot of the following log messages (syslog):

systemd-resolved[1119]: Server returned error NXDOMAIN, mitigating
potential DNS violation DVE-2018-0001, retrying transaction with reduced
feature level UDP.

Eventually systemd-resolved crashes. This happens more frequently (/or
only) when connected to wifi.

Trace extracted from an Apport crash report (cause was a segmentation
fault):

#0  0x7efeaa3c62ed in sd_event_source_unref (p=0x1b01030036100326) at 
../src/libsystemd/sd-event/sd-event.c:1912
__PRETTY_FUNCTION__ = "sd_event_source_unref"
#1  0x561894e7f162 in dns_query_stop (q=q@entry=0x5618967255b0) at 
../src/resolve/resolved-dns-query.c:336
c = 
__PRETTY_FUNCTION__ = "dns_query_stop"
#2  0x561894e7f1d0 in dns_query_complete (q=0x5618967255b0, 
state=) at ../src/resolve/resolved-dns-query.c:528
__PRETTY_FUNCTION__ = "dns_query_complete"
#3  0x561894e7f33f in on_query_timeout (s=, usec=, userdata=) at ../src/resolve/resolved-dns-query.c:539
q = 
__PRETTY_FUNCTION__ = "on_query_timeout"
#4  0x7efeaa3ceb76 in source_dispatch (s=s@entry=0x561896722680) at 
../src/libsystemd/sd-event/sd-event.c:3201
saved_type = SOURCE_TIME_BOOTTIME
r = 
__PRETTY_FUNCTION__ = "source_dispatch"
__func__ = "source_dispatch"
#5  0x7efeaa3ceef1 in sd_event_dispatch (e=e@entry=0x5618966cfcd0) at 
../src/libsystemd/sd-event/sd-event.c:3634
ref = 
p = 
r = 
__PRETTY_FUNCTION__ = "sd_event_dispatch"
#6  0x7efeaa3d0928 in sd_event_run (e=e@entry=0x5618966cfcd0, 
timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:3692
r = 1
__PRETTY_FUNCTION__ = "sd_event_run"
#7  0x7efeaa3d0b4f in sd_event_loop (e=0x5618966cfcd0) at 
../src/libsystemd/sd-event/sd-event.c:3714
ref = 0x5618966cfcd0
r = 
__PRETTY_FUNCTION__ = "sd_event_loop"
#8  0x561894e5a22a in run (argv=, argc=) at 
../src/resolve/resolved.c:84
notify_stop = 0x561894ea3d70 "STOPPING=1\nSTATUS=Shutting down..."

Log statement from the kernel log:

traps: systemd-resolve[1162] general protection fault ip:7efeaa3c62ed
sp:7ffef7d6f1b0 error:0 in libsystemd-shared-245.so[7efeaa39e000+174000]

(Although the trace started with a notify_stop, the system was not
shutdown at the time)

Other details:

Release: Ubuntu 20.04.01 (amd64)
Systemd package version: 245.4-4ubuntu3.4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS s

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2020-02-28 Thread Tim Riker

How should I persistently bypass systemd-resolved ? The DNS failures are
causes other applications to fail. I'd like resolv.conf to update with
dhcp returned data for DNS servers, but, for the time being, I'd like
applications to talk to the upstream DNS servers until this issue is
resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2019-03-31 Thread OlivierS

the backtrace is not always the same, here another one:

Program received signal SIGSEGV, Segmentation fault.
0x7fbc408726a6 in sd_event_source_unref () from 
target:/lib/systemd/libsystemd-shared-237.so
(gdb) bt
#0  0x7fbc408726a6 in sd_event_source_unref () from 
target:/lib/systemd/libsystemd-shared-237.so
#1  0x556a5158ea02 in ?? ()
#2  0x556a5158ea80 in ?? ()
#3  0x556a5158ec0b in ?? ()
#4  0x7fbc4079d41e in ?? () from 
target:/lib/systemd/libsystemd-shared-237.so
#5  0x7fbc4079d69a in sd_event_dispatch () from 
target:/lib/systemd/libsystemd-shared-237.so
#6  0x7fbc4079d829 in sd_event_run () from 
target:/lib/systemd/libsystemd-shared-237.so
#7  0x7fbc4079da6b in sd_event_loop () from 
target:/lib/systemd/libsystemd-shared-237.so
#8  0x556a5158972b in ?? ()
#9  0x7fbc40b99b97 in __libc_start_main (main=0x556a51588300, argc=1, 
argv=0x7ffd22f87e28, init=, fini=, 
rtld_fini=, stack_end=0x7ffd22f87e18) at 
../csu/libc-start.c:310
#10 0x556a51589dfa in ?? ()

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2019-03-31 Thread OlivierS

not sure if this gives helpful information, but here is a backtrace:

# gdb --pid=26353
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 26353
Reading symbols from target:/lib/systemd/systemd-resolved...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libc.so.6...Reading symbols 
from /usr/lib/debug/lib/x86_64-linux-gnu//libc-2.27.so...done.
done.
Reading symbols from target:/lib/systemd/libsystemd-shared-237.so...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libgpg-error.so.0...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libm.so.6...Reading symbols 
from /usr/lib/debug/lib/x86_64-linux-gnu//libm-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libgcrypt.so.20...(no 
debugging symbols found)...done.
Reading symbols from target:/lib64/ld-linux-x86-64.so.2...(no debugging symbols 
found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/librt.so.1...Reading symbols 
from /usr/lib/debug/lib/x86_64-linux-gnu//librt-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libcap.so.2...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libacl.so.1...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libcryptsetup.so.12...(no 
debugging symbols found)...done.
Reading symbols from target:/usr/lib/x86_64-linux-gnu/libip4tc.so.0...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libseccomp.so.2...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libselinux.so.1...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libidn.so.11...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/liblzma.so.5...(no debugging 
symbols found)...done.
Reading symbols from target:/usr/lib/x86_64-linux-gnu/liblz4.so.1...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libblkid.so.1...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libpthread.so.0...Reading 
symbols from 
/usr/lib/debug/.build-id/28/c6aade70b2d40d1f0f3d0a1a0cad1ab816448f.debug...done.
done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from target:/lib/x86_64-linux-gnu/libattr.so.1...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libuuid.so.1...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libdevmapper.so.1.02.1...(no 
debugging symbols found)...done.
Reading symbols from target:/usr/lib/x86_64-linux-gnu/libargon2.so.0...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libjson-c.so.3...(no 
debugging symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libpcre.so.3...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libdl.so.2...Reading symbols 
from /usr/lib/debug/lib/x86_64-linux-gnu//libdl-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libudev.so.1...(no debugging 
symbols found)...done.
Reading symbols from target:/lib/x86_64-linux-gnu/libnss_compat.so.2...Reading 
symbols from /usr/lib/debug/lib/x86_64-linux-gnu//libnss_compat-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libnss_nis.so.2...Reading 
symbols from /usr/lib/debug/lib/x86_64-linux-gnu//libnss_nis-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libnsl.so.1...Reading symbols 
from /usr/lib/debug/lib/x86_64-linux-gnu//libnsl-2.27.so...done.
done.
Reading symbols from target:/lib/x86_64-linux-gnu/libnss_files.so.2...Reading 
symbols from /usr/lib/debug/lib/x86_64-linux-gnu//libnss_files-2.27.so...done.
done.
0x7f7016940b77 in epoll_wait (epfd=4, events=0x7fffaadc3100, maxevents=14, 
timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
30  ../sysdeps/unix/sysv/linux/epoll_wait.c: No such file or directory.
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2019-01-09 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2019-01-08 Thread Brian Murray

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2019-01-01 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

8 matches

Site Navigation

Mail list logo

Footer information