2 Replies Latest reply on Dec 17, 2018 1:23 AM by Abhay Bhagat

    ITDA KM : Error while connecting to ITDA collection station

    Abhay Bhagat
      Share This:

      Dear Experts ,

       

      I am getting the below error  and agent (ITDA KM )is not getting connected to ITDA

       

      oracle@abhay-testdb2:/opt/bmc/Patrol3/bww/udc/logs$ more collection.log

      Nov 01, 2018 09:52:00 AM com.bmc.ola.bwagent.controller.AgentController main():43

      INFO: AgentController.main()

      Nov 01, 2018 09:52:00 AM com.bmc.ola.bwagent.controller.AgentController main():50

      INFO: starting collector:

      Nov 01, 2018 09:52:07 AM com.bmc.ola.utils.filewatch.FileWatcher$FACTORY getFileWatcher():69

      INFO: Using polling based file watcher

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():60

      INFO: Configuration Keyword provided

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():66

      INFO: 4 Configuration Parameter(s) specified

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():73

      INFO: Configuration Parameter is: agent.name=abhay-testdb2_abhay-testdb2_3181

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():80

      INFO: Key: agent.name, Value: abhay-testdb2_abhay-testdb2_3181

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():91

      INFO: 1 Configuration Parameter(s) already read

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():73

      INFO: Configuration Parameter is: host.name=abhay-testdb2.abhaytest.local

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():80

      INFO: Key: host.name, Value: abhay-testdb2.abhaytest.local

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():91

      INFO: 2 Configuration Parameter(s) already read

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():73

      INFO: Configuration Parameter is: station.discovery.identifier=http;172.21.38.182;8080

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():80

      INFO: Key: station.discovery.identifier, Value: http;172.21.38.182;8080

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():91

      INFO: 3 Configuration Parameter(s) already read

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():73

      INFO: Configuration Parameter is: stationprotocol=HTTP

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():80

      INFO: Key: stationprotocol, Value: HTTP

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():91

      INFO: 4 Configuration Parameter(s) already read

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():93

      INFO: 4 Configuration Parameter(s) left to read

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMConfigReader <init>():113

      INFO: Checking protocol in Station discovery http;172.21.38.182;8080

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMShutdownService register():75

      INFO: Registering the KM Shutdown Service

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMHeartBeatService init():71

      INFO: Started listening Hearbeat Services

      Nov 01, 2018 09:52:11 AM com.bmc.ola.bwagent.configreader.KMHeartBeatService register():94

      INFO: Registering the KM Heartbeat Service

      Nov 01, 2018 09:52:12 AM com.bmc.ola.bwagent.schedule.SchedulerThreadPoolController getScheduler():89

      INFO: Scheduler: name=_KMCONFIGURATION poolsize=2 created

      Nov 01, 2018 09:52:12 AM com.bmc.ola.bwagent.agentmodules.UpdateConfigAtStartupModule bootstrap():33

      INFO: Not required to check for updating properties file because the Agent Role is : COLLECTION_KM.

      Nov 01, 2018 09:52:12 AM com.bmc.ola.bwagent.agentmodules.ConfigProviderModule <init>():54

      INFO: Constructor of Configprovider

      Nov 01, 2018 09:52:19 AM com.bmc.ola.bwagent.utils.Utils waitForRandomTime():127

      INFO: Droid to try Station Registration after 15995 milliseconds

      Nov 01, 2018 09:52:50 AM com.bmc.ola.bwagent.registerudc.UdcPoolDiscovery processResult():390

      INFO: PoolName ITDAPool and station identifiers abhay-appmon-3.test.demo;8080;41414 retrieved from json client respo

      nse

      Nov 01, 2018 09:52:51 AM com.bmc.ola.bwagent.agentmodules.ConfigProviderModule bootstrap():105

      INFO: Registering agent , Name:abhay-testdb2_abhay-testdb2_3181, Role:COLLECTION_KM

      Nov 01, 2018 09:52:51 AM com.bmc.ola.bwagent.utils.Utils waitForRandomTime():127

      INFO: Droid to try Station Registration after 12318 milliseconds

      Nov 01, 2018 09:53:03 AM com.bmc.ola.bwagent.registerudc.UdcDroidRegister buildResult():357

      ERROR: Station Registration Failed

      com.bmc.ola.agent.service.util.UdcException: No valid response returned

              at com.bmc.ola.bwagent.registerudc.UdcDroidRegister.buildResult(UdcDroidRegister.java:348)

              at com.bmc.ola.bwagent.registerudc.RegisterBuilderFactory.executetask(RegisterBuilderFactory.java:127)

              at com.bmc.ola.bwagent.agentmodules.ConfigProviderModule.executeTask(ConfigProviderModule.java:126)

              at com.bmc.ola.bwagent.agentmodules.ConfigProviderModule.bootstrap(ConfigProviderModule.java:107)

              at com.bmc.ola.bwagent.controller.AgentModulesController.start(AgentModulesController.java:201)

              at com.bmc.ola.bwagent.controller.AgentController.main(AgentController.java:51)

      Caused by: com.bmc.ola.agent.service.util.UdcException: No valid response returned

              at com.bmc.ola.bwagent.registerudc.UdcDroidRegister.processResult(UdcDroidRegister.java:388)

              at com.bmc.ola.bwagent.registerudc.UdcDroidRegister.buildResult(UdcDroidRegister.java:340)

              ... 5 common frames omitted

       

      Please suggest if you have any suggestion or resolution for the same

       

      Regards

      Abhay

        • 1. Re: ITDA KM : Error while connecting to ITDA collection station
          Betty Neumann

          Hi Abhay,

           

          I did see a Support ticket for this issue, where it looks like it was resolved. The possible cause for this issue was a resolution issue:

          Please try to telnet the machines using the hostname.
          From the logs we see the following line
          INFO: PoolName ITDAPool and station identifiers efts-appmon-3.benefit.demo;8080;41414 retrieved from json client response
          Please check if the IP and the corresponding hostname entries are present and proper on both machines


          Check if the PATROL Agent machine and KM machine are pingable from each other.
          Please use both the hostname and the IP address while testing the ping scenario.
          We might need to modify the hosts file depending on the test.

           

          Please do let us know if this is still an issue, if so, please open a Support ticket for further assistance.

           

          • 2. Re: ITDA KM : Error while connecting to ITDA collection station
            Abhay Bhagat

            Issue got fixed by updating the host file of the source server