ems probe is not processing via the ems_uim_db_sync queue
search cancel

ems probe is not processing via the ems_uim_db_sync queue

book

Article ID: 277073

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are not seeing alarms from spectrumgtw in Operator Console.

The following is showing in the ems.log:

[attach_socket, ems] Exception when sending message from 'AlarmManager', reached maximum retries of 10
[attach_socket, ems] Exception when sending message from 'AlarmManager' to 'null,ems_uim_db_sync'
[attach_socket, ems] Exception when sending message from 'AlarmManager', reached maximum retries of 10
[attach_socket, ems] Exception when sending message from 'AlarmManager' to 'null,alarm_new'
[attach_socket, ems] Exception when sending message from 'AlarmManager', reached maximum retries of 10
[attach_socket, ems] Exception when sending message from 'AlarmManager' to 'null,ems_action'

Environment

  • Version: 20.4
  • Component: ems

Cause

  • Bad network alias

Resolution

One of the addresses that was listed in hub -> Name Services -> Network Aliases was set for the Primary hub which was pointing to itself. After removing that entry, the ems probe started processing data through the ems_uim_db_sync queue, and Spectrum alarms were then showing up in the Operator Console.