Sentinel Installation fails

  • 3187357
  • 19-Dec-2006
  • 26-Apr-2012

Environment

Sentinel 5.1.x
RedHat Linux
Novell SUSE Linux Enterprise Server 9

Situation

On installation, Sentinel creates its own install dir, known as $ESEC_HOME. By default, this is in /opt/sentinel5.1.3.0.

If, however, the customer specifies containing directories ( /opt/novell/sentinel5 e.g. ) the parent directories are left with root ownership. If this installation occurs on a system with restrictive umask, the 'esecadm' user will not be able to even descend into the $ESEC_HOME directory, and all services will fail (when attempting to start via init.d, a permission denied messages is recieved).
Note: the install guide states that for the Oracle install umask must be set to '022' this also applies to the Sentinel Install.

Resolution

Check the umask of the directories and make sure it is set to'022'
An enhancement has been created for the install to be more robust in handling a restrictive umask.