Thanks Marat, Thank you especially for the explanation of the start sequence. I'll rebuild my 2016.03 image later this month with you change.
On Tuesday, April 5, 2016 at 6:30:51 PM UTC-6, Marat Komarov wrote: > > Hello, > > Yes, Amazon Linux 2016.03 is not yet officially supported. We'll add it > later this month. > As for your workaround, I'm glad to know that it gives you functional > Scalarizr, but it's not right to start scalr-upd-client and scalarizr > simultaneously. Instead, scalr-upd-client should start scalarizr. That's > why scalarizr is turned off in chkconfig. The same time, we know that no > one could stop users from modifying initialization order, and that's why we > have our own workaround in scalarizr that supervises for scalr-upd-client > running first. But it time, and with messed start mode it can increase > initialization time for 10-15 seconds more. So I kindly suggest reverting > back chkconfig after we'll officially add support for 2016.03 > > Check for updates on http://update.scalr.net/ > > Regards, > Marat > > On Tuesday, April 5, 2016 at 7:36:30 AM UTC-7, Jay Farschman wrote: >> >> I just built out my packer image of the Amazon Linux 2016.03 and it seems >> like it doesn't setup the scalarizr daemon to start on launch. >> >> To be clear, this is the new Amazon Linux AMI released late in March, so >> I may be the first tester: >> >> *SYMPTOMS* >> >> 1. On launch, the instance stays in the pending state in the Scalr >> WebUI >> 2. However, in the AWS EC2 console the instances is fully initialized >> and ready >> 3. Inside the instance scalarizr daemon is not started. >> 4. If I start scalarizr daemon manually, the WebUI completes the >> initialization and shows a fully launched instance >> 5. A `chkconfig --list |grep scal` shows >> >> scalarizr 0:off 1:off 2:off 3:off 4:off 5:off 6:off >> scalr-upd-client 0:off 1:off 2:on 3:on 4:on 5:on 6:off >> >> I'm rebuilding with >> > -- 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.
