Viewed 2k times
I’m kind of new to Ubuntu but I’ve played around with older versions (13.04, 14.04, & 15.04) and now 16.04 on a spare laptop. However, I’ve never tried to map network shares on my Win 10 Pro 64-bit that is setup as my Home Media & Backup Server.
I bought a new ip address for my dedicated server on Ubuntu 16.04, and I've been trying to set it up, but I just consistently run into one issue; I'm unable to restart the networking service proper, even with the original config. This is what I get through systemctl status networking.service;
Here are the contents of the interfaces file (I've censored the addresses of course);
I get this error with both the original file (copied over from the .bak file) and the edited file with the new IP. The networking service simply fails to run for an unspecified reason. If I try to ifup eth0 directly, I get the 'File exists' and 'Failed to bring up eth0' lines. Yet, despite shutting down, the IPs seem to get set properly in the interface configuration; they are properly mapped to the corresponding interfaces (eth0, eth0:0) and the corresponding Apache/Postfix/Dovecot installations also seem to be functional.
Yet when looking through networkctl, this is the result I get;
The interface name is clearly eth0 and not something else. I'm wondering if some kind of dhcp service is interfering or if another service actually manages the interfaces. I don't think that NetworkManager is installed as the only way to get the server to be pingable again after flushing eth0 is to attempt to start networking, but networking still crashes on the same error. What I'm afraid of is that this will cause the server to be unpingable on a hard restart.
![Ubuntu 16.04 Restart Network Ubuntu 16.04 Restart Network](/uploads/1/2/5/6/125627869/281314987.png)
Does anyone have advice concerning the issue?
EDIT1: Here's ifconfig -a, here it is for eth0 and eth0:0
Here's what happens in var/log/syslog, could it be an issue with postfix?
Sefam
SefamSefam