Symantec Access Management

 View Only
  • 1.  [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure

    Posted Mar 12, 2018 11:53 AM

    Please help to to find cause of the Errors:

    "[FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure"

     

    [09 Mar 2018 21:23:54,490] [main] [INFO] The SiteMinder Agent is initializing ..
    [09 Mar 2018 21:23:54,490] [main] [INFO] SiteMinder Product Details: PRODUCT_VERSION=12.0 , PRODUCT_NAME=eTrust SiteMinder Agent for IBM WebSphere, PRODUCT_
    UPDATE=0200 , PRODUCT_LABEL=210.
    [09 Mar 2018 21:23:54,490] [main] [INFO] Administration Manager is trying to create configuration for the SiteMinder Agent
    [09 Mar 2018 21:23:54,519] [main] [INFO] Creating agent connection using file : <CA SSO WebSphere Agent installation Path>/smwasasa/conf/<WebAgent>.conf
    [09 Mar 2018 21:23:56,257] [main] [INFO] Registering the Configuration Manager with the Policy Server
    [09 Mar 2018 21:23:56,330] [main] [INFO] Obtained data from the Policy Server for Agent Config Object "<ACO>"
    [09 Mar 2018 21:23:56,330] [main] [INFO] Configuration Manager is creating the Configuration Management thread with pspollinterval of 30 seconds
    [12 Mar 2018 11:06:23,725] [Thread-33] [INFO] Obtained data from the Policy Server for Agent Config Object "<ACO>"
    [12 Mar 2018 11:06:[12 Mar 2018 11:06:41,105] [Thread-27] [INFO] Obtained data from the Policy Server for Agent Config Object "<ACO>"
    [12 Mar 2018 11:06:41,105] [Thread-27] [INFO] Creating logger interface ..
    gement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure
    [09 Mar 2018 22:01:33,680] [Thread-33] [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure
    [09 Mar 2018 22:03:36,264] [Thread-33] [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure



  • 2.  Re: [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure

    Posted Mar 12, 2018 11:58 AM

    Your logs are not in sync.

     

    There is mix up between 9th and 12th March data.

    Can we just get log from one day?

     

    Sent from my iPhone



  • 3.  Re: [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure

    Posted Mar 12, 2018 12:00 PM

    bellamkishore

     

    Could you confirm the following.

     

    A. All Policy Servers defined in HCO is up and running.

     

    B. The log lines you pasted seem kind of notorious. If we look at the date and timestamp. They start on 9th March, then go on to state 12th March, but ends again with 9th March. Is the log file correct OR you just copy pasted different lines.

     

     

    Regards

    Hubert



  • 4.  Re: [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure
    Best Answer

    Broadcom Employee
    Posted Mar 19, 2018 11:11 AM

    Hi Venkata Keshore,

     

    Based on your log snippet, this is the BASE R12 SP2 (Build 210) Application Server Agent for WebSphere. This issue is fixed with the "Build 213" "Need it Now" (NIN) release. Please open a Support Case to obtain the "Build 213" NIN which contains the fix for this issue.

     

    Thanks,

     

    Rick



  • 5.  Re: [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure

    Posted Apr 11, 2018 11:22 AM

    Hi Rick,

     

    Thanks for the Update.

     

    Please conform any separate installers for  "CA SSO Websphere Agent" for 64-bit and 32-bit

     

    We have Websphere Portal Applications where IBM HTTP Server is 32-bit so we have installed a 32-bit CA SSO Agent for enabling TAI.

     

    So, we need a 32-bit CA SSO Websphere Agent for the same.



  • 6.  Re: [FATAL] The doManagement Thread failed as the Policy Server could not be reached. Reason: Agent API Failure

    Broadcom Employee
    Posted Apr 11, 2018 12:24 PM

    Hi Venkata Kishore,

     

    The R12 SP2 Application Server Agent for WebSphere is a Java Agent that runs under WebSphere (Not Apache) in the WebSphere Runtime version of Java. There is not a separate 32 bit vs. 64 bit installer.

     

    Thanks,

     

    Rick