[Bug 2081645] Re: (during boot) failed: Cannot assign requested address

[Nick Rosbrook]

It looks like bind9 (named.service) is able to bind to the address just
fine after systemd-networkd reports the address is configured. Is named
maybe not setting SO_REUSEADDR/SO_REUSEPORT or something? Or (as an
experiment) does disabling named.service allow the others to start?

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

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

Title:
  (during boot) failed: Cannot assign requested address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Not sure where to post this, but since systemd controls boot
  precedence this section seems appropriate.

  I am testing oracular / 24.10 , and I bind some services to specific
  IPv6 addresses. In order to wait until the IP addresses are up before
  binding to them during boot, I use systemd-networkd-wait-online,
  modified to wait for IPv6.

  The problem is, despite systemd-networkd reporting the IPv6 addresses
  are up, binding to them still fails when the daemons attempt to
  launch. If I manually start the daemons after boot, they launch fine.

  It would appear the system is reporting IPv6 addresses as available
  before they are ready to be bound to by applications, therefore
  causing those application to fail during boot.

  Log attached.

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