There are many things that could be going on. permission issues, missing resources, mis matched regions or zones, zone availability of resource, simple typeos. The first step I recommend is looking at the variety of logs available. That should help you narrow down the issue.
Console log. In AWS Console select the instance and look at "Console Log" - this is the initial boot log, it won't appear on the filesystem - some 'obvious' messages may be hidden here. System Logs: ssh into the instance and look at /var/log/messages /var/log/mlcmd dmesg Check if the ML is running or not. SNS logs - these have the most detail by far. Create an "SNS" endpoint, and a subscription - the simplest is email - you will get 1 email message per event (about 200 events per node on startup). These have very detailed information every step of the startup process. Enter the SNS name into the "Log SNS" parameter in CF. In Cloud Formation - use the Advanced section and also subscribe the Cloud Formation events as well to the same SNS. This will get you notifications of AWS's side of things. Use CloudTrail and Configure features of AWS to see if there were errors during the startup process. Look at the ASG and CF Event logs. If those don't give you enough clues then write back with what you've found out. ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation [email protected] Phone: +1 812-482-5224 Cell: +1 812-630-7622 www.marklogic.com<http://www.marklogic.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Gulik, Ernest Sent: Friday, June 19, 2015 5:31 PM To: 'MarkLogic Developer Discussion' Subject: [MarkLogic Dev General] MarkLogic 7 cloudformation template does not start MarkLogic service Hello all, I'm working on standing up ML instance on AWS and I use cfn for ML7 with ami-7673661e but after the instance is launched MarkLogic service is not started. I can wait and wait and nothing will happen or I can do one of these 2 actions (tried them both in separate instances): - Restart the instance which will start initialization and eventually start the service - Execute 'service MarkLogic start' which will start initialization and start the service When I launch ec2 instance using cfn template for ML8 which uses ami-5494c93c then service is initialized and started automatically but not in the case of ML7. Cloudformation template is using autoscaling group so once new instance is launched, ML service will not be started until 'human intervention' will happen. Could someone please explain to me why this is happening and what is the best way to fix that problem? Thank you, Ernest G.
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
