IBM Support

How to collect STAP debug information on the Database Server (Unix/Linux).

Question & Answer


Question

If the STAP fails to start on the Database server, you may need look for the cause of the failure in existing log files and/or collect additional debugging information.

Answer

First, you should look at the standard STAP log files:

    /tmp/guard_stap.stdout.txt
    /tmp/guard_stap.stderr.txt

If the information in these files does not help to solve the problem, you may need to collect additional debugging information.

Log in with root credentials, make sure STAP is not running and start STAP in debug mode:
    /usr/local/guardium/guard_stap/guard_stap \
    /usr/local/guardium/guard_stap/guard_tap.ini 4 \
    > /tmp/stap_debug.log 2>&1

This command will start STAP in debug mode level 4 and will redirect stdout and stderr to a file.

Note: this command assumes you have STAP installation and guard_tap.ini file in the default directories.

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"10.0;10.1;8.2;9.0;9.5","Edition":"All Editions","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21508137

Page Feedback