Hi All,
Hoping someone can spot the problem here, I've run out of ideas!
Since updating to OMV4, I've had persistent problems with my bonded network interface. I thought I'd fixed them, but noticed again today that I'm stuck in a "apply config" loop. With OMV3, it was working fine for aeons (the OMV3 build was done with the bonded interfaces from the start).
There are three interfaces on the machine: eth0 is alone on one subnet, eth1 & eth2 are intended to be a 802.3ad bonded pair on another subnet. My switch (Zyxel GS1910) has 802.3ad LACP support enabled for the relevant two ports. I've also tried a fixed bond on the switch with balance-alb on the machine and that doesn't fix the problem, so it's not looking like a LACP issue.
Every time I tell OMV to apply the config, it fails - see error text below - and the interface is not working: even if ifconfig shows it as UP, it doesn't respond to ping and local services like nut & smbd/nmbd that are bonded to that interface report that it's not accessible. /etc/network/interfaces looks ok to me. If I then reboot the machine, the interface comes up but OMV still shows the config needing to be applied. Enter the "apply config" loop...
Does anyone have any ideas?
Screenshots attached show the OMV interface settings.
Here's the config:
root@dougal:/etc/network# more /etc/network/interfaces
# Include additional interface stanzas.
source-directory interfaces.d
# The loopback network interface
auto lo
iface lo inet loopback
# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.8.254
gateway 192.168.8.1
netmask 255.255.255.0
dns-nameservers 192.168.8.1
dns-search mydomain.net
iface eth0 inet6 manual
pre-down ip -6 addr flush dev $IFACE
# bond0 network interface
auto bond0
iface bond0 inet static
address 192.168.11.22
gateway 192.168.11.1
netmask 255.255.254.0
dns-nameservers 192.168.11.1
dns-search mydomain.net
bond-slaves eth1 eth2
bond-mode 4
bond-miimon 100
bond-downdelay 200
bond-updelay 200
iface bond0 inet6 manual
pre-down ip -6 addr flush dev $IFACE
journalctl -xe shows nothing of interest, just services whingeing that they can't find a network interface.
root@dougal:/etc/network# systemctl status networking.service
â— networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2018-06-03 17:40:20 BST; 2min 16s ago
Docs: man:interfaces(5)
Process: 2245 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 2241 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exi
Main PID: 2245 (code=exited, status=1/FAILURE)
Jun 03 17:40:19 dougal systemd[1]: Starting Raise network interfaces...
Jun 03 17:40:19 dougal ifup[2245]: sh: echo: I/O error
Jun 03 17:40:20 dougal ifup[2245]: RTNETLINK answers: File exists
Jun 03 17:40:20 dougal ifup[2245]: ifup: failed to bring up bond0
Jun 03 17:40:20 dougal systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 03 17:40:20 dougal systemd[1]: Failed to start Raise network interfaces.
Jun 03 17:40:20 dougal systemd[1]: networking.service: Unit entered failed state.
Jun 03 17:40:20 dougal systemd[1]: networking.service: Failed with result 'exit-code'.
IFCONFIG BEFORE REBOOT:
root@dougal:/etc/network# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.254 netmask 255.255.255.0 broadcast 192.168.8.255
ether d4:3d:7e:34:a7:16 txqueuelen 1000 (Ethernet)
RX packets 4617 bytes 1096970 (1.0 MiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 6357 bytes 7367515 (7.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 762 bytes 97399 (95.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 762 bytes 97399 (95.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
IFCONFIG AFTER REBOOT:
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.11.22 netmask 255.255.254.0 broadcast 192.168.11.255
ether 00:15:17:d3:5f:14 txqueuelen 1000 (Ethernet)
RX packets 69553 bytes 14195346 (13.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65806 bytes 18205876 (17.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.254 netmask 255.255.255.0 broadcast 192.168.8.255
ether d4:3d:7e:34:a7:16 txqueuelen 1000 (Ethernet)
RX packets 2250 bytes 174222 (170.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1339 bytes 114101 (111.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 00:15:17:d3:5f:14 txqueuelen 1000 (Ethernet)
RX packets 3308 bytes 309103 (301.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 61361 bytes 17797720 (16.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xf7ca0000-f7cc0000
eth2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 00:15:17:d3:5f:14 txqueuelen 1000 (Ethernet)
RX packets 66245 bytes 13886243 (13.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4445 bytes 408156 (398.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xf7c40000-f7c60000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2890 bytes 306387 (299.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2890 bytes 306387 (299.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
... interesting to note that eth1 & eth2 have their own entries now, not present before reboot.
/etc/network/interfaces is unchanged after reboot.
Any help greatly appreciated!
Thanks,
Jeff