Troubleshooting
Problem
Guardium STAP process does not start when "init q" is issued and /etc/inittab line is too long on some Operating Systems
Symptom
After installing the Guardium STAP to an alternate directory than the default /usr/local, the STAP does not start.
A message similar to the following can be seen in the syslog when "init q" is issued to attempt to start STAP
for example the /var/log/messages contains a message
/etc/inittab[100]: process field too long
Cause
This can happen if the utap line entry in the /etc/inittab is too long (for example over 127 characters)
For example - at installation time the installation directory was changed from the default /usr/local to be
/usr/local/guardium_v82_r57354_1
This caused the utap line entry to be too long in the /etc/inittab file
- utap:2345:respawn:/usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_stap /usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_tap.ini
on this system
- vmguard6:~ # uname -a
Linux vmguard6 2.6.32.45-0.3-default #1 SMP 2011-08-22 10:12:58 +0200 x86_64 x86_64 x86_64 GNU/Linux
vmguard6:~ #
vmguard6:~ # more /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
vmguard6:~ #
Resolving The Problem
To resolve the issue one of the following actions can be taken. 1) is preferred ..
1) - uninstall the product and install into a shorter directory name - eg the default directory /usr/local
- OR
to make a soft link - for example
ln -s /usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_tap.ini /var/guard_tap.ini
edit the /etc/inittab accordingly - wit the /var/guard_tap.ini at the end instead of the original long directory/path/file
utap:2345:respawn:/usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_stap /var/guard_tap.ini
start the STAP with init q
vmguard6:~ # init q
The STAP process can be checked by for example
vmguard6:~ # ps -ef | grep -i tap
root 6275 1 94 15:22 ? 00:00:01 /bin/bash -f /usr/local/guardium_v82_r57354_1/guardium/guard_stap/guard_stap /var/guard_tap.ini
root 6296 4031 0 15:22 pts/0 00:00:00 grep -i tap
By using a soft link - this will allow the original guard_tap.ini file to be amended manually or via GIM as normal - and have those changes reflected in the linked file - hence no extra maintenance would be needed on the linked file .
Example information on the limitation
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21883450