Delay in control panel displaying server status

April 12, 2013 2.9k views
Hello all, I'm wondering if anyone else has noticed this. I shut down my server from ssh (sudo halt -p) to create a snapshot. The system goes down properly. I go into control panel to create a snapshot - kaboom! The server appears active. So I wait and wait, and after anything between 15 min. and a few hours! the server appears to be "Off" and I can create a snapshot. If I shut it down from the control panel it appears Off immediately, but that's not the proper way to do it. Currently I'm waiting already for more than 45 min. and the server is still "Active" in control panel. This really bugs my as I went live with my website this morning and I wanted to create a snapshot of the first live version, but instead of 2 min. downtime, I'm experiencing a long downtime. Much longer than acceptable. I understood that a few hours ago there may have been some server backlog that caused the delay, but it's been almost half day since, and the things haven't improved. Anyone? Thank you, Goran
1 comment
  • Same problem here. Been three shutting down dropl;et. but it is still active .

    Even after two hours of creating support ticket for the same, it is not resolved.
    DigitalOcean support is usually good, but i dont know what happened today.

    My Site is down , and waiting for support to respond since last few hours.


6 Answers
The backend will automatically check the state of the virtual servers and update them as necessary, whether you do a halt or a shutdown it will still be checked the same why by the hypervisor and should make no difference.

Occasionally we've seen some backlogs on the scheduler which delays this processing so the state of the server in the Cloud may not be accurately reflecting the live state of the server and we're working on improving the time it takes for the Cloud to register a change in state.

If it happens frequently please open a ticket.
its probably a bug but maybe not when i poweroff my droplet after logout and relogin my droplet status turn to inactive a few minute later.
I have the same behavior here ...

made :
sudo service apache2 stop
sudo service mysql stop

and after some minutes still active ... only resolved after : shutdown + power off.
is this the right way to do it ?
I am experiencing this issue as well, and hope that you are working on it as it is a major factor in deciding whether or not to move my production sites onto DO. Thanks for the wonderful service otherwise, and please keep us updated!
@admin please open up a ticket if you still experience this. Thanks.

I have had the same problem. I have dealt with it clicking "Power Off" once I know it is already turned off and the status is updated almost immediately. Once you have done that, you can boot it again.

Have another answer? Share your knowledge.