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
Active: failed (Result: exit-code) since Mon 2018-11-12 01:18:50 UTC; 2min 10
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: Stopped Raise network interfaces.
Nov 12 01:18:50 Linux-Main systemd: Starting Raise network interfaces…
Nov 12 01:18:50 Linux-Main ifup: RTNETLINK answers: File exists
Nov 12 01:18:50 Linux-Main ifup: Failed to bring up eth0.
Nov 12 01:18:50 Linux-Main systemd: networking.service: Main process exited,
Nov 12 01:18:50 Linux-Main systemd: Failed to start Raise network interfaces.
Nov 12 01:18:50 Linux-Main systemd: networking.service: Unit entered failed s
Nov 12 01:18:50 Linux-Main systemd: 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.
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.×