Failed to start raise network interface on Ubuntu 16.04

17,197

Maybe a bit late, but I had the same issue, but then with ip6tables that gave an error :

$ sudo ifup ens160
run-parts: failed to exec /etc/network/if-pre-up.d/ip6tables: Exec format error
run-parts: /etc/network/if-pre-up.d/ip6tables exited with return code 1
Failed to bring up ens160.

My /etc/network/if-pre-up.d/ip6tables looked like this:

ip6tables-restore < /etc/ip6tables.conf

I solved the issue by adding a shebang on top of the script to make it look like this:

#!/bin/sh
ip6tables-restore < /etc/ip6tables.conf

Now my interface is willing to come up. I hope this solution might help you (and others that stumble across this post).

Share:
17,197

Related videos on Youtube

BSAI Techno Sales
Author by

BSAI Techno Sales

Updated on September 18, 2022

Comments

  • BSAI Techno Sales
    BSAI Techno Sales over 1 year

    All of sudden I am getting failed to start raise network interface error messages in Ubuntu. Any feedback will be great help.

    I tried the following steps but still the problem exists:

    root@storage:~# systemctl stop network
    Failed to stop network.service: Unit network.service not loaded.
    
    root@storage:~# systemctl disable network
    Failed to execute operation: No such file or directory
    
    root@storage:~# /etc/init.d/networking restart
    [....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
     failed!
    
    root@storage:~# ping 192.168.0.227
    PING 192.168.0.227 (192.168.0.227) 56(84) bytes of data.
    64 bytes from 192.168.0.227: icmp_seq=1 ttl=64 time=0.022 ms
    64 bytes from 192.168.0.227: icmp_seq=2 ttl=64 time=0.059 ms
    64 bytes from 192.168.0.227: icmp_seq=3 ttl=64 time=0.054 ms
    ^C
    --- 192.168.0.227 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 1998ms
    rtt min/avg/max/mdev = 0.022/0.045/0.059/0.016 ms
    root@storage:~# 
    

    root@storage:/home/bsaitechnosales# systemctl status networking.service
    ● networking.service - Raise network interfaces
    Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
    Drop-In: /run/systemd/generator/networking.service.d
    └─50-insserv.conf-$network.conf
    Active: failed (Result: exit-code) since Thu 2018-01-11 12:50:20 +0545; 10min ago
    Docs: man:interfaces(5)
    Process: 15534 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
    Process: 15529 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm
    Main PID: 15534 (code=exited, status=1/FAILURE)

    Jan 11 12:50:20 storage ifup[15534]: Failed to bring up lo.
    Jan 11 12:50:20 storage ifup[15534]: RTNETLINK answers: File exists
    **Jan 11 12:50:20 storage ifup[15534]: Failed to bring up enp1s0.**
    Jan 11 12:50:20 storage ifup[15534]: run-parts: failed to exec /etc/network/if-up.d/iptables: Exec format error
    Jan 11 12:50:20 storage ifup[15534]: run-parts: /etc/network/if-up.d/iptables exited with return code 1
    Jan 11 12:50:20 storage systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
    Jan 11 12:50:20 storage ifup[15534]: /sbin/ifup: post-up script failed.
    Jan 11 12:50:20 storage systemd[1]: Failed to start Raise network interfaces.
    Jan 11 12:50:20 storage systemd[1]: networking.service: Unit entered failed state.
    Jan 11 12:50:20 storage systemd[1]: networking.service: Failed with result 'exit-code'.

    • hatterman
      hatterman over 6 years
      Can you check the service "networking" not "network", I think thats the correct name. Also, is this a server or a desktop ?
    • jeroen
      jeroen over 6 years
      If you are using network-manager, then the correct syntax would be: (sudo) systemctl stop NetworkManager.service you can also replace stop with restart. The capitol N and M inthe command are mandatory
    • jeroen
      jeroen over 6 years
      Furthermore you are able to check the status of your network interface with (sudo) ip link somtimes it helps to bring the interface down and up manually: (sudo) set ip link eth0 down and afterwards (sudo) set ip link eth0 up eth0 is an example use the interfacename you got with (sudo) ip link.
    • BSAI Techno Sales
      BSAI Techno Sales over 6 years
      root@storage:/home/bsaitechnosales# systemctl stop NetworkManager.service root@storage:/home/bsaitechnosales# systemctl start NetworkManager.service root@storage:/home/bsaitechnosales# systemctl restart NetworkManager.service root@storage:/home/bsaitechnosales# root@storage:/home/bsaitechnosales# set ip link enp1s0 up root@storage:/home/bsaitechnosales# sudo ip link 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 30:9c:23:5e:04:ad brd ff:ff:ff:ff:ff:ff
    • BSAI Techno Sales
      BSAI Techno Sales over 6 years
      @hatterman root@storage:/home/bsaitechnosales# service restart networking restart: unrecognized service root@storage:/home/bsaitechnosales# 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@storage:/home/bsaitechnosales# sudo systemctl restart networking.service Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
    • Chai T. Rex
      Chai T. Rex over 6 years
      If you want to use HTML to mark up terminal output, you can surround it with <pre> and </pre> to make it look good.
    • José
      José about 6 years
      cat /etc/network/interfaces please