Linux-UNIX: Using guard-config-update to start, restart, and stop S-TAP, and view status

You can use the guard-config-update utility to update your S-TAP configuration (without using the GUI), whether S-TAP was installed with GIM, RPM, or shell.

Before you begin

For all commands, <filepath> is the path to the guard-config-update utility, where the path depends on your installation type, as follows,
  • Shell installation - Default path = /usr/local/guardium/bin/guard-config-update
  • GIM installation - Default path = /usr/local/modules/STAP/current/guard-config-update
  • RPM installation - Default path = /opt/guardium/bin/guard-config-update
Note: If your site does not use the default filepath, make sure you know the correct location for the guard-config-update utility.

Procedure

  1. Log in to the database server as root.
  2. To stop S-TAP: 
    # /<filepath>/guard-config-update --stop stap
Stopping STAP
utap stop/waiting
#
  3. To start S-TAP: 
    # /<filepath>/guard-config-update --start stap
Starting STAP
utap start/running, process 14969
#
  4. To restart S-TAP: 
    # /<filepath>/guard-config-update --restart stap
Restarting STAP
utap start/running, process 15331
#
  5. To show S-TAP status: 
    # /<filepath>/guard-config-update --status
Running services:
    STAP   : root     15331     1  0 14:14 ?        00:00:00 /usr/local/guardium/guard_stap/guard_stap /usr/local/guardium/guard_stap/guard_tap.ini

Services configured:
    STAP   : enabled
    TEE    : disabled
    MONITOR: disabled

DAM plaintext connections:
tcp        0      0 9.70.147.17:24007           9.32.132.217:16016          ESTABLISHED 
tcp        0      0 9.70.147.17:51791           9.32.132.217:16016          TIME_WAIT   
DAM TLS connections:
None
FAM plaintext connections:
None
FAM TLS connections:
None

TLS is disabled

STAP debug is not enabled via config

System info:
    RESTART METHOD: upstart
#