Hi Krishna, To confirm, no servers are initializing correctly including those built from our shared roles? Did you also run the scalr-server-ctl reconfigure command after completing installation? If so, you may have network configuration issues preventing proper communication between Scalr and managed servers. On the Scalr server, relevant logs should be located within /opt/scalr-server/var/logs, and on the client the scalarizr logs should be located within /var/log/. Chances are the scalarizr.log and scalarizr_debug.log will have the most relevant entries.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Saturday, July 23, 2016 at 2:44:00 PM UTC-6, Krishna Kurkal wrote: > > Thanks for your prompt response Marc. I tried both agentless and now with > Scalr public images from the AWS shelf. I had missed putting in the IAM > policy but just plugged that in and I'm seeing the same behavior. > > Anything else I might be missing? Also, where are all the logs? Which > log files should I be looking at under /opt/scalr-server/var/log location > or are the pertinent logs located elsewhere? > > Thanks, > Krishna > > On Friday, 22 July 2016 17:26:22 UTC-5, Marc O'Brien wrote: >> >> Hi Krishna, >> >> Have you installed the agent on these images? If not, were these images >> mapped to an agentless role after you registered them with Scalr? Are you >> able to successfully launch other roles? Also, did you complete the IAM >> set up for AWS as described here >> <https://scalr-wiki.atlassian.net/wiki/display/docs/Adding+Amazon+EC2+Credentials+-+Walkthrough> >> ? >> >> Many thanks, >> Wm. Marc O'Brien >> Scalr Technical Support >> >> >> >> On Friday, July 22, 2016 at 4:01:15 PM UTC-6, Krishna Kurkal wrote: >>> >>> Hello, >>> >>> I think I have all the ports open on both, the scalr mgmt node and the >>> the SG that the provisioned VMs use (using AWS as the cloud provider here), >>> as per requirements listed here: >>> https://scalr-wiki.atlassian.net/wiki/display/docs/Required+Network+Configuration+for+Scalr >>> . >>> >>> But instance seem to keep ending up in the 'pending' state and >>> eventually terminating. The 2 instance's I have been trying are built from >>> images with AMI IDs of 'ami-6869aa05' (Amazon Linux) and 'ami-0129cc68' >>> (CentOS). >>> >>> For CentOS spin up, AWS console also shows that the instance >>> reachability test failed but AWS Linux shows everything passed in AWS >>> Console. However, I'm unable to ssh into the VMs using the public key and >>> Scalr is ending up in the pending state and terminating. >>> >>> Any ideas on where the root cause might lie? >>> >>> >>> Thanks, >>> Krishna >>> >> -- 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.
