By kaneclover
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 http://www.google.com/ 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
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!
I’m seeing similar behavior on a similar system; want a support ticket from me too?
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!
Weird. Can you please open up a support ticket if this ever happens again? Thanks!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.