Setting the CA APM Installer in debug output for troubleshooting.

Document ID : KB000030428
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

The new installers in CA APM is designed to save time and make installation easier. However, an installer might not always work. This article explains how to collect debug information from an installer.

Solution: 

The installer can produce three kinds of debug information:

  1. runtime debug output
  2. log files
  3. installer variables

Collecting Runtime Debug Output

The installer can print debug output while running, but it does not send the output to the installation logs. However, you have several choices  where to send the different types of output:

Important: Before sending any debug output to a console, make sure that the terminal buffer is large enough to hold several thousand lines.

Method 1 – Send Windows debug output to a console

  1. Hold down the Ctrl key.
  2. Double-click on the installer.exe file.
  3. Continue to hold down the Ctrl key while the installer extracts its files. Eventually, a console window containing the debug output will appear.

The console window will disappear when the installation process is complete.

Method 2 – Send Windows debug output to a file

 

  1. Open the lax file in a plain text editor.
  2. Find these lines:
    lax.stderr.redirect=
    lax.stdout.redirect=
    Modify them to include values such as:
    lax.stderr.redirect=C:\\installer.stderr.txt
    lax.stdout.redirect=C:\\installer.stdout.txt
  3. Execute Installer. The installer will print debug output to the files you specified.

Method 3 – Send Windows or Unix debug output to a console

  1. Open a command prompt.
  2. Set the environment variable LAX_DEBUG to true.

    On Windows:
    C:\> set LAX_DEBUG=true
    On Unix:
    [root@sunbox:/] LAX_DEBUG=true
    [root@sunbox:/] export LAX_DEBUG/code>
  3. Invoke the installer from the command line. The installer will print debug output to the console.

This console will remain open when the installer process finishes.

Method 4 – Send Unix output to a console

This method is only for bin installers. Use it only if #3 does not work.

  1. Open a command prompt.
  2. Invoke the installer using the following command:
    sh -x installer.bin
    The installer will print detailed debug output to the console.

Method 5 – Send pure Java installer debug output to a console

This method is only for jar installers.

  1. Open a command prompt.
  2. Change to the directory in which the installer jar file resides.
  3. Run this command to create a file called ia_debug:
    touch ia_debug
  4. Invoke the installer. The installer will print debug output to a console.

Viewing and Collecting Installation Log Files

If the installer runs to completion, it will create a number of logs in the install folder, located in the Introscope root directory.

  • The main log is Introscope_InstallLog.log and contains a record of all actions taken by the installer.
  • The other log files contain information about specific Ant configuration tasks run during the installation.

To find problems in these logs:

  1. Open Introscope_InstallLog.log in a text editor.
  2. Search for the word "ERROR" to locate any errors.
  3. If an error occurred in an "Execute ANT Script" action, get additional information by searching the other log files for the word "ERROR" or "FAILED." A good place to start is with the log that was last modified.

Viewing and Collecting Installer Variables

In some cases, Wily's Support team may need to obtain a list of the variables that the installation program used during runtime. If the installer runs to completion, it will store these variables in up to three different locations: 

  1. A partial set of variables will always be written to autogenerated.responsefile in {Introscope_root}/install.
  2. A different partial set of variables will always be written to the file installvariables.properties in {Introscope_root}/UninstallerData.
  3. You can tell the installer to write a complete set of variables to the file installvariables.txt in {Introscope_root}/install by appending the following switch to the installer start command:
    -DdumpDebugVars=true
    This is true for all platforms and modes. For example, for the bin installer on Unix, you would use this command:
    [root@sunbox:/] ./introscope5.0solaris.bin -DdumpDebugVars=true