5 minute delay

[Airw0lf]

Team,

I'm trying to build a LXC container with a few network services like docker, pihole and chrony.
The build went as expected. However, after a reboot, there is a little over 5 minute delay when starting these services.
Using debug mode of pihole reveiled the following message:

Jun 26 15:12:32 morpheus systemd[1]: ifupdown-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 26 15:12:32 morpheus systemd[1]: ifupdown-wait-online.service: Failed with result 'exit-code'. Jun 26 15:12:32 morpheus systemd[1]: Failed to start Wait for network to be configured by ifupdown. Jun 26 15:12:32 morpheus systemd[1]: Reached target Network is Online.
Once this stage is reached all services mentioned previously are started immediately.

Anyone an idea what might be happening here?
And what service might be causing this?

The LXC container is running on the latest version of Debian 11.
Proxmox is running on the latest version 7.

Within the LXC container there is no DHCP - all interfaces have static IP adresses.

In addition IPv6 is turned off for the host as well as the LXC container.
This is done by putting the the following 3 lines in sysctl.conf:
net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1


Many thanks - Will

 

[donhwyo]

Sounds like the network is being delayed and times out after 5 min. Should be able to see it with

systemd-analyze blame

Good luck

 

[Airw0lf]

Sounds like the network is being delayed and times out after 5 min. Should be able to see it with

systemd-analyze blame

Good luck

Thank you.

When I run this on 2 different LXC containers (one with Debian en one with Ubuntu), the Ubuntu container has 13 seconds for systemd-networkd-wait-online.service. While the Debian container has 5min for ifupdown-wait-online.service.

Any idea where these differences are coming from?
Is their a way for figuring out what it is that they are waiting for?

 

[donhwyo]

Sorry I am not familiar enough with containers to help. At least you know what to look at. Maybe the network config?

 

[Dunuin]

You also set the IPv6 to static in the LXCs options and not to something like DHCP?

 

[Spoonman2002]

Team,

I'm trying to build a LXC container with a few network services like docker, pihole and chrony.
The build went as expected. However, after a reboot, there is a little over 5 minute delay when starting these services.
Using debug mode of pihole reveiled the following message:

Jun 26 15:12:32 morpheus systemd[1]: ifupdown-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 26 15:12:32 morpheus systemd[1]: ifupdown-wait-online.service: Failed with result 'exit-code'. Jun 26 15:12:32 morpheus systemd[1]: Failed to start Wait for network to be configured by ifupdown. Jun 26 15:12:32 morpheus systemd[1]: Reached target Network is Online.
Once this stage is reached all services mentioned previously are started immediately.

Anyone an idea what might be happening here?
And what service might be causing this?

The LXC container is running on the latest version of Debian 11.
Proxmox is running on the latest version 7.

Within the LXC container there is no DHCP - all interfaces have static IP adresses.

In addition IPv6 is turned off for the host as well as the LXC container.
This is done by putting the the following 3 lines in sysctl.conf:
net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1


Many thanks - Will

In the properties of the LXC, set IPv6 to static (with empty ip address) and not dhcp.

 

[Airw0lf]

Yes - the IPv6 field is set to static and all fields are left empty.

In addition - nothing on IPv6 in /etc/network/interfaces.
This applies for the host as well as the container.

 

[donhwyo]

Look at

systemd-analyze --help

or the man page. Maybe some of the options could help?

When I was having problems with this it turned out to the fault of the vm distro. Never did see what the fix was.

 

[Airw0lf]

Thank

Sorry I am not familiar enough with containers to help. At least you know what to look at. Maybe the network config?

Must be something like this - yes.

 

[Airw0lf]

I managed to solve (work-around?) this with:
(1) - disabling the ifupdown-wait-online.service
(2) - install ifupdown2 (which turned out removing the already installed ifupdown?)
Both where done within the LXC container

It now works as expected.