Unable to connect to local ProactiveNet Agent.

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    ProactiveNet Performance Management Suite


    APPLIES TO:

    BMC ProactiveNet Performance Management Suite



    PROBLEM:

     

    Unable to connect to local ProactiveNet Agent. The ProactiveNetAgent.log shows :

      

    INFO 09/04 19:43:09 Agent [SessionHandler(DspMsg-AgentCntl] 102451 Agent 10494 initialization completed.
    INFO 09/04 19:50:07 Agent [AC_Listener] 102456 Agent received a connection request from /172.28.8.125
    WARN 09/04 19:50:07 Agent [AC_Listener] 102736 Agent denied the connection attempt from /172.28.8.125 as it is already connected to another server ( /172.28.8.125).

     


    SOLUTION:

     

    Legacy ID:KA354252

      

    The first line shows that the agent id is 10494 but for a local agent this should be 10001. This indicates that another agent has 'stolen' the local agent's connection the the agent controller.

    In the Admin console, see if there is an agent that has IP address 0.0.0.0 as this would be the cause of the problem. The fact that it has IP address of 0.0.0.0 indicates that there has been a name resolution problem. Edit the IP address of the device which will also change the IP address of the agent. Then restart the agent controller and the local agent.

      
    Related Products:  
       
    1. BMC ProactiveNet Performance Management Suite

     


    Article Number:

    000056902


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles