@tursiops said in alarm_events table still holds an alert of removed node:
Can you confirm that DeleteEventsOfDeletedObject is set to 1?
Have you tried shutting NetXMS down and running "nxdbmgr check" on your server?
Just in case your problem is related to inconsistencies in your database.
I can confirm that DeleteEventsOfDeletedObject is set to 1.
I stopped the service and ran nxdbmgr check and got the following output.
NetXMS Database Manager Version 2.2.15 Build 9523 (2.2.15.2) (UNICODE)
Checking database (excluding collected data):
* Zone object properties [PASSED]
* Node object properties [PASSED]
* Node to subnet bindings [PASSED]
* Interface object properties [PASSED]
* Interface bindings [PASSED]
* Network service object properties [PASSED]
* Network service bindings [PASSED]
* Cluster object properties [PASSED]
* Cluster member nodes [PASSED]
* Template to node mapping [PASSED]
* Object properties [PASSED]
* Container membership [ 94% ]
Container 2446 contains non-existing child 2455. Fix it? (Yes/No/All/Skip) A
* Container membership [FIXED ]
* Event processing policy [PASSED]
* Network map links [PASSED]
* Data tables [PASSED]
* Raw DCI values table [ 24% ]
Found raw value record for non-existing DCI [3458]. Delete it? (Yes/No/All/Skip) A
* Raw DCI values table [ 61% ]
Found raw value record for non-existing DCI [5684]. Delete it? (Yes/No/All/Skip) Y
* Raw DCI values table [FIXED ]
* DCI thresholds [ 46% ]
Found threshold configuration for non-existing DCI [3458]. Delete? (Yes/No/All/Skip) A
* DCI thresholds [FIXED ]
* Table DCI thresholds [PASSED]
4 errors was found, 4 errors was corrected
All errors in database was fixed
Commit changes? (Yes/No) Y
Committing changes...
Changes was successfully committed to database
Database check completed
C:\NetXMS\bin>
I ran the check again and it found no issues. I then restarted the service, but still got the alert emails. However, they all are just telling me these nodes are up, and just a few specific ones, not all of them.
I can understand if there was an active alarm, like a node down, and I did get one like that - but my node is actually down. The others are all up with no issues, and it just decides it has to tell me that for these 5 nodes every time I restart the service.
Any help is appreciated!