EEM not started after a reboot or not starting.
search cancel

EEM not started after a reboot or not starting.

book

Article ID: 50809

calendar_today

Updated On:

Products

CA Security Command Center CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description:

This document explains why EEM might fail to start. The ownership of the DXSERVER log files must to be set to DSA ETRDIR , and the DXSERVER needs to be started by the DSA user or via the rc script.

Solution:

  1. Make sure that the ownership of the logs files under : /opt/CA/Directory/dxserver/logs is set to dsa etrdir as follow :

    -rw-r----- 1 dsa etrdir 2372 2010-09-17 16:51 dxadmind.log
    -rw-r----- 1 dsa etrdir 27646 2010-09-17 16:51 dxserver-rc.log
    -rw-r----- 1 dsa etrdir 5817 2010-09-29 15:37 iTechPoz-xxxxxxx_alarm.log
    -rw-r----- 1 dsa etrdir 5545 2010-09-29 15:37 iTechPoz-xxxxxxx-Router_alarm.log
    -rw-r----- 1 dsa etrdir 7594 2010-09-29 15:37 iTechPoz-xxxxxxx-Router_trace.log
    -rw-r----- 1 dsa etrdir 7985 2010-09-29 15:37 iTechPoz-xxxxxxx_trace.log
    -rw-r----- 1 dsa etrdir 4063 2010-09-17 16:51 iTechPoz-Server.log
    -rw-r----- 1 dsa etrdir 444 2009-09-28 07:34 logs.help

    If it is not, run the command :

    chown dsa:etrdir /opt/CA/Directory/dxserver/logs/*          as Root

  2. In order to start the DSA, 2 methods :

    Method 1:
                       [[email protected] ~]$ su root           Password: enter the password          [[email protected] caelmadmin]# su - dsa           dxserver start all    ( to start the DSA )           dxserver stop all     ( to stop the DSA )           dxserver status      ( to check the status of the DSA )
    Method 2 :
                [[email protected] ~]$ su root           Password: enter the password            /etc/rc.d/init.d/dxserver start  ( to start the DSA )             /etc/rc.d/init.d/dxserver stop   ( to start the DSA ).
  3. Any failure to use the above procedure to start the DSA, or having the ownership of the logs files set correctly, might result in the following errors in /var/log/messages :
               Oct 11 08:26:20 lod1389 iTechPoz-xxxxxxxx: LOG: Unable to open log file 'logs/iTechPoz-xxxxxxxx_alarm.log': Permission denied         Oct 11 08:26:20 lod1389 iTechPoz-xxxxxxxx-Router: LOG: Unable to open log file 'logs/iTechPoz-xxxxxxxx-Router_alarm.log': Permission denied         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx: LOG: Unable to open log file 'logs/iTechPoz-xxxxxxxx_trace.log': Permission denied         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx-Router: LOG: Unable to open log file 'logs/iTechPoz-xxxxxxxx-Router_trace.log': Permission denied         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx-Router: DSA_E1280 Error in initialization files         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx-Router: DSA_I1240 DSA shutting down         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx: DSA_E1280 Error in initialization files         Oct 11 08:26:21 lod1389 iTechPoz-xxxxxxxx: DSA_I1240 DSA shutting down

***** with xxxxxxxx being the hostname throughout the document *****

Environment

Release:
Component: CAELM