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...
Cause
Red Hat has made some changes which causes the GIM installation script can't correctly update runlevel information for system services.
Environment
RHEL 6 with GIM client release lower than r64382
Diagnosing The Problem
If file /etc/lsb-release exists on your RHEL system and there is no link to file /etc/rc.d/init.d/upguard in /etc/rc.d/rc*.d directories, then you are facing this problem.
Resolving The Problem
The problem is fixed in GIM client release r64382. For lower release of GIM client please go through the steps below to solve the problem.
1.Check whether guard_tap.ini configuration file is renamed to guard_tap.ini.err or not. The file resides in <GIM_installation_dir>/modules/STAP/current, if it is renamed, recover the file by following steps.
a) stop SUPERVISOR as it will continuously rename guard_tap.ini to guard_tap.ini.err
initctl list | grep gsvr
The output of the the command is like below:
gsvr_57263 start/running, process 4282
Then issue the stop command according to the your above output:
stop gsvr_57263
b) rename the file back
cd <GIM_installation_dir>/modules/STAP/current
mv guard_tap.ini.err guard_tap.ini
chmod 640 guard_tap.ini
2.Manually update runlevel information for system services so that the problem will not reoccur when you reboot your system again.
/sbin/chkconfig --add upguard
3.Now you can reboot your system to solve the problem. If an immediate system reboot is not allowed, you can issue the following command to start STAP manually:
/etc/init.d/upguard start
If SUPERVISOR is stopped in step 1, start it like the example below:
start gsvr_57263
Then you can check that STAP should be started and running.
ps -ef | grep stap
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21680476