Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-25931

Failed systemd services disabled after discovery

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • None
    • None
    • None

      Steps to reproduce:
      Terminate a systemd service and the status of the items changes to failed. The Trigger "Systemd: {#UNIT.NAME}: Service is not running" changes to the status Problem. But only until the next discovery "Service units discovery" runs. Only systemd services with activestate = active will be discovered and therefor systemd services with activestate = failed will be immediatle disabled. So the Trigger will also be disabled immediatly after the discovery.

      Result:
      Trigger of a failed systemd service is disabled after the next discovery.

      Expected:
      Please change the macro {$SYSTEMD.ACTIVESTATE.SERVICE.MATCHES} to (active|failed) in the Systemd by Zabbix Ageng 2 template.

            zit Zabbix Integration Team
            huna Hubert Nachbaur
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: