Troubleshooting
Problem
Why does the S-Tap process not start automatically on Linux ?
Symptom
The "/etc/inittab" file shows a correct utap entry but the process does not start
Cause
Various Linux distributions such as RedHat 6 have deprecated the use of the traditional init daemon that utilises the "etc/inittab" file and replaced it with an init process called "Upstart".
Upstart uses the "/etc/event.d" and "/etc/init" directories for the automated start , stop and respawn of processes like utap.
The S-Tap installer (both native and GIM) now checks for the existence of the "/etc/event.d" directory. If it exists then entries in "/etc/init" are created for use by Upstart. If it does not exist then entries in "/etc/inittab" are created for use by the traditional init daemon.
The result is that if "/etc/event.d" is missing for any reason on a system using Upstart the inittab file will be populated instead and the stap process will not start or respawn when needed.
Diagnosing The Problem
Check for the existence of the "/etc/event.d/" directory.
Resolving The Problem
If the "/etc/event.d/" directory does not exist, do the following to resolve the situation:
- Un-install the existing S-Tap installation
- Create the /etc/event.d dir as user root ( mkdir /etc/event.d )
- Re-install the S-Tap
Was this topic helpful?
Document Information
Modified date:
12 December 2019
UID
swg21624395