DX Unified Infrastructure Management

Hi,

Post Upgrade of Nimsoft from version 8.2 to version 8.47 both nas and trellis probes are not working (in the error state). Can anyone suggest how to make these probes active?

Please find a clipping of the log file :

Jan 10 10:18:48:030 [9424] nas: dbBeginTransaction dbsRun, OK - rc:0
Jan 10 10:18:48:077 [10860] nas: sockClose:000000001A7DC070:<server IP>/52087
Jan 10 10:18:48:077 [10860] nas: SREQUEST: _close -><server IP>/48002
Jan 10 10:18:48:077 [10860] nas: Subscriber terminated...
Jan 10 10:18:48:077 [8216] nas: Subscriber destroyed...
Jan 10 10:18:48:077 [8216] nas: Destroying Correlation engine...
Jan 10 10:18:48:077 [8216] nas: Correlation engine destroyed...
Jan 10 10:18:48:077 [8216] nas: Destroying the NiS bridge...
Jan 10 10:18:48:077 [8216] nas: NiS bridge destroyed...
Jan 10 10:18:48:077 [8216] nas: QosBridge - waiting for thread to complete.
Jan 10 10:18:48:077 [8216] nas: QosBridge - destroyed...
Jan 10 10:18:48:077 [8216] nas: Destroying Activity-Logger...
Jan 10 10:18:48:077 [8216] nas: Activity-Logger destroyed...
Jan 10 10:18:48:077 [8216] nas: Destroying Transaction-Logger...
Jan 10 10:18:48:077 [8216] nas: Transaction-Logger destroyed...
Jan 10 10:18:48:077 [8216] nas: Destroying Replication engine...
Jan 10 10:18:48:155 [10236] nas: The replication importer terminated...
Jan 10 10:18:48:593 [7580] nas: Replication engine terminated...
Jan 10 10:18:48:593 [8216] nas: Replication engine destroyed...
Jan 10 10:18:48:593 [8216] nas: maint Maintenance Mode Destroyed
Jan 10 10:18:48:593 [8216] nas: Destroying Event publisher...
Jan 10 10:18:48:593 [8216] nas: Event publisher destroyed...
Jan 10 10:18:48:593 [8216] nas: Destroying NameService...
Jan 10 10:18:48:921 [10924] nas: NameService terminated...
Jan 10 10:18:48:921 [8216] nas: NameService destroyed...
Jan 10 10:18:48:921 [8216] nas: Destroying Database service...
Jan 10 10:18:50:124 [9424] nas: dbCommitTransaction dbsRun, OK - rc:0
Jan 10 10:18:50:124 [9424] nas: dbsRun committed 1 requests. 0 remaining in queue...
Jan 10 10:18:50:140 [8216] nas: Database service destroyed...
Jan 10 10:18:50:140 [9424] nas: Database service terminated...
Jan 10 10:18:50:140 [8216] nas: NAS Terminated.
Jan 10 10:18:50:140 [8216] nas: SREQUEST: port_unregister -><server IP>/48000
Jan 10 10:18:50:140 [8216] nas: RREPLY: status=OK(0) <-<server IP>/48000 h=37 d=0
Jan 10 10:18:50:140 [8216] nas: sockClose:000000001A7DC070:<server IP>/54518
Jan 10 10:18:50:140 [8216] nas: SREQUEST: _close -><server IP>/48000
Jan 10 10:18:50:140 [8216] nas: nimEnd

Thanks in advance.

Hi DebapriyaC,

Some basic steps as a first try:

1. stop nas

2. stop alarm_enrichment

3. stop trellis

4. redeploy these 3 probes (right click on the probe  > Update version > reinstall same version)

5. start alarm_enrichment

6. start nas

7 start trellis

Does this fix it? if not, you may need to investigate further, just some ideas: did the upgrade complete correctly? is everything else working fine? is there any java memory related warning in the full log? what is the size of the database.db and transactionlogdb? 

Hi Marco,

Thanks for the quick response. What will the size of the database.db and transactionlogdb signify?

Thanks in advance.

the idea would be to check if the reason the probe cannot start up is because of a bad local database/transactionlog db files

The other thing to check is if the queues for nas and alarm_enrichment were created on the local hub. Also when clipping the log, can you try to get the startup and failure? The snippet you included looks to be a clean shutdown. Though it does does show clean database access during that shutdown process. Marco's suggestion of redeploying and activating in the correct order is the likely solution.

-Garin

Try nas v8.43 from the URL below.

CA Unified Infrastructure Management Hotfix Index - CA Technologies 

I just had a similar issue like this with the trellis probe after upgrade to 8.5.

Thread: https://communities.ca.com/message/241948941?commentID=241948941&et=watches.email.outcome#comment-241948941 

What I had to do once the upgrade finally worked was stop all services on Pri-Hub. Start all services then wait for everything to start up. Deactivated the broken probes so in my case: nas, trellis and prediction. Full stop, then start of Nimsoft Robot watcher service. 

Then once all other probes were up and running with PID's I select all 3 and Activated and it worked. They finally all started back up normally. 

If that doesn't work is your nas probe just RED in an error state or just not processing alarms?