mjhjmtu

I can't ifdown an interface on Debian 6.0.5:

user@box:/etc/network$ sudo ifdown eth0 && sudo ifup eth0
ifdown: interface eth0 not configured
SIOCADDRT: File exists
Failed to bring up eth0.

user@box:/etc/network$ cat interfaces 
auto lo
iface lo inet loopback

allow-hotplug eth0 
allow-hotplug eth1 

auto eth0
iface eth0 inet static
address 10.0.0.1
netmask 255.255.255.0
gateway 10.0.0.254

auto eth1
iface eth1 inet manual

As requested by marco:

user@box:/etc/network/$ cat /run/network/ifstate 
lo=lo
eth1=eth1

Check the contents of the file /run/network/ifstate. ifup and ifdown use this file to note which network interfaces can be brought up and down. Thus, ifup can be easily confused when other networking tools are used to bring up an interface (e.g. ifconfig).

From man ifup

The program keeps records of whether network interfaces are up or
down. Under exceptional circumstances these records can become
inconsistent with the real states of the interfaces. For example,
an interface that was brought up using ifup and later
deconfigured using ifconfig will still be recorded as up. To fix
this you can use the --force option to force ifup or ifdown to
run configuration or deconfiguration commands despite what it
considers the current state of the interface to be.

ifdown is a high-level program which does a lot of things you might not need. Additionally, it isn't available everywhere. The more portable way might work for you:

$ sudo ifconfig eth0 down

If you then can't ifup it, you likely have some configuration problem. Manually bringing it up with ifconfig eth0 up probably isn't the right thing in that case. On Debian, ifup is a binary executable, so you'd probably have to strace it to figure out where it's getting hung up:

$ sudo strace -e open ifup eth0

That will tell you which files ifup is opening while it works, which might clue you into the problem.

On other systems (e.g. RHEL and derivatives) ifup is a shell script, so it's a lot easier to debug:

# sh -x `which ifup` eth0

Running a shell script with sh -x makes it print every line it runs, so you can trace the execution.

I've seen this before when ethX wasn't properly configured in
/etc/network/interfaces. This needs something like:-

auto eth0
 iface eth0 inet dhcp

Even with an improperly configured /etc/network/interfaces file, you can still bring down eth0 with:

$ sudo ip link set eth0 down

For anyone struggling with this problem:

I checked the file ifstate."interface-name" at /run/network.

It was empty so I included "interface-name"(eth0) into ifstate."interface-name" file at /run/network.

Add eth0=eth0 to /run/network/ifstate. This worked for me

What I found helped me is to call the rm command to remove the lock file within /run/network/

Do ls -la and you should see a hidden .ifstate file or something under that name.

Remove that and then try: ifdown && ifup

If you're worried you might break something just make a copy of that file outside the directory and remove the one inside the directory.