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 (this is visible during start as the appliance taking a long time to start and then failing; the log says that appliance start timed out). To fix this, verify the appliance runs the /appliance/vma_load.sh script when it is done booting. All templates from the global catalog have this script and start it by default.

Start the application with --debug flag on the app start command; this will help ensure that CA 3Tera AppLogic will leave the appliance in start-failed state after the boot timeout has expired. For example app start myapp --debug.
attempt to SSH into the appliance using the comp ssh command. For example 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 be executed 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 got 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.

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.

Verify that the configuration files are listed in the Config Files tab of the class in the Class Editor.
Verify that the configuration files are instrumented using the ADL property markup syntax