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

Hi all,

I'd trouble to re-configure my static ip after reebooting my host.

Please see below error

non-zero exitcode (1) for command : ifdown 'etho' ifdown: failed to open statefile /run/network/ifstate: no such file or directory

Please help since this instance is my corporate website, my backup instance also showing same problem.

Jeremy Davis's picture

Just to be clear what exactly were you doing/trying to do. You said you rebooted your server; then you tried to adjust your static IP.

Did you have it set with a static IP before and were changing it? Or is this the first time you have set a static IP (used a dynamic IP previously)? Where is this server running? Is it a VM? A container? A VPS?

Zasilacz's picture

I have the same poblem, after the first run. I am trying to set static ip for the host-only connection in virtualbox.

Jeremy Davis's picture

You should not get this issue if you use bridged networking; but you should be able to use other types of networking too!

Perhaps you could try exiting to the console and run this:

/etc/init.d/network restart

If that seems to do something contructive then see if you have an eth0 by running this:

ifconfig eth0

If that all works then you should be able to go back to the confconsole (the screen in the screenshot above) with the command:


Let me know how you go and I'll try to help you out...

Mike's picture

In my case, it seems taht /etc/init.d/network script isn't there.. also the /etc/network/run directory points to /run/network - which also doesn't exist.  Is there a sort of "reset all settings command" ?

Jeremy Davis's picture

TBH unless you have a good reason for that sort of thing to have happened (e.g. you accidentally deleted it) I would be very concerned why that stuff is missing! (Data corruption? Hardware dying? Someone hacked you? Someone who doesn't know what they are doing mucking around inside? ...)

Personally my first course of action would be to do some hardware scans and regardless replace the server (assuming a VM or just reinstall if on bare metal) and migrate data across.

Mike's picture

It was a n00b person trying to manually fix things, as root ... so you do the math. Reinstalling the system again and then migrating. Thank you!

Salmonstix's picture

Hi all, Im sorry to bring up an old thread but im in desperate need of help. My linux box running a mineos server has recently spat this exact error code out and i cant afford to format and start fresh :(


can anyone please help. I tried 

/etc/init.d/network restart

But with no luck.


any help would be greatly appreciated!

Jeremy Davis's picture

So my guess is that someone has broken something somewhere along the line. Last I checked, MineOS was built on/from TurnKey but I have no idea what version you are running and I suspect it's an older one.

TurnKey is based on Debian though so perhaps google might lead you to some more info? If you do manage to find something please post back.

Also FWIW, considering how volatile and unreliable harddrives are (and SSDs aren't much better) if you don't have backups, then it's only a matter of time before you experience data loss. And every day that everything runs smoothly increases the odds that you will experience data loss tomorrow.

I don't mean to be preachy, but that's the reality! Daily backups stored on Amazon S3 (with 99.99999999999% fault tolerance - far better than any consumer grade storage) FTW!

Post new comment