I had this issue trying to run an Ubuntu 24.04 LXC container on a CentOS
7 host. But enabling debug logging did work for me, and revealed this:

Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Received dns UDP packet of 
size 57, ifindex=0, ttl=64, fragsize=0, sender=127.0.0.1, destination=127.0.0.53
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Got DNS stub UDP query 
packet for id 60636
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Looking up RR for 
esm.ubuntu.com.lxc.qwarx.com IN AAAA.
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: sd-event: Failed to create 
timer event "query-timeout": Invalid argument
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Freeing transaction 20144.
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Failed to start query: 
Invalid argument
Mar 19 23:34:05 openwisp-2404 systemd-resolved[951]: Sending response packet 
with id 60636 on interface 1/AF_INET of size 57.

Which led me to this bug report:

https://github.com/systemd/systemd/issues/34580

Basically saying that systemd 250 (in Ubuntu 2404) is incompatible with
older kernels, such as 3.10.0 on CentOS 7, and won't be fixed :( Looks
like I'll have to disable systemd-resolved instead.

** Bug watch added: github.com/systemd/systemd/issues #34580
   https://github.com/systemd/systemd/issues/34580

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040055

Title:
  systemd-resolved fails: Failed to start query: Invalid argument

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to