Tips on Troubleshooting Cloud Application Manager
Check the solutions to common issues before you contact Cloud Application Manager support in the case of a problem.
In this article
- Instance unreachable during an operation
- Instance is stuck deploying
- Instance is still terminating
- Instance hangs at the install Cloud Application Manager agent step
- Quick start box not installing properly
- Cloud Application Manager appliance is unavailable
Instance Unreachable During an Operation
When you trigger a lifecycle operation on an instance, it goes into a processing state because the agent is not running at all or not running properly. This problem can affect instances launched through the Cloud Application Manager web interface, the API, or directly using the agent command.
Install the agent on the instance to bring it online. Then re-run the lifecycle operation.
Connect to the instance by SSH or RDP.
Install the agent. The command uses the token of the older agent to connect to the instance.
Linux instances deployed from the Cloud Application Manager cloud service:
curl -sSL https://cam.ctl.io | sudo bash
Windows instances deployed from the Cloud Application Manager cloud service (run the command as a PowerShell administrator):
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12 (New-Object Net.WebClient).DownloadString("https://cam.ctl.io") | iex
Linux instances deployed from the Cloud Application Manager Appliance:
curl -ks 10.0.0.1 | sudo bash
Windows instances deployed from the Cloud Application Manager Appliance (run the command as a PowerShell administrator):
(New-Object Net.WebClient).DownloadString("http://10.0.0.1") | iex
Note: Replace 10.0.0.1 with your appliance IP or hostname.
Instance is Stuck Deploying
An instance can’t update its state because the Cloud Application Manager agent can’t connect to Cloud Application Manager. Poor agent network connectivity can cause this issue.
Restart the agent on the Linux or Windows instance:
sudo /usr/elasticbox/elasticbox restart
Windows (run in command prompt):
net stop elasticbox net start elasticbox
In Cloud Application Manager, open the lifecycle editor of the instance and click Reinstall. The instance should reflect the proper status.
The Linux or Windows image on the instance doesn’t have cloud-init.
Cloud Application Manager needs cloud-init for its agent to execute box script configuration on the VM image. Install cloud-init on the image and launch a new instance.
When box scripts exit with 100 typically because of apt-get failures, the Cloud Application Manager agent goes into sleep mode waiting for the machine or service to reboot.
Place the apt-get exit code in the file executing it and to the last line of executable code, add this:
[[ "$?" -eq "100" ]] && exit 1
Restart the agent on the Linux or Windows instance.
Instance is Still Terminating
Several concurrent terminate requests within seconds of each other can cause a race condition that keeps the instance in flux.
Force the instance to terminate. In the lifecycle editor of the instance, click Force Terminate.
Instance Hangs at the Install Cloud Application Manager Agent Step
Something causes the agent to hang even though it’s running on the instance.
Log in to the instance and kill the agent.
Redeploy the instance from the lifecycle editor in Cloud Application Manager. The agent should start deploying.
Quick Start Box Not Installing Properly
A broken puppet manifest or chef recipe can cause the box to not install properly.
Contact support to alert us of the broken box. In the meantime, you can define the install in a box using bash commands like apt-get, wget, cURL, and more.
Cloud Application Manager Appliance is Unavailable
When you configure the hostname, SSL certificate, or block device for the appliance, there’s a chance that the appliance may become unavailable. This issue can happen because you set the hostname incorrectly, upload a non-matching SSL certificate and key, or the block device gets corrupt, runs out of space or dismounts from the system. As a result, the appliance fails to reboot. Instance operations fail, and the appliance can’t reach deployed instances properly.
Contact support. We will walk you through recovering the appliance. Send us the appliance version number shown at the top of the setup console. And send us the logs you can download from the Logs section of the appliance setup console.
Logs help us debug your appliance issues. The .log files include recent audit information like who did what, user connections, and contain the logs of all the services.