Systemctl restart networking fails after enabling ipv6

November 12, 2018 3.3k views
Ubuntu 16.04 Networking IPv6

I was following this guide to fully setup ipv6 for my droplet: https://www.digitalocean.com/docs/networking/ipv6/how-to/enable/

Unfortunately when I get to the steps for restarting networking “sudo systemctl restart networking” I receive the following error:

“Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service” and “journalctl -xe” for details.“

Looking at the "systemctl status networking.service” shows the following log…


networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Mon 2018-11-12 01:18:50 UTC; 2min 10
Docs: man:interfaces(5)
Process: 2424 ExecStart=/sbin/ifup -a –read-environment (code=exited, status=
Process: 2419 ExecStartPre=/bin/sh -c [ “$CONFIGURE_INTERFACES” != “no” ] && [
Main PID: 2424 (code=exited, status=1/FAILURE)

Nov 12 01:18:50 Linux-Main systemd[1]: Stopped Raise network interfaces.
Nov 12 01:18:50 Linux-Main systemd[1]: Starting Raise network interfaces…
Nov 12 01:18:50 Linux-Main ifup[2424]: RTNETLINK answers: File exists
Nov 12 01:18:50 Linux-Main ifup[2424]: Failed to bring up eth0.
Nov 12 01:18:50 Linux-Main systemd[1]: networking.service: Main process exited,
Nov 12 01:18:50 Linux-Main systemd[1]: Failed to start Raise network interfaces.
Nov 12 01:18:50 Linux-Main systemd[1]: networking.service: Unit entered failed s
Nov 12 01:18:50 Linux-Main systemd[1]: networking.service: Failed with result ‘e

lines 1-18/18 (END)

Failed to bring up eth0? Bad news right? Any ideas how to resolve this? Google hasn’t seemed to give me any results that solve this issue.

Thanks in advance.

1 Answer

Hey friend!

I have a few questions that might help me to understand why this is happening:

  1. What is your distro/version?
  2. If you upgraded to that version, what distro/version was the droplet created with?
  3. What is your interface named if you run “ifconfig” in the console? Is it eth0 or something like ens#?

Jarland

  • 1.) What is your distro/version?

    • Ubuntu 16.04.4 x64

    2.) If you upgraded to that version, what distro/version was the droplet created with?

    • No manual upgrades have been done. Droplet was created as Ubuntu 16.04.4 x64 as of 8 months ago as far as I’m aware.

    3.) What is your interface named if you run “ifconfig” in the console? Is it eth0 or something like ens#?

    • eth0
    • Thanks! Hmm. Any chance the files were edited with an editor that uses tabs instead of spaces? It should be yaml which means one spacing issue and all is lost. Try removing the IPv6 lines and then pasting them in with an editor like nano over SSH (if you haven’t already).

      • Oooo… This is possibility. I just edited the file directly through WinSCP which opened it with notepad I believe.

        I’ll check this and get back to you.

      • Are you sure that file is suppose to be yaml? Having trouble with various editors (I haven’t tried nano yet) and can’t seem to get anything to successfully report it as valid yaml.

        I’ll keep investigating but just wanted to double check that it should actually be yaml.

Have another answer? Share your knowledge.