Good evening.
I have 2 NICs, Intel i-210 (eth0) and Intel i-219 (eth1) to which I cannot make any configuration changes either in CLI mode (omv-firstaid) or in the webUI (Network tab), as I always get this error:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1':
Job for <a href="http://networking.service">networking.service</a> failed because the control process exited with error code.
See "systemctl status <a href="http://networking.service" "="">networking.service"</a> and "journalctl -xe" for details
In details:
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl start 'networking' 2>&1' with exit code '1': Job for <a href="http://networking.service">networking.service</a> failed because the control process exited with error code.
See "systemctl status <a href="http://networking.service" "="">networking.service"</a> and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(146): OMV\System\SystemCtl->exec('start', NULL, false)
#2 /usr/share/openmediavault/engined/module/networking.inc(44): OMV\System\SystemCtl->start()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleNetworking->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
If I enter "systemctl status networking.service" I get:
● <a href="http://networking.service">networking.service</a> - Raise network interfaces
Loaded: loaded (/<a href="http://lib/systemd/system/networking.service;">lib/systemd/system/networking.service;</a> enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-12-08 14:04:10 CET; 13s ago
Docs: man:interfaces(5)
Process: 11629 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 11624 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environmen
Main PID: 11629 (code=exited, status=1/FAILURE)
CPU: 182ms
dic 08 14:04:10 olmos13nas systemd[1]: Starting Raise network interfaces...
dic 08 14:04:10 olmos13nas ifup[11629]: ifquery: recursion detected for interface eth0 in post-up phase
dic 08 14:04:10 olmos13nas ifup[11629]: run-parts: /etc/network/if-up.d/openmediavault-issue exited with return c
dic 08 14:04:10 olmos13nas ifup[11629]: ifup: failed to bring up eth0
dic 08 14:04:10 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Main process exited, code=exited, status=1/FAILURE
dic 08 14:04:10 olmos13nas systemd[1]: Failed to start Raise network interfaces.
dic 08 14:04:10 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Unit entered failed state.
dic 08 14:04:10 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Failed with result 'exit-code'.
Alles anzeigen
And if I enter "journalctl -xe" I get:
dic 08 14:06:58 olmos13nas systemd[1]: Starting Raise network interfaces...
-- Subject: Unit <a href="http://networking.service">networking.service</a> has begun start-up
-- Defined-By: systemd
-- Support: <a href="https://www.debian.org/support">https://www.debian.org/support</a>
--
-- Unit <a href="http://networking.service">networking.service</a> has begun starting up.
dic 08 14:06:58 olmos13nas ifup[13693]: ifquery: recursion detected for interface eth0 in post-up phase
dic 08 14:06:58 olmos13nas ifup[13693]: run-parts: /etc/network/if-up.d/openmediavault-issue exited with return code 1
dic 08 14:06:58 olmos13nas ifup[13693]: ifup: failed to bring up eth0
dic 08 14:06:58 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Main process exited, code=exited, status=1/FAILURE
dic 08 14:06:58 olmos13nas systemd[1]: Failed to start Raise network interfaces.
-- Subject: Unit <a href="http://networking.service">networking.service</a> has failed
-- Defined-By: systemd
-- Support: <a href="https://www.debian.org/support">https://www.debian.org/support</a>
--
-- Unit <a href="http://networking.service">networking.service</a> has failed.
--
-- The result is failed.
dic 08 14:06:58 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Unit entered failed state.
dic 08 14:06:58 olmos13nas systemd[1]: <a href="http://networking.service:">networking.service:</a> Failed with result 'exit-code'.
Alles anzeigen
The main drawbacks are:
- I cannot activate wake-on-lan so I have to go physically to power on the NAS when I need it.
- I cannot do link-aggregation (eth0+eth1) to have a backup in case one of the NICs fail.
Technically I can configure them, but at the moment of saving the changes in the webUI, it shows the errror and it does not take the changes.
It seems that there is something wrong at the moment of raising the netowrk interface (if up).
My /etc/network/interfaces looks like this:
# The loopback network interface
auto lo
iface lo inet loopback
# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet manual
pre-down ip -4 addr flush dev $IFACE
dns-search olmos13
iface eth0 inet6 manual
pre-down ip -6 addr flush dev $IFACE
Alles anzeigen
Ifconfig gives the following information (masked the MAC parts):
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet <a href="http://172.17.0.1">172.17.0.1</a> netmask <a href="http://255.255.0.0">255.255.0.0</a> broadcast <a href="http://0.0.0.0">0.0.0.0</a>
ether XX:XX:XX:XX:XX:XX txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet <a href="http://192.168.13.31">192.168.13.31</a> netmask <a href="http://255.255.255.0">255.255.255.0</a> broadcast <a href="http://192.168.13.255">192.168.13.255</a>
ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet)
RX packets 23820840 bytes 29159028858 (27.1 GiB)
RX errors 0 dropped 0 overruns 622 frame 0
TX packets 12043434 bytes 1909707069 (1.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xdfe00000-dfe7ffff
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet <a href="http://127.0.0.1">127.0.0.1</a> netmask <a href="http://255.0.0.0">255.0.0.0</a>
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 8368781 bytes 10767049842 (10.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8368781 bytes 10767049842 (10.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Alles anzeigen
I tried:
- Perform any change with the network cable attached and detached
- Enter the command "ifconfig eht0 down" and "ifconfig eth1 down" and tried to perform any change
- Enter "system restart networking" (command works)
- Flush by entering: "ip addr flush dev eth0" and "ip addr flush dev eth1" (command works)
Thanks in advance.
Regards.