Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-05-26 Thread Luca Boccassi 
Control: close -1

On Sat, 20 Jan 2024 20:52:20 +0100 Michael Biebl 
wrote:
> Hi Corin
> 
> 
> On Wed, 03 Jan 2024 12:50:13 +0100 Luca Boccassi 
wrote:
> > Control: severity -1 normal
> > Control: tags -1 moreinfo
> > 
> > On Wed, 03 Jan 2024 12:02:40 +0100 Corin Langosch 
> > wrote:
> > > Package: systemd
> > > Version: 247.3-7+deb11u4
> > > Severity: critical
> > > File: systemd-resolved
> > > Justification: breaks the whole system
> > 
> > Your logs show that it restarts just fine after the oom kill, so it
is
> > most definitely not "grave". Also, you did not attach your local
> > resolved.conf.
> > 
> > Also, oldstable is old. Try with backports or with upgrading to
stable.
> 
> Any updates here? Did you have the chance to reproduce this with at 
> least stable, i.e. v252. Even better would be, if you can try with
v254 
> from bookworm-backports.
> 
> So far I failed to reproduce the issue with the given information.
> 
> $ host 54.49.125.74.in-addr.arpa
> Host 54.49.125.74.in-addr.arpa not found: 3(NXDOMAIN)
> 
> That is all I get.

No follow-up in half a year, closing.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-20 Thread Michael Biebl 

Hi Corin


On Wed, 03 Jan 2024 12:50:13 +0100 Luca Boccassi  wrote:

Control: severity -1 normal
Control: tags -1 moreinfo

On Wed, 03 Jan 2024 12:02:40 +0100 Corin Langosch 
wrote:
> Package: systemd
> Version: 247.3-7+deb11u4
> Severity: critical
> File: systemd-resolved
> Justification: breaks the whole system

Your logs show that it restarts just fine after the oom kill, so it is
most definitely not "grave". Also, you did not attach your local
resolved.conf.

Also, oldstable is old. Try with backports or with upgrading to stable.


Any updates here? Did you have the chance to reproduce this with at 
least stable, i.e. v252. Even better would be, if you can try with v254 
from bookworm-backports.


So far I failed to reproduce the issue with the given information.

$ host 54.49.125.74.in-addr.arpa
Host 54.49.125.74.in-addr.arpa not found: 3(NXDOMAIN)

That is all I get.


Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-03 Thread Luca Boccassi 
Control: severity -1 normal
Control: tags -1 moreinfo

On Wed, 03 Jan 2024 12:02:40 +0100 Corin Langosch 
wrote:
> Package: systemd
> Version: 247.3-7+deb11u4
> Severity: critical
> File: systemd-resolved
> Justification: breaks the whole system

Your logs show that it restarts just fine after the oom kill, so it is
most definitely not "grave". Also, you did not attach your local
resolved.conf.

Also, oldstable is old. Try with backports or with upgrading to stable.

-- 
Kind regards,
Luca Boccassi

Bug#1059899: systemd-resolved: systemd-resolved takes up all memory on certain PTR queries and is then oom-killed

2024-01-03 Thread Corin Langosch 
Package: systemd
Version: 247.3-7+deb11u4
Severity: critical
File: systemd-resolved
Justification: breaks the whole system
X-Debbugs-Cc: cor...@gmx.de

Dear Maintainer,

systemd-resolved takes up all memory on certain PTR queries within only a few 
milliseconds and is then oom-killed. This sometimes renders the whole system 
unusable.

I can reliably reproduce the issue using this simple command:

~# host 54.49.125.74.in-addr.arpa
;; connection timed out; no servers could be reached

I already tried to debug the issue a little, please find the details below. If 
you need more information please let me know.

~# systemd-resolve --version
systemd 247 (247.3-7+deb11u4)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN 
+PCRE2 default-hierarchy=unified

~# cat /etc/systemd/resolved.conf 
[Resolve]
DNS=192.168.0.1
Domains=intern.xxx xxx.com

~# tcpdump -i any -n port 53
11:35:31.012308 loIn  IP 127.0.0.1.58906 > 127.0.0.53.53: 28856+ A? 
54.49.125.74.in-addr.arpa. (43)
11:35:31.014406 vlan4 Out IP x.x.x.x.50491 > 192.168.0.1.53: 29042+ [1au] A? 
54.49.125.74.in-addr.arpa. (54)
11:35:31.033018 vlan4 In  IP 192.168.0.1.53 > x.x.x.x.50491: 29042 NXDomain 
0/1/1 (114)

Jan 03 11:35:31 system1 systemd-resolved[40859]: SELinux enabled state cached 
to: disabled
Jan 03 11:35:31 system1 systemd-resolved[40859]: Positive Trust Anchors:
Jan 03 11:35:31 system1 systemd-resolved[40859]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jan 03 11:35:31 system1 systemd-resolved[40859]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 
31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal 
intranet lan local private test
Jan 03 11:35:31 system1 systemd-resolved[40859]: Using system hostname 
'system1'.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link *, protocol 
dns, family *
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 9/vlan1000
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 8/vlan102
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 7/vlan101
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 6/vlan100
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 5/vlan98
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 4/vlan4
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 3/vlan3
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 2/vlan2
Jan 03 11:35:31 system1 systemd-resolved[40859]: Found new link 1/lo
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan1000, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 3857 for  scope llmnr on vlan1000/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
51270us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan102, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 15599 for  scope llmnr on vlan102/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
51008us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan101, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 61000 for  scope llmnr on vlan101/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
81403us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan100, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 62244 for  scope llmnr on vlan100/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
72225us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan98, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 43244 for  scope llmnr on vlan98/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
68513us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan4, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 65377 for  scope llmnr on vlan4/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr transaction for 
79327us.
Jan 03 11:35:31 system1 systemd-resolved[40859]: New scope on link vlan3, 
protocol llmnr, family AF_INET6
Jan 03 11:35:31 system1 systemd-resolved[40859]: Transaction 41217 for  scope llmnr on vlan3/INET6.
Jan 03 11:35:31 system1 systemd-resolved[40859]: Delaying llmnr