Symantec Privileged Access Management

 View Only
  • 1.  CA PIM

    Posted Sep 01, 2017 12:26 AM

    In Red Hat-Linux



    What is the solution?

  • 2.  Re: CA PIM

    Posted Sep 08, 2017 05:53 PM

    Hi Suhang,


    This would indicate seosd is not able to handle messages fast enough, seoswd did not receive heartbeat of seosd in the timeout period so it killed old seosd and started new seosd.


    If this would continue and impact functionality of product I suggest to open a support case where it can be further investigated.