Using CA AppLogic › Grid User Guide › Grid Troubleshooting

Grid Troubleshooting

This section contains the following topics:

Appliance Start

Application Start

Inaccessible Volume

Inaccessible Grid

GUI Slowdown

Appliance Start

Appliance will not 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 that the appliance runs the /lib/applogic/vmad bash 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 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, but all properties remain at their default values in the 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.

Application Start

There are multiple processes that you can use to start the application. Use the steps that that correspond with the condition that you encountered.

Inaccessible application

1. Try to login as a grid operator.
2. Restart the application using the following:

   app restart myapp
   

3. Try to login again as a grid operator
4. Restore the application to last snapshot or to initial state

Application errors due to data volume full

1. Stop the application using the following:

   app stop myapp
   

2. Resize the application's data volume by doing the following:
   1. Verify the current volume size using the following:

      vol list myapp --all
      

   2. To resize, do the following:
      • Grid server: vol resize myapp:GSC.boot size=20G
      • cPanel: vol resize myapp:cPanel.boot size=20G
3. Restart the application using the following:

   app stop myapp
   

Inaccessible Volume

Volumes may be inaccessible for one of the following reasons:

• Volume does not exist
• Volume is already mounted
• Volume is in error state or needs repair/migration

To verify that the volume exists, execute vol info name. If the volume does not exist, create the volume; see vol create command.

To verify if the volume is mounted, execute vol info name and inspect the volume mount state. If the volume is mounted, the volume is in use either by an appliance or by another user who is executing a volume operation over that volume. You must either stop the application that is using that volume or wait until the volume operation over that volume has completed.

To verify if the volume needs repair, execute vol repair --status and inspect whether the volume is in the list.

If the volume is in error state, verify that all servers on which the volume mirrors reside are up and operational - execute vol info name to see on which servers the mirrors reside.

If the volume needs repair - attempt to repair the volume - execute vol repair name.

If the volume needs migration you can attempt to migrate the volume using vol migrate name. However, the fact that a volume needs migration should not result in it being inaccessible.

Inaccessible Grid

If the grid is inaccessible, the grid controller is either down, the user with which you are trying to log into the grid controller has not been created, or the SSH key you are using is incorrect if trying to connect via SSH. You should contact your grid administrator or Technical Support if this occurs.

GUI Slowdown

Sometimes, if there is heavy load being put upon the grid controller - typically due to a heavy I/O operation (for example, copying volumes), the GUI may seem slow and should begin responding normally when the operation is complete. If the GUI remains slow for an extended period of time, you should contact your grid maintainer or Technical Support.