Failed to start networking

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Failed to start networking

      I am getting a failed to start networking error while booting. I am also no able to change any networking settings in the gui or with firstaid. The weird thing is, in the gui it is showing a network interface that does not exist, or that is not in my interfaces file. Here are my errors.

      root@mymediavault:/etc/openmediavault# systemctl status networking
      networking.service - Raise network interfaces
      Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
      Active: failed (Result: exit-code) since Sat 2019-01-05 20:18:24 PST; 20h ago
      Docs: man:interfaces(5)
      Main PID: 9297 (code=exited, status=1/FAILURE)
      CPU: 67ms
      Jan 05 20:18:24 mymediavault systemd[1]: Starting Raise network interfaces...
      Jan 05 20:18:24 mymediavault ifup[9297]: RTNETLINK answers: File exists
      Jan 05 20:18:24 mymediavault ifup[9297]: ifup: failed to bring up enp3s0
      Jan 05 20:18:24 mymediavault systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      Jan 05 20:18:24 mymediavault systemd[1]: Failed to start Raise network interfaces.
      Jan 05 20:18:24 mymediavault systemd[1]: networking.service: Unit entered failed state.
      Jan 05 20:18:24 mymediavault systemd[1]: networking.service: Failed with result 'exit-code'.
      root@mymediavault:/etc/openmediavault#


      Here is my interfaces file

      # Include additional interface stanzas.
      source-directory interfaces.d
      # The loopback network interface
      auto lo
      iface lo inet loopback
      # enp3s0 network interface
      auto enp3s0
      allow-hotplug enp3s0
      iface enp3s0 inet static
      address 192.168.1.160
      gateway 192.168.1.1
      netmask 255.255.255.0
      dns-nameservers 192.168.1.1 8.8.8.8
      iface enp3s0 inet6 manual
      pre-down ip -6 addr flush dev $IFACE

      However here is what the gui shows
      Network Gui

      What is actually working is what the interface file shows. When I try to change it from within the gui , i get an error about the networking service and to see the status with systemctl status networking as shown above.

      Any idea whats going on?
    • What is the output of

      Shell-Script

      1. # ip addr show
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • I also have problem with my network after a restart. My NAS have two network card and I have tried setting both static ip and dhcp using omv-firstaid but neither work.

      When the server start up can I see this message "A start job is running for Raise network interfaces".

      I am running Docker on the server and the only IP address I see when I run ifconfig is an address for the docker interface.
    • votdev wrote:

      What is the output of

      Shell-Script

      1. # ip addr show
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
      2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether 60:e3:27:03:55:2b brd ff:ff:ff:ff:ff:ff
      inet 192.168.1.160/24 brd 192.168.1.255 scope global enp3s0
      valid_lft forever preferred_lft forever
      3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
      link/ether 02:42:2c:ce:f4:81 brd ff:ff:ff:ff:ff:ff
      inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      valid_lft forever preferred_lft forever
      5: vetha695511@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
      link/ether da:7c:86:d8:6b:b1 brd ff:ff:ff:ff:ff:ff link-netnsid 0
      root@mymediavault:~#
    • votdev wrote:

      What is the output of

      Shell-Script

      1. # ip addr show
      root@mymediavault:~# 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 Tue 2019-01-08 16:26:38 PST; 2h 30min ago
      Docs: man:interfaces(5)
      Process: 804 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
      Process: 673 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
      Main PID: 804 (code=exited, status=1/FAILURE)
      CPU: 73ms

      Jan 08 16:26:34 mymediavault systemd[1]: Starting Raise network interfaces...
      Jan 08 16:26:36 mymediavault ifup[804]: ifup: waiting for lock on /run/network/ifstate.enp3s0
      Jan 08 16:26:38 mymediavault ifup[804]: RTNETLINK answers: File exists
      Jan 08 16:26:38 mymediavault ifup[804]: ifup: failed to bring up enp3s0
      Jan 08 16:26:38 mymediavault systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      Jan 08 16:26:38 mymediavault systemd[1]: Failed to start Raise network interfaces.
      Jan 08 16:26:38 mymediavault systemd[1]: networking.service: Unit entered failed state.
      Jan 08 16:26:38 mymediavault systemd[1]: networking.service: Failed with result 'exit-code'.
      root@mymediavault:~# systemctl restart networking
      Job for networking.service failed because the control process exited with error code.
      See "systemctl status networking.service" and "journalctl -xe" for details.
      root@mymediavault:~# ip addr show
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
      2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether 60:e3:27:03:55:2b brd ff:ff:ff:ff:ff:ff
      inet 192.168.1.160/24 brd 192.168.1.255 scope global enp3s0
      valid_lft forever preferred_lft forever
      3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
      link/ether 02:42:2c:ce:f4:81 brd ff:ff:ff:ff:ff:ff
      inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      valid_lft forever preferred_lft forever
      5: vetha695511@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
      link/ether da:7c:86:d8:6b:b1 brd ff:ff:ff:ff:ff:ff link-netnsid 0


      root@mymediavault:~# ifup enp3s0
      RTNETLINK answers: File exists
      ifup: failed to bring up enp3s0
      root@mymediavault:~#

      The post was edited 1 time, last by happimeal ().

    • geaves wrote:

      happimeal wrote:

      RTNETLINK answers: File exists
      That's the problem, try this directly on OMV from the cli ip addr flush dev enp3s0 followed by /etc/init.d/networking/restart then try the GUI login, this may or may not work.
      so running the first command brought the system down, had to reset it manually, i guess I should do if from the console with a monitor? I reset the system, same problem, i ran ifup --ignore-errors and it started, and then i was able to bring up networking, not sure if it will restart after a reboot though?
    • happimeal wrote:

      That fixed the problem, thank you, I was wondering what the RTNETLINK error means and what the command you had me run does?
      Basically it removes the address assigned to the interface and therefore takes it down, the second command restarts the networking and hopefully is reassigned an ip address.
      That error has appeared a few times on the forum and I'm in the habit of keeping notes on errors and any subsequent solutions, I hadn't made a note that this needs to be done whilst directly connected to omv's console, but at least it's working :thumbsup:
      Raid is not a backup! Would you go skydiving without a parachute?
    • Users Online 1

      1 Guest