UIM - data_engine probe failing with max restarts
search cancel

UIM - data_engine probe failing with max restarts

book

Article ID: 193703

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Observed  several probes showing down on Primary Hub. Tried to reactivate or validate these probes but not responding. See sample snippet below
 
 

Environment

Release : 9.0.2

Component : UIM - DATA_ENGINE

Cause

Most probes have dependency on data_engine probe to correctly start 

data_engine probe itself was failing with error in logs as below

un 18 11:17:24:219 [6520] 0 de: CA Data Engine 9.02 [Oct 15 2018]
Jun 18 11:17:24:219 [6520] 0 de: Copyright 2018, CA. All rights reserved.
Jun 18 11:17:24:219 [6520] 0 de: port=48023 PID=5264 debug=1
Jun 18 11:17:24:219 [6520] 1 de: DB Plugin: Oracle
Jun 18 11:17:24:223 [6520] 1 de: Found distsrv:xxxxx/distsrv
Jun 18 11:17:24:226 [6520] 0 de: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH
Jun 18 11:17:24:243 [6520] 0 de: License SLM-QOS:xxxx
Jun 18 11:17:24:243 [6520] 0 de: License SLM-SLA: xxxxx
Jun 18 11:17:24:243 [6520] 0 de: License SLM-GUI: xxxxx
Jun 18 11:17:24:252 [6520] 0 de: SLMFactory::NewSLM - Requesting Oracle
Jun 18 11:17:24:253 [6520] 0 de: CDLLLoader::LoadDLLbyName - Failed to load: OCI.DLL. NULL
Jun 18 11:17:25:246 [1736] Controller: Max. restarts reached for probe 'data_engine' (command = data_engine.exe)

Resolution

The UIM database was MSSQL but the data_engine probe was using oracle plugin in its config file 

There were some Windows patches applied before this issue was observed which might have caused this unexpected behavior


 server = xxxxx, 54321
  port = 1521
  servicename = orcl
  db_plugin = Oracle

Changed in data_engine config to point to correct plugin and port to match the database server which was MSSQL 


 server = xxxx,54321
 port = 
 servicename = 
 db_plugin = Microsoft

After correcting the above and restarting the data_engine probe it was processing data correctly