I rebuilt with a change for my Packer script to make sure the daemon gets started on boot and everything works now.
#!/bin/bash # scalrizr.sh - Simply loads scalr. You will still need to use # the Scalr WebUI and import this image # "Images | New Images | Image from non-Scalr server" PLATFORM=ec2 && curl -L https://my.scalr.net/public/linux/latest/$PLATFORM/install_scalarizr.sh | sudo bash # Temporary work around for Amazon Linux 2016.03 OS_VERSION=`cat /etc/redhat-release /etc/system-release 2>/dev/null | head -1 | \ awk '{split($0, a, " release "); $0=a[2]; print $1}'` *if [[ $OS_VERSION = "2016.03" ]] ; then* * sudo /sbin/chkconfig scalarizr on* *fi* On Tuesday, April 5, 2016 at 8:36:30 AM UTC-6, 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.
