Previous Topic: Move the Appliance to a CatalogNext Topic: Modifying Appliances to Use SCSI Disks


Troubleshooting

Debugging Appliance Start

If the appliance fails to start when you start the application, 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 have this script and start it by default.

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 the volume and inspect it, or start from the template again. If the problem recurs, contact Technical Support. If your network is not working, consider the following information to get shell access to the appliance:

Appliance starts but property values are not propagated

Appliance starts OK, but all properties are left at their default values in the instrumented configuration files.

  1. Verify that the configuration files are listed in the boot volume of the appliance.
  2. Verify that the configuration files are instrumented using the ADL property markup syntax