IBM Support

InfoSphere Guardium STAP is not running after system reboot under GIM installation on RHEL system

Troubleshooting


Problem

You successfully installed STAP on Red Hat Enterprise Linux(RHEL) by Guardium Installation Manager(GIM). But after a reboot of the RHEL system, you observed that STAP was inactive or offline.

Symptom

STAP can run normally before the system reboot, but after system reboot, stap process is not started while GIM and SUPERVISOR processes are started and running.

In <GIM_installation_dir>/modules/central_logger.log, you will see the following message:


./init_installer: line 154: update-rc.d: command not found

And the /var/log/messages file on RHEL system may contain the following message:


Tap_controller::init failed Opening pseudo device /dev/guard_ktap No such file or directory. Sleeping...
GUARD-01: Error Initializing STap Opening pseudo device /dev/guard_ktap No such file or directory. Sleeping...

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Guardium Database Activity Monitor","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.1;9.0","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
16 June 2018

UID

swg21680476