Finally we have found what cause this problem. Can anyone confirm that this bug was finally fixed?
Jeremy, thanks for instance IDs. Thanks to all who helped us to fix this issue. On Jul 15, 10:21 pm, rhythmandcode <[email protected]> wrote: > I can confirm that this is not fixed. Farm 2082. I terminated the > farm around 1 hour and 45 minutes ago. The farm list page shows the > farm as "Terminated", but the "Instances" column shows 2 instances > which are in fact running. Instance IDs i-0b3a0562 and i-0d3a0564 > both show they've been running for 1 hour 38 minutes. Please take > another look at this bug. > > Thanks, > Jeremy > > On Jul 14, 3:56 am, Nickolas Toursky <[email protected]> wrote: > > > > > Hi Kenneth, > > > Could you please provide instance ids affected? > > > Nick > > > On Jul 14, 2:35 am, kenvogt <[email protected]> wrote: > > > > I just had the same problem after terminating farm 2056. Are you sure > > > this bug is fixed? > > > > On Jul 11, 12:36 am, "Igor V. Savchenko (DicsyDel)" > > > > <[email protected]> wrote: > > > > Bug was fixed. Thaks for the report. > > > > > On Jul 11, 1:04 am, rhythmandcode <[email protected]> wrote: > > > > > > Hello, three times today I have had troubleterminatinga farm. Each > > > > > time, I choose to terminate the farm, and confirm my choice. The > > > > > Scalr panel shows the farm as 'Terminated' and the Instances panel > > > > > shows the instances as waiting to be shut down. Then the instances go > > > > > away, and within about 5 minutes Scalr launches new instances but > > > > > continues to show the farm status as 'Terminated', but does list the > > > > > instances within the farm. > > > > > > One of the farms I just deleted hoping that the instances would be > > > > > terminated, but I ended up having to go to the AWS management console > > > > > to terminate the instances. The other farm ID is 2044, and this > > > > > problem has happened twice today on this farm. > > > > > > The last time it happened I tried to launch the farm again, which > > > > > seemed to work. The Scalr panel showed the farm as 'Running'. Then I > > > > > tried to terminate the farm, and got the same problem detailed above. > > > > > So, I'm now going to go to the AWS console to terminate the > > > > > instances. The latest two "rogue instance" IDs are i-2180b148 and > > > > > i-2580b14c. > > > > > > By the way, is anyone from Scalr actually reading this forum? I sent > > > > > a few questions the a scalr.net email address before signing up and > > > > > was impressed with the speed at which I got a response. Since signing > > > > > up I've posted several questions to this group as well as sent a few > > > > > questions via email to the same scalr.net email address and have heard > > > > > nothing. > > > > > > Jeremy- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
