Layer7 Privileged Access Management

Expand all | Collapse all

PROCESS IS NOT RUNNING

Jump to Best Answer
  • 1.  PROCESS IS NOT RUNNING

    Posted 01-18-2018 04:58 AM

    Hi Team,

     

    I am getting problem on server : gotsvl1032, Control minder is not starting

     

    gotsvl1032:~ # seload
    CA ControlMinder seload v12.80.0.1432 - Loader Utility
    Copyright (c) 2013 CA. All rights reserved.
    18 Jan 2018 10:53:02> WAKE_UP : Server going up
    18 Jan 2018 10:53:02> INFO    : Filter mask: 'WATCHDOG*' is registered
    18 Jan 2018 10:53:02> INFO    : Filter mask: 'INFO    : Setting PV*' is registered
    18 Jan 2018 10:53:02> INFO    : Filter mask: 'INFO    : DB*' is registered
    18 Jan 2018 10:53:02> INFO    : Filter mask: '*seosd.trace*' is registered
    18 Jan 2018 10:53:02> INFO    : Filter mask: '*FILE*secons*(*/log/*)*' is registered
    Starting seosd. PID = 24389.
    Checking database ...

     

    gotsvl1032:~ # issses
    -bash: issses: command not found
    gotsvl1032:~ # issec
    CA ControlMinder version 12.8 installed in /usr/seos
    VeRsIoN: 12.80-0 (1432) Compiled On:Nov 14 2013 22:59:39  Kernel: 2.6.16.60-0.54.5-SUSE10c _LINUX100SUSEcX86_64.X86_64 STOP 30032
    CA ControlMinder kernel extension is loaded.
    CA ControlMinder daemons are not running.
    CA ControlMinder security daemon is not running.
    CA ControlMinder watchdog daemon is not running.
    CA ControlMinder agent daemon is running, pid=2014 (agent)
    CA ControlMinder serevu daemon is not running.
    CA ControlMinder selogrd daemon is not running.
    CA ControlMinder selogrcd daemon is not running.
    CA ControlMinder eacws daemon is not running.
    CA ControlMinder ReportAgent daemon is not running.
    CA ControlMinder AgentManager daemon is not running.
    CA ControlMinder policyfetcher daemon is not running.
    CA ControlMinder KBLAudMgr daemon is not running.
    CA ControlMinder auxiliary daemon is not running.

    Control minder is going down I have tried to fix it by swapping the memory also

     

    Jan 18 10:50:01 gotsvl1032 /usr/sbin/cron[9331]: (root) CMD (/usr/local/vcc/cron/reginer.sh >/dev/null 2>&1)
    Jan 18 10:51:01 gotsvl1032 /usr/sbin/cron[15068]: (root) CMD (/usr/local/vcc/cron/reginerproxy-1min.pl >/dev/null 2>&1)
    Jan 18 10:52:01 gotsvl1032 /usr/sbin/cron[20145]: (root) CMD (/usr/local/vcc/cron/reginerproxy-1min.pl >/dev/null 2>&1)
    Jan 18 10:52:54 gotsvl1032 sshd[23689]: Accepted publickey for root from 10.255.179.172 port 32945 ssh2
    Jan 18 10:53:01 gotsvl1032 /usr/sbin/cron[24370]: (root) CMD (/usr/local/vcc/cron/reginerproxy-1min.pl >/dev/null 2>&1)
    Jan 18 10:53:02 gotsvl1032 seload[24382]: CA ControlMinder kernel extension is already loaded.
    Jan 18 10:53:02 gotsvl1032 seload[24382]: Starting /usr/seos/bin/seosd daemon. (CA ControlMinder)
    Jan 18 10:53:02 gotsvl1032 seosd[24389]: START-UP: CA ControlMinder PID=24389
    Jan 18 10:53:04 gotsvl1032 kernel: SEOS Syscall Monitor - ACTIVATED
    Jan 18 10:53:08 gotsvl1032 seosd[24389]: CA Access Control daemon going down on signal.
    Jan 18 10:53:09 gotsvl1032 seosd[24389]: PID=24389 (PPID=1) signal handler: 11
    Jan 18 10:54:01 gotsvl1032 /usr/sbin/cron[27986]: (root) CMD (/usr/local/vcc/cron/reginerproxy-1min.pl >/dev/null 2>&1)
    Jan 18 10:55:01 gotsvl1032 /usr/sbin/cron[28022]: (lpar2rrd) CMD (/home/lpar2rrd/lpar2rrd/load_hea.sh > ^I/home/lpar2rrd/lpar2rrd/load_hea.out 2>&1)

     

    Please, inform me how to fix a problem for this server

     

    Thanks in Advance



  • 2.  Re: PROCESS IS NOT RUNNING

    Posted 01-18-2018 09:31 AM

    Hi,

     

    Is that the full output from seload? If so, then I believe there is an issue with the database that is preventing the services from starting up. Please perform the following test and let me know the results.

     

    # ps -ef | grep seos ((verify that PIM services are not running))

    # selang -l  ((provide the output of this command))

     

    Thanks,

    Brian Rehder

    CA Support



  • 3.  Re: PROCESS IS NOT RUNNING

    Posted 01-18-2018 10:33 AM

    Hi Rehder,

     

    Thanks for your reply

     

    gotsvl1032:~ # ps -ef | grep seos
    root      2014     1  0 09:37 ?        00:00:00 /usr/seos/bin/seagent SEOSD
    root     24500 24450  0 16:28 pts/2    00:00:00 grep seos
    gotsvl1032:~ # selang -l
    CA ControlMinder selang v12.80.0.1432 - CA ControlMinder command line interpreter
    Copyright (c) 2013 CA. All rights reserved.

    AC>

     

    when I am providing : selang -l command it is running but I have to fix it normally

     selogrd is going down

    CA ControlMinder daemon going down.

     

    so please tell me how to fix it

     

    Thanks in Advance



  • 4.  Re: PROCESS IS NOT RUNNING

    Posted 01-18-2018 04:13 PM

    Hello,

     

    The database appears to be fine, but I noticed that seagent is still running, which could also prevent PIM from starting up. Please do the following and test if PIM can start up afterwards. If it still cannot start, then please create a support case for us to review the issue.

     

    1- Stop seagent manually.

    # kill 2014

     

    2- Even though the seosdb appears to be fine, let's reindex the database to be safe.

    Go to the seosdb directory:
    # cd /usr/seos/seosdb

    Close the database, in case it's open still:
    # dbmgr -u -close
    Check the database:
    # dbmgr -u -check
    Rebuild the database files using the following commands:
    # dbmgr -u -build seos_cdf.dat
    # dbmgr -u -build seos_pdf.dat
    # dbmgr -u -build seos_pvf.dat
    # dbmgr -u -build seos_odf.dat

     

    3- Start up PIM

    # seload



  • 5.  Re: PROCESS IS NOT RUNNING
    Best Answer

    Posted 01-19-2018 03:57 AM

    Please uninstall the PIM Client completely and install it afresh.

    Anyway, use the latest LINUX ROLLUP version of PIM 12.8 SP1 which you can download from here

    CA Privileged Identity Manager Solutions & Patches - CA Technologies 

     

    Should the problem remain, please do not hesitate to open a formal Support Case with us and we will work it accordingly