Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

networking.service fails to start (times out after 5 minutes) when both IPv4 and IPv6 are enabled for an interface #116

amezin opened this Issue Jun 1, 2018 · 2 comments


None yet
3 participants
Copy link

amezin commented Jun 1, 2018

When I enable both IPv4 and IPv6 for some interface (DHCP in both cases), omv boots very slowly. The problem is networking.service. It freezes and times out after 5 minutes:

root@omv:~# systemctl status networking.service 
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2018-06-01 14:20:43 +06; 3min 41s ago
     Docs: man:interfaces(5)
  Process: 463 ExecStart=/sbin/ifup -a --read-environment (code=killed, signal=TERM)
  Process: 332 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
 Main PID: 463 (code=killed, signal=TERM)

Jun 01 14:15:42 omv systemd[1]: Starting Raise network interfaces...
Jun 01 14:15:43 omv ifup[463]: ifup: waiting for lock on /run/network/ifstate.enp0s3
Jun 01 14:20:43 omv systemd[1]: networking.service: Start operation timed out. Terminating.
Jun 01 14:20:43 omv systemd[1]: networking.service: Main process exited, code=killed, status=15/TERM
Jun 01 14:20:43 omv systemd[1]: Failed to start Raise network interfaces.
Jun 01 14:20:43 omv systemd[1]: networking.service: Unit entered failed state.
Jun 01 14:20:43 omv systemd[1]: networking.service: Failed with result 'timeout'.

But the interface gets an IPv6 address:

root@omv:~# ifconfig enp0s3
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet  netmask  broadcast
        inet6 fe80::a00:27ff:fed8:1436  prefixlen 64  scopeid 0x20<link>
        inet6 2a02:2698:5422:c615:a00:27ff:fed8:1436  prefixlen 64  scopeid 0x0<global>
        ether 08:00:27:d8:14:36  txqueuelen 1000  (Ethernet)
        RX packets 889  bytes 102471 (100.0 KiB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 733  bytes 68035 (66.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Reproducible on real hardware and in VirtualBox. Installed OMV 4 on top of a minimal installation of Debian 9 using this guide:
The same problem didn't occur on Debian prior to installation of OMV


This comment has been minimized.

Copy link

jonathanmmm commented Mar 8, 2019

I have the same issue after I changed my motherboard and had to reconfigure (enp4s0 changed to enp2s0).

But removing auto (as in refferenced) will propably dissable autostart of the network interface and make the machine after restart not available over network (if I understand correctly what auto does, it autostarts the interface on bootup?).

Before the system also needed some time to boot up but maybe I have never typed:
systemctl status networking.service.
I just looked at ifconfig or similar outputs.

If I disable ipv6 with omv-firstaid all works properly.

I chose both auto (dhcpv6 and slaac?) ways for IPv6 both didn´t work.

The system gets ipv6 (fd55..., fe80..., 2003...) and can ping6 and also an ipv6 (2003) of another device in my network.

So all seems to work. But still the networking.service failed. I don´t believe this is good.

@votdev votdev added bug 4.x labels Mar 8, 2019


This comment has been minimized.

Copy link

votdev commented Mar 8, 2019

The same problem didn't occur on Debian prior to installation of OMV

Does this apply to the same machines your using to test OMV? If yes, does the /etc/network/interfaces file looks exact the same? I'm wondering because OMV does not do any special things to the userland network stack.

The only thing that comes into mind is the systemd unit openmediavault-issue. Can you give it a try and disable this unit. Maybe this will fix the boot issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.