Pandora FMS Community

Pandora OPEN agent alert inhibited

Davide · 22 sept 2026, 13:42 · 10 mensajes · 208 visitas

  1. Inicio del debate

    Good afternoon,

    I tried replying to my previous thread but it's not working. We found something in the logs, I'll leave the image attached. This occurs with all agents, they are not on downtime/disabled/quiet etc, new agents don't work as well

  2. Hello @bonameenee ,

    Did you created the alerts from scratch within Pandora Open?

    Or those alerts were migrated from v757 to Pandora Open without any intervention?

    This info can help us determine the troubleshoot steps moving forward.

    Kind regards,

    Sergio B.

  3. Hi Sergio, alerts are created from scratch but following the standard we had in v757. We have them also in v777 with no issues. It seems that they are not triggered even if they are in crit status

  4. One thing worth mention, there is a bug in Pandora Open where the cascade protection inhibits alerts from triggering.

    You can execute this 2 queries in the DB Interface to probably fix the issue in the first place:

    UPDATE tagente SET cps = -1;
    
    UPDATE tagente_modulo SET cps = -1;
    

    Let us know if everything works once this queries are executed.

    Kind regards,
    Sergio B.

  5. Hi Sergio,

    we executed the queries but still the alerts are not firing in critical status

    pic attached

  6. Now somehow it's working but only on determined alerts. The testing alert is not triggered and new alerts are still not triggered. Seems to be a queue but don't know how to find it to clear it

    We launched

    SELECT COUNT(*) FROM talert_execution_queue;

    but it returns 0

  7. Hello Davide,

    In this case if some alerts are working you need to check what's the difference between the one working and the one that's not.

    That way you can modify whether is the template or the action in order for it to work in the same way the others do.

    Kind regards,
    Sergio B.

  8. Hi Sergio,

    I'm using the same templates for all the alerts. It's a new machine, so we are importing just a few things and now they are using the same templates and actions.

    Is there a command to see the queue of alerts that are fired?

    Thanks

  9. Hello,

    The queued alerts will be shown in the table talert_execution_queue that you already checked.

    Does the logs contain any information that may help you figure out the problem?

    You have the possibility to set the verbosity parameter to 10

    This will provide more information on what's happening with the alert.

    Also make sure the conditions are met, both in status and threshold side.

    Try forcing a module with an alert to go to critical without forcing the alert itself.

    This way you can force the threshold and the status and when the conditions are met the alert should trigger the "fired" event.

    Kind regards,
    Sergio B.

  10. Hi Sergi,

    in the picture I sent above, the alert was forced to go down but no alert was fired. This is the main issue since if I fire it by hand, it works fine. Seems like the alert don't know that the condition is met.

    Log verbosity is already set to 10, could you share some info I need to search for?

    Thanks

Entra en tu cuenta para publicar.