Tips on Troubleshooting ElasticBox¶
Check the solutions to common issues before you contact ElasticBox 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 ElasticBox agent step
- Quick start box not installing properly
- ElasticBox 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 ElasticBox 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 ElasticBox cloud service:
curl -ks ebx.co | sudo bash
Windows instances deployed from the ElasticBox cloud service (run the command as a PowerShell administrator):
(New-Object Net.WebClient).DownloadString("http://ebx.co") | iex
Linux instances deployed from the ElasticBox Appliance:
curl -ks 10.0.0.1 | sudo bash
Windows instances deployed from the ElasticBox 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 ElasticBox agent can’t connect to ElasticBox. 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 ElasticBox, 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.
ElasticBox 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 ElasticBox 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
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 ElasticBox 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 ElasticBox. The agent should start deploying.