I noticed recently that a number of alarms have a time of arrival between 3 to 6 minutes before they actually arrive in the alarm console.
When looking in the nas log I see hundreds of events saying the following:
nas: Constraint violation on insert, generating new nimid.
and then I get a message of:
nas: Database operation retries...100
I am then seeing the nas rules been running and then a message of:
nas: Event-Processor: published 2 messages in 6ms, 0 in queue.
nas: NiS bridge: NTS UPDATED: nimid='YC27333054-07559' rc: 0 took 2ms
nas: NiS bridge: NA UPDATED: nimid='YC27333054-07559' rc: 0 took 1ms
nas: NiS bridge: NTS UPDATED: nimid='ZG48895979-94826' rc: 0 took 1ms
NiS bridge: NA UPDATED: nimid='ZG48895979-94826' rc: 0 took 1ms
nas: Subscriber processed 2 msg.,0 updates the last 10s, 0.20 msg/s, queued:1
nas: Subscriber processed 2 msg.,0 updates the last 10s, 0.20 msg/s, queued:1
nas: dbsRun committed 1 requests. 0 remaining in queue...
and then the constraint alarms come back in
I have checked availability of the DB and that is connecting in the data_engine probe, Looking in the data_engine I can see under statistics the amount of msg/min listed
I do not see any obvious alarms in the data_engine logs (nimid's are listed in the logs).
Release : UIM 20.x
Component : UIM NAS
Nas probe version: 9.06
Upgrading Nas probe from 9.06 to 9.32 solves this issue.
The hotfix can be downloaded here: nas_9.32_HF1.zip