No incidents or alarms are generating after server migration.
search cancel

No incidents or alarms are generating after server migration.

book

Article ID: 235061

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After  Nimsoft migration from  windows server 2008 to Windows server 2019  no incidents or alarms being generating in new environment.

error in alarm enrichment:

Feb 17 03:13:40:938 [main, alarm_enrichment] (1) error, Failed to connect to database: Read timed out ClientConnectionId:1500f427-ce5f-4869-af48-fe38979999b5
 at com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource.connectToDatabase(CmdbJdbcDataSource.java:113)
 at com.nimsoft.probe.service.enrichment.cmdb.CmdbJdbcDataSource.initialize(CmdbJdbcDataSource.java:57)
 at com.nimsoft.probe.service.enrichment.cmdb.CmdbCacheEnrichmentSource.createDataSourceHandlerForConfigEntry(CmdbCacheEnrichmentSource.java:191)
 at com.nimsoft.probe.service.enrichment.cmdb.CmdbCacheEnrichmentSource.initialize(CmdbCacheEnrichmentSource.java:122)
 at com.nimsoft.probe.service.enrichment.cmdb.CmdbCacheEnrichmentSource.readCmdbSection(CmdbCacheEnrichmentSource.java:66)
 at com.nimsoft.probe.service.nas.alarmenrichment.AlarmEnrichmentService.loadEnrichmentSources(AlarmEnrichmentService.java:96)
 at com.nimsoft.probe.service.nas.alarmenrichment.AlarmEnrichmentService.<init>(AlarmEnrichmentService.java:40)
 at com.nimsoft.probe.service.nas.Nas.postLoginInitialization(Nas.java:466)
 at com.nimsoft.probe.service.nas.Nas.login(Nas.java:418)
 at com.nimsoft.nimbus.NimProbeBase.nimAttachProbe(NimProbeBase.java:303)
 at com.nimsoft.nimbus.NimProbe.initSubscribe(NimProbe.java:572)
 at com.nimsoft.nimbus.NimProbe.doForever(NimProbe.java:416)
 at com.nimsoft.probe.service.nas.Nas.run(Nas.java:611)
 at com.nimsoft.probe.service.nas.Nas.main(Nas.java:394)

 

Environment

Release : 20.3

Component : UIM OPERATOR CONSOLE - ALARM VIEWER

Cause

Old entry of database server in nas.config causing issues with database access

Resolution

Changed  database server entry in nas.config  to new server resolved the issues with alarming