Question

Systemctl restart networking fails after enabling 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)

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.

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

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