[Bug 2081645] Re: (during boot) failed: Cannot assign requested address
Dominic
2081645 at bugs.launchpad.net
Thu Oct 10 22:49:27 UTC 2024
I've added my script back in to the wait-online override, which looks
like this. After a few reboots, nginx once again failed to bind to this
address.
My hacky solution is to add a 5 second sleep to the end of this script.
#!/bin/bash
ip=$(ip -6 address)
until [[ $ip == *"2603:af50:1630:aec9:f19a:227e:2f54:5c73"* ]]
do
ip=$(ip -6 address)
sleep 1
done
--
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
More information about the foundations-bugs
mailing list