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.
<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
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.
<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?