Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › Troubleshooting Guidelines

Troubleshooting Guidelines

Application won’t start

There are typically a handful of reasons that an application won’t start. Here are a few but the first thing to do in every situation is check the logs.

Causes:

• Not enough resources available for what the app has been allocated
• Something is wrong with an appliances boot process (Disk/nfs won’t mount)
• Currently running VM’s under high load (iowait,st processes, etc,etc)
• General mis-configuration not limited to network or storage volumes
• Orphaned or corrupt volume
• Bad/corrupt/misconfigured appliance template

Troubleshooting Steps:

• First simply try to restart the application again and see if it continues to fail.
• Start the application in debug mode, <appname start --debug>. You can then ssh into the appliance and check the applogic_init.log for any errors. You can also try to log into the graphical interface also to see if any errors are occurring.
• Possibly the boot volume is full, check the free space on the boot volume and if necessary expand the size with the vol manage command.
• Run a log list command on the controller and check for any log messages with that application when you try to start it.

Server won’t start/Component won't start

Causes:

• Most likely related to any of the above “Application Won’t Start Issues”
• Server mis-configuration, corrupted boot process

Troubleshooting Steps:

• Check the servers console (monitor) and see what messages are coming up.
• Verify you can access the servers bios and no hardware changes were made
• Verify the systems memory is Ok
• Verify the disks are not going bad
• Check for a kernel panic or blue screen during a boot
• Verify the network connection on the server is functioning properly.

Grid is down

Causes:

• Most often is hardware related. Switch/Harddrives/PDU, but from what I have been told there are no longer any single points of failure within the controller code so if a customer has redundant controllers and redundant hardware this shouldn’t be a very relevant issue.
• ·Act of God

Troubleshooting Steps:

• · Verify the servers on your grid are up and running properly.
• · Verify there is no network connectivity issue between grid servers
• · Verify you have access to the grid controller. Endure the user and password are correct and your ssh keys are configured for access.
• · Try to restart the grid controller, grid reboot -controller [-force] restart grid controller.