Hi Jay, What is you Scalr version and what version of agent is running on these failed servers?
Regards, Igor On 25 July 2016 at 14:52, Jay Farschman <[email protected]> wrote: > Hello, > > PROBLEM > User's suspend VM/Instances in AWS at night and then resume them later. > Mostly this works great, but sometimes it fails. When it fails I will take > remedial actions and this fixes many things. I'll walk through the ACTIONS > below and ask for any feedback on what I could do differently or perhaps a > different order: > > > ACTIONS > To correct for instances stuck Resuming, or Rebooting: > > Firewall on Instance - I'll check the firewall on the instance to make sure > I have open port 8008-8013 TCP as well as UDP. > Soft Reboot Instance - From the Scalr Interface I'll issue a hard reboot. > The results fall into three buckets > > Reboot Successful (Normal) - The instance works now. > Reboot (Resuming) - The never seems to get out of the "Resuming" state, but > the AWS Console shows the instance running. Users are learning that they > can just log in even when it says resuming. This is annoying. > Reboot (NO Love) - This system is not rebooting. I can go into the AWS > Console and start it up from there, but I have no method of getting things > back in sync. > > ????? > > > One other thing... mostly it's Windows system, but not all of them, not even > the majority of them. Maybe 1 in 10. > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
