UCMDB and UD Practitioners Forum (Previously CMS)
cancel
Showing results for 
Search instead for 
Did you mean: 

Data Flow probe not displayed in UCMDB 9.05

Highlighted
Mathew_ucmdb
Collector

Data Flow probe not displayed in UCMDB 9.05

 

Hi Team,

 

We have our production environment version 9.05. We tried to upgrade to 10.*, we got some upgrade issues and hence planned to roll back to 9.05.

 

We re-installed the UCMDB Server and Data Flow Probes..but we are not seeing Probes under Data Flow Probe setup. This is our production env and now everything is at stand still..

 

2 probes and 1 server:

We have re-installed 9.05 CUP 8 on the UCMDB server.

Reinstalled Data flow probe 9.05 ver 314 (on 1 probe)

Did not install data flow probe on the 2nd probe.

 

We have all our old folders in place. Is it possible for us to replace the old backup folders of UCMDB and Data flow probe and will it work then?

 

Anyone experience this issue before? Please help.

 

Thank You.

 

Mathew

14 REPLIES
ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

Can you please provide probe-error and probe-infra log

Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi,

 

We restored the DB schemas and it's working fine now.

 

However, The Discovery jobs are failing, integration jobs failing.

 

We tried de-activating it and re-activating the jobs but it did not help. I guess we need to wait till the schedule time..plz correct me if I am wrong.

 

Regards

Mathew

Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi Team,

 

What happens if I clear the probe results cache and re-run the discover job:

Ex: Host connection by shell..

 

Any one has tried this? please advice.

 

Regards

Mathew

ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

we can't help you without knowing what the error is
ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

To prevent probe from sending the same data twice, the probe kept a cache it discovery result. By clearing the probe cache, all discovery result will be sent to ucmdb server.
Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi,

 

We had deactivated all Jobs, cleared the Data flow Probe cache and activate the jobs today.

 

We still get errors, not sure if it is taking time to connect to the IP's.

 

Please find the error from the communication log. I have generated this for connection by Shell. (have edited the IP's and names for security reasons)

 

<execution jobId="DB Connections by Shell" destinationid="herthethrthrth">
 <destination>
  <destinationData name="id">herthethrthrth</destinationData>
  <destinationData name="ip_address">57357</destinationData>
  <destinationData name="ip_domain">75353</destinationData>
  <destinationData name="hostId">jghjhj</destinationData>
  <destinationData name="language">eng</destinationData>
  <destinationData name="credentialsId">2_1_CMS</destinationData>
  <destinationData name="Protocol">ntcmd</destinationData>
  <destinationData name="codepage">Cp1252</destinationData>
 </destination>
 <params>
  <param param_name="filterByDiscoveredProcesses" param_value="false" />
  <param param_name="use_sudo" param_value="false" />
  <param param_name="discover_oracle" param_value="true" />
  <param param_name="use_lsof" param_value="true" />
  <param param_name="discover_db2" param_value="true" />
  <param param_name="discover_mssql" param_value="true" />
  <param param_name="JOB_ID" param_value="DB Connections by Shell" />
 </params>
 <log start="2:24:40" severity="debug">NTCMD: Operation failed.</log>
 <log start="2:24:40" severity="debug">Reporting error code 208 to framework.</log>
 <log start="2:24:40" severity="debug">Error message is: NTCMD: Operation failed.</log>
 <results>
  <results_for_add_or_update>
   <vector />
  </results_for_add_or_update>
  <results_for_delete>
   <vector />
  </results_for_delete>
 </results>

 

 

Thank You.

 

Regards

Mathew

ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

Error message is: NTCMD: Operation failed

Look like your shell is using NTCMD protocol to connect, not SSH. 

CHeck out this link to learn more about ntcmd

http://support.openview.hp.com/selfsolve/document/KM205040

 

IF you just want to use SSH, Edit your adapter and under "Required Discovery Protocol" remove telnet and NTCMD.

Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi Experts,

 

We have followed the instructions and it did not help us muchj. On the probe logs we find the following error:

 

Failed to get credential for id 127_1_CMS - Could not fetch credential with id 127_1_CMS from Confidential Manager Client

 

HP gave us a PDF for this particular error but we didnt have to use it as we were finding the vector IP, etc in the file.

 

Any thoughts on this please.

 

Regards

Mathew

Dima Gomel
HPE Expert

Re: Data Flow probe not displayed in UCMDB 9.05

It's hard to say what the problem is without logs and detailed info.

Would you mind raising the case fo rthe quick resolution please?

Regards
-Dmitry Gomel, PMP
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the Like button at the bottom to say 'Thanks'.
Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi Dima,

 

Sorry for not being clear. I have attached the probe logs and will upload the server logs soon.

 

2 Probes: 9.05 CUP 8 build 250

1 UCMDB server: 9.05 CUP 8 11.4

 

Yes, raised a ticket a week back and HP is working on the same.

 

The issues is that Dsicovery jobs like TCP data by shell, TCP data by SNMP, Host connection by Shell and SNMP and other related jobs are not running.

 

Probes errors:

 

<2013-08-06 09:45:29,486> [ERROR] [JobExecuterWorker-23:Host Connection by Shell_10.140.221.109] (ConfidentialManagerClientWrapper.java:78) - Failed to get credential for id 228_1_CMS - Could not fetch credential with id 228_1_CMS from Confidential Manager Client

 

Tried couple of thins from HP:

============================================================================

 Please follow the Data Flow Credentials Management documentation in HP UCMDB Deployment Guide, which explains how to synchronized LWSSO
configuration manually.

In particular, you should grab lwsso init string from UCMDB's JMX console:
Go to LW-SSO Configuration service in UCMDB's JMX console and click on "retrieveConfiguration" method. Copy the value of LW-SSO init string key
Go to probe's JMX console and choose CMClient service Locate the "setLWSSOInitString" method and provide the same init string that you've copied from UCMDB Click the "setLWSSOInitString" button.
If the above still doesn't help, please reproduce your issue and send again the log files from both probe and UCMDB server.

 

Do you have the situation like this, you have two probes in the same domain,and one probe is working fine, another cannot work.
If you have this situation, please try to back up the cm folder in your problematic probe. The cm folder location is: X:\hp\UCMDB\DataFlowProbe\deploy
Copy the cm folder from the working probe, and then restart your problematic probe and try it again.

5) If you don't have this situation of 4 or it still can not work, please do the things as below: login your problematic probe, and find the files probeMgrLog4j.properties

Edit it as:
log4j.logger.com.hp.sw.bto.ast.security.cm=DEBUG, CM_CLIENT
#donot forward log messages to console:
log4j.additivity.com.hp.sw.bto.ast.security.cm=falselog4j.logger.org.apache.wink=DEBUG, CM_CLIENT

log4j.logger.com.hp.sw.bto.ast.security.lwsso=DEBUG, LWSSO_CLIENT
-----------------------------------------------
Open DiscoveryProbe.properties file, Modity the attribute: com.hp.ucmdb.discovery.common.security.storeCMData=false
-----------------------------------------------
Login your ucmb server and go to Infrastructure Settings Manager.
Find “Enable automatic synchronization of CM/LW-SSO configuration and init string with probe” keep it is true.

 

=================================================================================

 

 

Please let me know if any more information is required.

 

 

Any help is appreciated.

 

Thank You.

 

Regards

Mathew

Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Attaching the logs

ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

<2013-08-05 09:40:28,092> [ERROR] [Thread-34] (ProbeTaskResultsSender.java:204) - Failed sending ad hoc results to the server
java.lang.Exception: Server returned invalid response: NOT_OK - Unknown Task

 

Seem to me like probe and server having some type of communication problem.

 

Can you go to Modelling > Data Flow Probe Setup and make sure all probe status are connected?

 

 

 

Mathew_ucmdb
Collector

Re: Data Flow probe not displayed in UCMDB 9.05

Hi,

 

The probe status shows connected.

ctruong
Member

Re: Data Flow probe not displayed in UCMDB 9.05

Let do this can you stop the probe. Delete all the log. Then start the probe and when it status is connect run a job.

 

Then send  me the following log.

 

WrapperProbeGw, probe-infra, and error.log

 

Thank

//Add this to "OnDomLoad" event