lksupport

lksupport, found in the /opt/LifeKeeper/bin/ directory, is used to collect important configuration information and log files and place them in a compressed tar file. SIOS Support Engineers will commonly request this tar file as part of the Support process.

To run this utility, please execute the following:

1. sudo su
2. /opt/LifeKeeper/bin/lksupport

Repeat the previous steps for each node in the cluster
This will create a .tar file for each node under the directory: /tmp/lksupport

EXAMPLE: /tmp/lksupport/myhostname01.lksupport.2603201056.tar.gz

*Note: If lksupport is generated after the issue event, it may miss relevant message files. Please include the specific message files covering the issue time along with the lksupport tar file.

Options:
Default (No switch): Includes the last 200,000 lines of /var/log/lifekeeper.log and /var/log/messages along with relevant configuration information. (Recommended method)

--full – Switch to capture the entire LifeKeeper log set. Caution the resulting tar file may be several hundred MiB.

--help – Displays command usage information

--nohanatraces – Skip collection of HANA trace logs

--hanaonly – Only collect HANA information

--nooracletraces – Skip collection of oracle trace logs

--oracleonly – Only collect Oracle information

Best Practice: Use the default setting unless a SIOS Support Engineer specifically requests the --full switch or any other options.

Addons:

Some patches, hotfixes and generic application kits require expanded data collection. Lksupport supports modular addon scripts. Simply place them in the designated directory with the correct permissions to include them in the lksupport logs.

*Note: Addons scripts should not be used unless working with a SIOS Support Engineer

To be successfully integrated into the lksupport bundle, addon scripts must adhere to the following specifications:

• Location: Scripts must be placed in the /opt/LifeKeeper/bin/lksupport.d directory.
• Permissions: All scripts in the lksupport.d directory must have executable permissions.
• Arguments: Addon scripts must accept a -d parameter, which specifies the target lksupport output directory. No other parameters are supported.
• Output Naming:
  Scripts should output to a file in the target lksupport output directory using the following naming convention:
  • <filename>.<lksupport_addon_name>.txt
  • Example: hanatrace.lkhana_trace_collector.txt

• In the event of a failure, all STDERR output will be mirrored to the command line and output to a debug file in the target lksupport output directory using the following naming convention
  • <lksupport_addon_name>.error.txt
  • Example: lkhana_trace_collector.error.txt