Layer7 Privileged Access Management

Expand all | Collapse all

several CA PIM AgentManager process

Jump to Best Answer
  • 1.  several CA PIM AgentManager process

    Posted 10-14-2018 04:45 PM

    HI gurus,

    I have a several SLES 11 sp4 s390x servers with this issue.

    Any boby can help me to resolve Why CA PIM has several AgentManager process running?

     

    tepsp:/opt/infosec/pim/log # ps -fea | grep AgentManager
    root     10786     1  0 02:00 ?        00:00:33 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     15459     1  0 03:46 ?        00:00:29 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     19125     1  0 05:01 ?        00:00:26 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     22582     1  0 06:16 ?        00:00:23 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     25327     1  0 07:16 ?        00:00:20 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     27359     1  0 08:02 ?        00:00:19 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     29267     1  0 08:47 ?        00:00:18 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     30735     1  0 09:17 ?        00:00:16 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     32140     1  0 09:47 ?        00:00:15 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     33527     1  0 10:17 ?        00:00:15 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     34889     1  0 10:47 ?        00:00:13 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     36721     1  0 11:33 ?        00:00:12 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     38124     1  0 12:03 ?        00:00:11 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     39494     1  0 12:33 ?        00:00:10 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     40852     1  0 13:03 ?        00:00:10 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     42204     1  0 13:33 ?        00:00:09 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     43572     1  0 14:03 ?        00:00:08 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     45401     1  0 14:48 ?        00:00:06 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     46764     1  0 15:18 ?        00:00:05 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     48137     1  0 15:49 ?        00:00:05 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     50946     1  0 16:19 ?        00:00:03 /opt/infosec/AccessControlShared/bin/AgentManager start
    root     50965 50946  0 16:19 ?        00:00:03 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent
    root     51384 51139  0 16:29 pts/2    00:00:00 grep AgentManager
    root     59035     1  0 Oct13 ?        00:00:45 /opt/infosec/AccessControlShared/bin/AgentManager -watchdog -plugin PupmAgent

     

    I found these messages on /var/log/messages 

     

    Oct 13 22:44:49 tepsp IBM Java[59015]: Starting plugin PupmAgent
    Oct 14 02:00:35 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 02:00:54 tepsp IBM Java[10776]: Starting plugin PupmAgent
    Oct 14 03:45:57 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 03:46:03 tepsp IBM Java[15440]: Starting plugin PupmAgent
    Oct 14 05:01:17 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 05:01:23 tepsp IBM Java[19106]: Starting plugin PupmAgent
    Oct 14 06:16:37 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 06:16:42 tepsp IBM Java[22563]: Starting plugin PupmAgent
    Oct 14 07:16:51 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 07:16:56 tepsp IBM Java[25308]: Starting plugin PupmAgent
    Oct 14 08:02:00 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 08:02:05 tepsp IBM Java[27338]: Starting plugin PupmAgent
    Oct 14 08:47:09 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 08:47:14 tepsp IBM Java[29248]: Starting plugin PupmAgent
    Oct 14 09:17:17 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 09:17:22 tepsp IBM Java[30715]: Starting plugin PupmAgent
    Oct 14 09:47:26 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 09:47:31 tepsp IBM Java[32121]: Starting plugin PupmAgent
    Oct 14 10:17:34 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 10:17:40 tepsp IBM Java[33508]: Starting plugin PupmAgent
    Oct 14 10:47:43 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 10:47:49 tepsp IBM Java[34869]: Starting plugin PupmAgent
    Oct 14 11:32:57 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 11:33:02 tepsp IBM Java[36702]: Starting plugin PupmAgent
    Oct 14 12:03:06 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 12:03:11 tepsp IBM Java[38104]: Starting plugin PupmAgent
    Oct 14 12:33:14 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 12:33:20 tepsp IBM Java[39474]: Starting plugin PupmAgent
    Oct 14 13:03:23 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 13:03:28 tepsp IBM Java[40833]: Starting plugin PupmAgent
    Oct 14 13:33:31 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 13:33:36 tepsp IBM Java[42185]: Starting plugin PupmAgent
    Oct 14 14:03:35 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 14:03:40 tepsp IBM Java[43551]: Starting plugin PupmAgent
    Oct 14 14:48:48 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 14:48:57 tepsp IBM Java[45381]: Starting plugin PupmAgent
    Oct 14 15:18:54 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 15:18:59 tepsp IBM Java[46744]: Starting plugin PupmAgent
    Oct 14 15:49:02 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 15:49:07 tepsp IBM Java[48118]: Starting plugin PupmAgent
    Oct 14 16:19:06 tepsp seoswd: The Watchdog is restarting the AgentManager. The process reached the specified critical memory level (500MB).
    Oct 14 16:19:11 tepsp IBM Java[50946]: Starting plugin PupmAgent

     

    Oct 14 16:50:36 tepsp IBM Java[10786]: ERROR: Failed to connect to the Distribution Server ssl://evt-cupccmap-00.evertecinc.net:7243, rv = 1 : Exception: Failed to connect to any server at: ssl://evt-cupccmap-00.evertecinc.net:7243,ssl://evt-cupccmap-00.evertecinc.net:7243



  • 2.  Re: several CA PIM AgentManager process

    Posted 10-15-2018 04:05 AM

    Hi there

    First of all, cold you specify the version you are in ? There are several things here

     

    1. It seems to complain about the memory limit at which the watchdog will try to restart the agent. In seos.ini there is, as you know section seoswd, where you can actually specify the threshold for restarting the daemon. You may want to increase ProcVSizeCritical if you see that indeed the daemons are taking a lot of memory (and this is legitimate because of high utilization, etc)

     

    2. What I believe is not normal is that it leaves several processes running. The processes should go down and not accumulate. Have you checked if there are core dumps generated ? We have dealt in the past with cases where there were multiple process and that was solved in some patches. We need to look at your CA PIM version to find out.

     

    Best regards



  • 3.  Re: several CA PIM AgentManager process

    Posted 10-15-2018 08:49 AM

    Thanks Miguel,

     

    the issue is with CA PIM 12.8 sp1 on SuSE 11 sp4 s390x only.

     

    1.  ProcVSizeCritical = 500  -- default value

    2. No core dumps 

     

    Regards



  • 4.  Re: several CA PIM AgentManager process
    Best Answer

    Posted 10-15-2018 10:07 AM

    Please make sure you are using the latest build of PIM 12.8 SP1 for s390

    RO99373

    or

    RO99369

    which you can download from

    CA Privileged Identity Manager Solutions & Patches - CA Technologies 

     

    Should the issue remain, please open a Support Case with us and we shall investigate accordingly