We created a custom rule and can see by the Rule run condition query box and by the Rule Diagnostics the rule evaluated to true and the actions should fire. The logs do not show any issues with the rules themselves and all rules have stopped emailing at this point.
There was a faulty command action script that was using all the action threads in the FMS server and all other actions that were true could not be performed.
The FMS has a pool of 20 threads that it can use to execute actions and according to the thread dump in the diagnostic snapshot all the threads appear to be waiting for the command action script to complete.
We could see this in the FMS log to help identify the script in question
YYYY-MM-DD HH:MM:SS.SSS VERBOSE [Thread-265] com.quest.foglight.integration.util.StreamGobbler - Command Action Out: /foglight/scripts/testscript "" "host" "Agent Health State" "AIX_Console_AIX_Console@host" "YYYY-MM-DD HH:MM:SS.SSS" "alert message occured on host
RESOLUTIOIN
The FMS has to be recycled to clear the action threads and the faulty script will have to be edited to be correct or removed from the FMS
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center