Ramael, I don't think you want to remove them from the database, but instead find out why they do not complete the termination command. I would check all your routing and firewall information. See if yo can find out what address the VMs are using to connect back to the Scalr Admin. Maybe you have private IPs trying to connect to the external IP address and just need to set app[:instances_connection_policy] = 'local'
On Thursday, December 10, 2015 at 7:14:41 PM UTC-7, Ramael Metatron wrote: > > I do not understand why Scalr fails to complete the pending terminate > status on servers that have already been terminated from AWS. > These are on servers that initially failed in their status due to error > with automation software. however the terminate behavior does complete in > AWS, yet the server's stay in the server list. > > 1. is there a safe way to remove these from the db? > 2. what are some advice on dealing with this if anyone has experienced it. > > Best Regards. > -- 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.
