If your appliance fails to start, the most likely reason is that the appliance is not starting the VM agent. For example, during start, the appliance takes a long time to start and then fails. The log says that appliance start timed out.
To fix this issue, verify that the appliance runs the /lib/applogic/vmad bash script when booting completes. All templates from the global catalog start this script by default.
This flag indicates the appliance is in a start-failed state after the boot timeout expires. For example, app start myapp --debug.
For example, enter comp ssh myapp:main.comp. If you can ssh into the appliance, then things are good -- get in and trace the start sequence. At some point, the VM agent needs to be loaded. At boot-complete, vme should execute with started_ok. For example vme id=started_ok.
If you cannot SSH to the appliance, then most likely the volume or its boot configuration may have become corrupted. You can stop the application, manage, and inspect the volume or start from the template again. If the problem reoccurs, contact Technical Support.
If your network is not working, consider the following information to obtain shell access to the appliance:
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|