search cancel

sdgtw - checkConnection: Got NimException connecting to queue alarm_assign, alarm_update, alarm_close: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null' 

book

Article ID: 202322

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We can do a validation test and they can see the probe reaching them, validating the connection, then canceling the transaction.  I've activated the probe, and the profile.  But they're not getting any connections now.  In the log it keeps showing the following over and over again.

Oct 22 12:06:19:608 [Thread-189, sdgtw] subscribe to queue hub address is /NimZBCtest/NIMT01A/nimt01a/hub 
Oct 22 12:06:19:608 [Thread-189, sdgtw]  inside subscribe to queue hub address is /NimZBCtest/NIMT01A/nimt01a 
Oct 22 12:06:20:613 [Thread-189, sdgtw] checkConnection: Got NimException connecting to queue alarm_assign, alarm_update, alarm_close: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null' 
Oct 22 12:06:30:615 [Thread-189, sdgtw] subscribe to queue hub address is /NimZBCtest/NIMT01A/nimt01a/hub 
Oct 22 12:06:30:615 [Thread-189, sdgtw]  inside subscribe to queue hub address is /NimZBCtest/NIMT01A/nimt01a 
Oct 22 12:06:31:618 [Thread-189, sdgtw] checkConnection: Got NimException connecting to queue alarm_assign, alarm_update, alarm_close: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null' 

It looks like it's not connecting to the alarm queues in order to process the alarms.  I don't see why it can't find these queues though.

Environment

Release : 9.1.0

Component : UIM - SDGTW

Resolution

The problem is in the sdgtw.cfg file.   

Instead of providing a queue name for the alarms to be processed by the sdgtw probe, you listed the alarm subjects:

queue_name = alarm_assign, alarm_update, alarm_close

By default the probe uses tickets for the queue name.  They need to either continue using tickets for the queue name, or manually create a queue from the hub Configure GUI which subscribes to the 3 alarm subjects they are currently using for the queue_name, then use the name of the new queue in the sdgtw.cfg file. 

The error message recorded in the sdgtw.log is telling you that the probe is failing to connect to any of the 3 queue names that they configured in the sdgtw.cfg file for the queue_name:

 

Got NimException connecting to queue alarm_assign, alarm_update, alarm_close: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'subscribe' name = 'null'

 

Step #3 in the "(Optional) Configure General Properties" section of the sdgtw AC Configuration document provides instructions for configuring the queue name.