Hi Amit, Are you able to SSH in to these machines and gather any logs while they are in the OS booting stage? Does the AWS console indicate that the machines are running or still initializing? Is this behavior impacting all roles/farms or only this one? If only this farm is impacted, what is different about this farm or role that could be causing the failure to boot? This information should help you isolate why these instances are failing to boot when other farms previously launched successfully for you.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Monday, October 10, 2016 at 7:37:07 AM UTC-6, Amit Saini wrote: > > Hi Marc, > > When I was monitoring my Server and observer some strange behavior with my > Server and EC2 Instance > > > 1. Its taking lot of time in 3rd step "*Wait for OS to finish booting*". > It take near about 40 Minutes. > > Which is same time mention in FARM setting to terminated the Instance if > not get the *Hostup *notification (Refer Image 1,2) > > > 2. If after 40 minutes, My EC2 Instance got terminated and a New instance > start running (Refer Image 3 ,4) Initialization process start again and > then 3rd step wait for 40 minutes and then terminated > > > > I have change the Instance termination 2400 Seconds to 5000 Seconds (Refer > Image 5)but got the same issue after 3rd step EC2 Instance got terminated > and new Instance start > > > > *Its look like that Instance is not able to boot the OS* > > Please Check at the security Group (Refer Image6,7) > > > Kindly Help > -- 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.
