Hello I have some tags that have alarms that show up when they are fired. If I fire that tag to trigger the alarm I get the alarm. However for some reason I get the alarm again 10-11 seconds later. Heres what I tried to debug this.
-
First things first I made sure this alarm was not somehow on two tags by exporting and looking through the tags, no luck.
-
I trended the tag to see if it was somehow triggering twice, it was not
-
I then backed up all tags and temporarely removed them completely from the system (To clarify I removed them from the tag browser in the designer). The 'phantom' alarm still showed! I checked the database tables related to the alarm journal and confirmed the entries were infact showing up.
-
I searched around to make sure their were not two ignition services somehow running and found nothing (Not sure what I should be looking for to confirm this however). I suspect I have not done a good job and confirming this is not the issue and would love any ideas on how to best approach proofing this.
Wondering if anyone has any ideas, I'm at the end of the road on ideas so far. My only thoughts are its either a bug in ignition alarms (which I highly believe is untrue) or some type of rogue ignition service thats running and interacting with the database somehow, any thoughts on how to confirm that?
Some info on the system, its a redundant gateway setup with the redundancy being on its own separate server. We also are using databases in a replication/fail over setup which could possibly be the culprit too but have seen no issue with replication and have debugged just shutting down both the redundant gateway and database (issue still exist).
Anyway any help would be appreciated, I feel like I'm missing something obvious 
