Highlighted
Honored Contributor.
Honored Contributor.
666 views

Probe cannot connect to server

Jump to solution

can anybody help to troubleshoot.

we installed 10.11 with latest CUP and CP. Then we installed probe 10.10 ( we planned to upgrade the probe later manually using the probe update function). The probe doesn't appear in the uCMB. The logfile from the probe shows the following:

 

==========

wrapper  |     http://wrapper.tanukisoftware.org
wrapper  |   Licensed to Hewlett-Packard Company for UCMDB Data Flow Probe
wrapper  |
wrapperp | port 1777 already in use, using port 32000 instead.
wrapper  | Launching a JVM...
jvm 1    | -XX:+CMSClassUnloadingEnabled -XX:+CMSIncrementalMode -XX:CompileCommand=exclude,jregex/Pretokenizer,next -XX:+HeapDumpOnOutOfMemoryError -XX:InitialHeapSize=1073741824 -XX:+ManagementServer -XX:MaxGCPauseMillis=250 -XX:MaxHeapSize=2147483648 -XX:MaxPermSize=201326592 -XX:MaxTenuringThreshold=6 -XX:NewRatio=2 -XX:OldPLABSize=16 -XX:PermSize=134217728 -XX:+PrintCommandLineFlags -XX:+UseAdaptiveGCBoundary -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:-UseLargePagesIndividualAllocation -XX:+UseParNewGC
jvm 1    | CompilerOracle: exclude jregex/Pretokenizer.next
jvm 1    | WrapperManager: Initializing...
jvm 1    | Starting the Probe ...
jvm 1    | log4j:WARN No appenders could be found for logger (com.hp.ucmdb.discovery.library.common.CollectorsParameters).
jvm 1    | log4j:WARN Please initialize the log4j system properly.
jvm 1    | Default OEM Encoding: cp850, Default ANSI Encoding: Cp1252
jvm 1    | Probe version [UCMDB.PROBE.10.10.Build_620]
jvm 1    | <2014-12-16 16:39:09,163> 359  [INFO ] [WrapperSimpleAppMain] (ProbeGwDBServicesFactory.java:32) - starting the DBServices for the ProbeGwDBServicesFactory...
jvm 1    | <2014-12-16 16:39:09,726> 922  [INFO ] [WrapperSimpleAppMain] (DBServicesImpl.java:104) - Connected to DB: Custom URI: jdbc:postgresql://localhost/dataflowprobe with userName mamprobe
jvm 1    | <2014-12-16 16:39:09,741> 937  [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=DbService
jvm 1    | SLF4J: Class path contains multiple SLF4J bindings.
jvm 1    | SLF4J: Found binding in [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/slf4j-jdk14.jar!/org/slf4j/impl/StaticLoggerBinder.class]
jvm 1    | SLF4J: Found binding in [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
jvm 1    | SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.Server doStart
jvm 1    | INFO: jetty-7.6.0.RC4
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.s.ServletContextHandler{/,null}
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.AbstractConnector doStart
jvm 1    | INFO: Started SelectChannelConnector@0.0.0.0:80 STARTING
jvm 1    | <2014-12-16 16:39:10,116> 1312 [INFO ] [WrapperSimpleAppMain] (GtwJettyWrapper.java:56) - Start listening on port 80 for callhome.
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.Server doStart
jvm 1    | INFO: jetty-7.6.0.RC4
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/cm,file:/C:/hp/UCMDB/DataFlowProbe/deploy/cm/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\cm
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/incoming,file:/C:/hp/UCMDB/DataFlowProbe/deploy/incoming/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\incoming
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/jmx-console,file:/C:/hp/UCMDB/DataFlowProbe/deploy/jmx-console/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\jmx-console
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/original,file:/C:/hp/UCMDB/DataFlowProbe/deploy/original/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\original
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/rum,file:/C:/hp/UCMDB/DataFlowProbe/deploy/rum/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\rum
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/shortstatus,file:/C:/hp/UCMDB/DataFlowProbe/deploy/shortstatus/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy\shortstatus
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.handler.ContextHandler startContext
jvm 1    | INFO: started o.e.j.w.WebAppContext{/,file:/C:/hp/UCMDB/DataFlowProbe/deploy/},C:\hp\UCMDB\DataFlowProbe\bin\..\deploy
jvm 1    | Dez 16, 2014 4:39:10 PM org.eclipse.jetty.server.AbstractConnector doStart
jvm 1    | INFO: Started SelectChannelConnector@0.0.0.0:1977 STARTING
jvm 1    | <2014-12-16 16:39:10,773> 1969 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=Scheduler
jvm 1    | <2014-12-16 16:39:10,773> 1969 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:300) - Added the internal scheduler: Probe_H1047:type=Scheduler
jvm 1    | <2014-12-16 16:39:10,866> 2062 [INFO ] [WrapperSimpleAppMain] (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from URL [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/discovery-probe.jar!/pojo/probegw/probe-gateway-pojos.xml]
jvm 1    | <2014-12-16 16:39:11,195> 2391 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=MainProbe
jvm 1    | <2014-12-16 16:39:11,210> 2406 [INFO ] [WrapperSimpleAppMain] (DiscoveryClient.java:233) - Registering on URL: HTTP://H1046:8080/mam-collectors for customer: 1
jvm 1    | <2014-12-16 16:39:11,210> 2406 [INFO ] [WrapperSimpleAppMain] (UpgradePackageHandler.java:44) - Probe identified os:windows
jvm 1    | <2014-12-16 16:39:11,226> 2422 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=GwDownloader
jvm 1    | <2014-12-16 16:39:11,226> 2422 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=GwAgentsConnection
jvm 1    | <2014-12-16 16:39:11,226> 2422 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=GwTaskResultDistributer
jvm 1    | <2014-12-16 16:39:11,226> 2422 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=TouchResultSender
jvm 1    | <2014-12-16 16:39:11,241> 2437 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=GwTaskDistributer
jvm 1    | <2014-12-16 16:39:11,241> 2437 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=AdapterRequestDispatcher
jvm 1    | <2014-12-16 16:39:11,241> 2437 [INFO ] [WrapperSimpleAppMain] (BaseAgent.java:177) - Added service: Probe_H1047:type=GeneralUtils
jvm 1    | <2014-12-16 16:39:11,241> 2437 [INFO ] [WrapperSimpleAppMain] (ProbeTouchResultsSender.java:46) - Starting ProbeTouchResultsSender
jvm 1    | <2014-12-16 16:39:11,241> 2437 [INFO ] [WrapperSimpleAppMain] (ProbeTouchResultsSender.java:50) - ProbeTouchResultsSender started
jvm 1    | <2014-12-16 16:39:11,304> 2500 [INFO ] [WrapperSimpleAppMain] (ProbeDownLoader.java:66) - The Probe DownLoader has started successfully
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [WrapperSimpleAppMain] (ProbeMgrDBServicesFactory.java:36) - starting the DBServices for the ProbeMgrDBServicesFactory...
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [WrapperSimpleAppMain] (ProbeMgrDBServicesFactory.java:51) - Created DBContext for ProbeMgrDBServicesFactory: Custom URI: jdbc:postgresql://localhost/dataflowprobe with userName mamprobe
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [WrapperSimpleAppMain] (DBServicesImpl.java:104) - Connected to DB: Custom URI: jdbc:postgresql://localhost/dataflowprobe with userName mamprobe
jvm 1    | <2014-12-16 16:39:11,351> 2547 [ERROR] [ProbeGW Task Results Sender] (TaskResultsSenderThread.java:285) - Failed sending results to the server, will retry later
jvm 1    | java.lang.Exception: Server returned invalid response: <html>
jvm 1    |  at com.hp.ucmdb.discovery.library.communication.client.DiscoveryClient.sendResultsToServer(DiscoveryClient.java:677)
jvm 1    |  at com.hp.ucmdb.discovery.library.results.sending.TaskResultsSenderThread.sendToServer(TaskResultsSenderThread.java:613)
jvm 1    |  at com.hp.ucmdb.discovery.library.results.sending.TaskResultsSenderThread.processTaskResults(TaskResultsSenderThread.java:211)
jvm 1    |  at com.hp.ucmdb.discovery.library.results.sending.TaskResultsSenderThread.run(TaskResultsSenderThread.java:156)
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [ProbeGW Task Results Sender] (TaskResultsSenderThread.java:157) - Finished sending results to server. time: 63
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [ProbeGW Task Results Sender] (TaskResultsSenderThread.java:162) - Process Result Time Statistics - Total Time:63, Results size:5, Time To get Tasks:0,
jvm 1    | <2014-12-16 16:39:11,351> 2547 [INFO ] [WrapperSimpleAppMain] (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from URL [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/discovery-probe.jar!/pojo/probemgr/probe-manager-pojos.xml]
jvm 1    | <2014-12-16 16:39:11,476> 2672 [INFO ] [WrapperSimpleAppMain] (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from URL [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/discovery-probe.jar!/pojo/probemgr/probe-manager-netlinks-pojos.xml]
jvm 1    | <2014-12-16 16:39:11,523> 2719 [INFO ] [WrapperSimpleAppMain] (XmlBeanDefinitionReader.java:315) - Loading XML bean definitions from URL [jar:file:/C:/hp/UCMDB/DataFlowProbe/lib/discov

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.
Honored Contributor.

Re: Probe cannot connect to server

Jump to solution

Hi, thanks for investigating here. This issue could be solved, we had an old setting for the communication server probe in the database, mam-collectors were mapped to "http, https_client_auth". We assumed that if it is configured like this, both methods are valid. This was wrong, we set it to https and probes connected to the server.



Probes show up in the ucmdb now, unfortunately with the wrong version or the "Deploy Update" did not work. We opened a supportcase for this and post the solution here.

View solution in original post

0 Likes
2 Replies
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Probe cannot connect to server

Jump to solution

Hello ,

 

Thanks for the details .

 

I will proceed to review this information and investigate .

 

As soon as I have an update I will contact you .

 

Best regards ,

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: Probe cannot connect to server

Jump to solution

Hi, thanks for investigating here. This issue could be solved, we had an old setting for the communication server probe in the database, mam-collectors were mapped to "http, https_client_auth". We assumed that if it is configured like this, both methods are valid. This was wrong, we set it to https and probes connected to the server.



Probes show up in the ucmdb now, unfortunately with the wrong version or the "Deploy Update" did not work. We opened a supportcase for this and post the solution here.

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.