Related to:

The error RuleManager Rule <rule> references non-existent action <action> in the Secondary Gateway log indicates that a rule references an action that cannot be found. This typically occurs due to one of three main causes: the action depends on a script that exists only on the Primary Gateway and has not been replicated to the Secondary Gateway; the action definition is missing; or the script path is invalid or inaccessible on the secondary server. As a result, the Secondary removes the action reference, and the rule will not execute correctly.

Problem:

In a Hot-Standby Geneos setup (Primary and Secondary Gateway), the Secondary Gateway log shows the following error:

ERROR: RuleManager Rule <rule> references non-existent action <action> 
(check for previous action error?), removing the action reference from the rule.

Possible cause(s):

• Root Cause 1: The script file required by the action exists only on the Primary Gateway Server.
• Root Cause 2: The action definition is missing or incorrectly configured in the Secondary Gateway setup file.
• Root Cause 3: The script path configured in the action is invalid or inaccessible on the Secondary server.

Possible solution(s):

• Solution Root Cause 1: Ensure that all script files used by actions are replicated to the Secondary Gateway server.

• Solution Root Cause 2: Synchronize the Gateway setup configuration.

  2.1 Compare gateway.setup.xml files.

  2.2 Ensure the <action> block exists and matches exactly.

  2.3 Restart the Secondary Gateway after correction.

• Solution Root Cause 3: Correct the script path in the action configuration

  3.1 Update the <command> path to match the Secondary environment.

  3.2 Ensure execution permissions:

  chmod +x <script>.sh

  3.3 Restart the Secondary Gateway and confirm the log no longer reports the error.

Note: When the script is present on both the primary and secondary gateway and the script needs to be changed, the File Syncronisation feature can be utilized so that no mismatch will occur.

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.