Why is networking dead after a soft reboot?

So I just ran “reboot now” as root on an Ubuntu 12 VM (I’d installed/updated some packages and it said reboot required). I waited a while but the machine was dead to the outside world. Not contactable via SSH or HTTP (80). I logged in via the console and:

ps aux | grep nginx Yep. It’s running

ps aux | ssh Yep. All ok.

curl -i Nothing! Hmmm…

ifconfig The interface appears to be up.

/etc/init.d/networking restart Ok, but still no connectivity.

Power cycled via the Droplet admin thing and everything’s back to normal. Any idea what’s going on there? This is a new VM with only a handful of packages installed - nothing outlandish and no config changes to do with networking at all. Any idea what’s going on?

Cheers, Kane

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Oops, never mind, found another hint about a bug in “reboot now” vs. just “reboot” on the command line. <br> <br>Also didn’t realize my username was going to be derived from my email address like that. I’m in no way officially representing digitalocean. <br> <br>Delete this at will!

I’m seeing similar behavior on a similar system; want a support ticket from me too?

Weird. Can you please open up a support ticket if this ever happens again? Thanks!