POST_QUEUE_COMM_ERROR captured on the secondary nas log with Tunnel enabled
Article ID: 433693
Updated On:
Products
DX Unified Infrastructure Management (Nimsoft / UIM)
Issue/Introduction
Secondary nas instances installed on Hubs with Tunnel enabled capture the following entries in the nas log file even though all alarms are synced properly.
nas log entries with debug set to 2 in the nas.cfg
nas: replExporter: POST_QUEUE_COMM_ERROR destination: <primary_hub_name> dest_addr: /<domain>/<primary_hub_name>/primary_hubrobotname>/nas sendTime: 0 ms timeout:30s
nas: replExporter: POST_RECONNECTED address: '/<domain>/<primary_hub_name>/primary_hubrobotname>/nas'
nas: replExporter: POST_QUEUE_SEND_DONE destination: <primary_hub_name>' count: # sendTime: 561ms rc:
Resolution
This is a benign error message, provided that alarms are properly synced and a 'POST_QUEUE_SEND_DONE' is captured after a 'POST_QUEUE_COMM_ERROR'.
Feedback
Yes
No
Powered by
