Don Zauker's picture

Hello,

I'm facing a strange network related issue, I have a TK LAMP installed as VM on a ESX system, sometimes when I reboot the VM the network interface goes crazy:

non-zero exitcode (1) for command: ifdown 'eth0'

/etc/network/interfaces:14: duplicated option

ifdown: couldn't read interface file

"/etc/network/interfaces"

Usually network files is:

# UNCONFIGURED INTERFACES
# remove the above line if you edit this file
 
auto lo
iface lo inet loopback
 
auto eth0
iface eth0 inet static
    address xx.xx.xx.xx
    netmask xx.xx.xx.xx
    gateway xx.xx.xx.xx
    dns-nameservers xx.xx.xx.xx.xx.
 
When it goes mad I found another line:
 
iface eth1 inet dhcp
 
but eth1 doesn't exist at all !
 
To fix I have to force dhcp on eth0 and reboot.
This Vm machine was installed rom CD and not moved from other virtual environment.
Forum: 
DjK's picture

I had the same issue, came out of nowhere on a restart of the Turnkey LAMP server on ESXi.

If you look in the file "/etc/network/interfaces" you will probably have a duplicate entry for your eth0 adapter.  I had one entry which was my static address but further down the file I also had another entry for eth0 set as dhcp.

I removed the dhcp duplicate entry against 'eth0' then issued ifup eth0 and it came up fine.

Yannatos's picture

Don Zauker    Thank you for your help. My VM had the same problem. Thanks a lot
ct2193's picture

My original server was running TurnKey LAMP 14. I had previous versions on the same hardware too. None of these ever had an issue with the networking. Today I tried to install LAMP 16 and I'm error coding on DHCP and a screen flooded with useless junk when trying to set static. After wasting most of the day fighting with this, I tried to test LXC on another server. It says it's version 15.1. Looks like it has the same networking issues. Both physical servers are the same hardware and had previously run TKL of older versions without issue. Again, version 14 and previous never had these problems for me. Not sure where the problem lies.
Jeremy Davis's picture

I'll need a bit more info than what you've provided before I'd be even make an educated guess on what might be going wrong with your setup.

Also, rather than hijacking this old thread, I suggest that you sign up (so you can start your own new support thread - requires logged in user for that link to work).

Then please provide as much info as you can about your hardware. Assuming that you're connecting via a wire plugged into a NIC, then if it's a branded PC, then the brand and model should be enough. If it's a "white box" (i.e. assembled from parts) then the motherboard manufacturer and model will help. If you're connecting via an alternate NIC (e.g. a USB or PCI/PCIe) then the brand and model of the adaptor.

Also a copy of the "useless junk" that is displayed when you try to set a static IP would also be useful (ideally copy/paste the text; but on hardware I understand that can be a pain, so even a photo is better than nothing). My guess is that the "junk" that is being displayed is a stacktrace. A stacktrace should detail the cause of the issue, or at least hints on what the issue might be.

Also the output of the following commands might give us some ideas/hints:

cat /etc/network/interfaces
ifconfig
ip addr
dmesg | grep -i "fail"

Add new comment