IT Process Automation

 View Only
  • 1.  COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Posted Sep 20, 2017 11:06 AM

    Hi Team,

     

    We have installed the ITPAM Agent in one of our target node with deprecated communication. And the CA Process Automation Agent service is running perfectly in the Windows Service Console. But we are not able to check the agent status via CA ITPAM (Agent Console) in the configuration tab.

     

    Our ITPAM Application is running over https communication.

    https://<instancename>:8443/itpam

     

    ITPAM Details: -

    CA Process Automation Service Pack 04.3.02

    Version: 04.3.02
    Build: 04.3.200 - May 8, 2017 12:07:12 AM

     

     

     

    Agent Log: -

    -----------------

    2017-09-20 07:40:23,141 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] Mapping File serviceOperationMappingFilenot Found. This may be available at GUI or Source.
    2017-09-20 07:40:23,141 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] SimpleCastorXMLUtil.getMapping: failed to find mapping serviceOperationMappingFile file: serviceOperationMappingFile
    2017-09-20 07:40:30,644 WARN  [com.optinuity.c2o.util.SSLCertificateUtilities] [A Agent Startup] Setup to accept all SSL Certificates

     

    ITPAM Log: -

    -----------------

    2017-09-20 10:55:56,887 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : e2e43786-c8b3-40c1-8f0c-940689225b09 is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)
    2017-09-20 10:57:36,828 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : 86469863-9b15-44b1-be26-3fdc5aeee09c is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)
    2017-09-20 10:58:56,905 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : e2e43786-c8b3-40c1-8f0c-940689225b09 is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)
    2017-09-20 11:00:16,911 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : 86469863-9b15-44b1-be26-3fdc5aeee09c is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)
    2017-09-20 11:01:36,932 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : e2e43786-c8b3-40c1-8f0c-940689225b09 is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)
    2017-09-20 11:02:56,942 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [_autoTPRecovery] Agent with id : 86469863-9b15-44b1-be26-3fdc5aeee09c is not reachable
    com.optinuity.c2o.util.C2OException: Unidentified UUID while resolving node
     at com.optinuity.c2o.transport.Resolver.getNodeURL(Resolver.java:417)
     at com.optinuity.c2o.c2oserver.ServerManager.initiateAutomaticTouchpointRecovery(ServerManager.java:4921)
     at com.optinuity.c2o.c2oserver.ServerManager.access$400(ServerManager.java:247)
     at com.optinuity.c2o.c2oserver.ServerManager$6.run(ServerManager.java:1464)
     at java.util.TimerThread.mainLoop(Timer.java:555)
     at java.util.TimerThread.run(Timer.java:505)

     

    Kindly help us to sort out this issue.

     

    Thanks in advance.

     

    Regards,

    Arunkumar Perumal

    +91-9971559485



  • 2.  Re: COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Broadcom Employee
    Posted Sep 20, 2017 11:15 AM

    This is much better suited for a support case, but to begin with I would suggest checking PORTs to ensure there is no communication blocking.

     

    Ports Used by CA Process Automation



  • 3.  Re: COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Posted Sep 20, 2017 11:53 AM

    Thanks Michael. let me cross check the port communication once and let you know.



  • 4.  Re: COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Posted Sep 20, 2017 11:35 AM

    Hi,

    The Agent is not shown on the agent list?

    If it isn't, maybe there was something wrong with the installation of the agent. Are both (domain orchestrator and agent) with the same version of Java?


    You could force recovery also with this steps 


    Force Recovery (re deploy)
    1. Stop PAM
    2. Backup and delete the contents of the \log directory.
    3. Delete the following directories from PAM installation\server\c2o


    audit
    data
    scripts
    tmp
    temp
    work
    wrappers

    4. Restart PAM Service



  • 5.  Re: COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Posted Sep 20, 2017 11:52 AM

    Thanks Marcel. I am able to see the installed agent information in the configuration tab of CA Process Automation Console. And I am not able to get the status of an agent via CA ITPAM (Agent Console) in the configuration tab.



  • 6.  Re: COMMAND EXECUTION ISSUE WITH RUN SCRIPT OPERATOR

    Posted Sep 20, 2017 02:43 PM

    Did you tryed the recovery steps?