S-TAP does not start automatically on Linux

If the S-TAP agent for DB2 or Oracle does not start automatically on Linux, check for the /etc/event.d/ directory.

Symptoms

The S-TAP process does not automatically start on Linux even though the /etc/inittab file shows a correct U-TAP entry.

Causes

Various Linux distributions such as RedHat 6 deprecated the use of the traditional init daemon that uses the etc/inittab file. They 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 such as U-TAP.

The S-TAP installer 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.

If /etc/event.d is missing for any reason on a system with upstart, the inittab file is populated instead. The S-TAP process does not start or respawn when needed.

Environment

S-TAPs running on Linux are affected.

Resolving the problem

Check for the existence of the /etc/event.d/ directory.

If the /etc/event.d/ directory does not exist, complete the following steps to resolve the situation.

  1. Uninstall the existing S-TAP installation.
  2. Create the /etc/event.d dir as user root (mkdir /etc/event.d) .
  3. Install the S-TAP.