Ad Widget

Collapse

Actions not fired after update to v4.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ducatimonster900ie
    Junior Member
    • Oct 2018
    • 6

    #1

    Actions not fired after update to v4.0

    Hello to everyone

    after updating Zabbix in our production environment from v3.4.11 to v4.0.0 no actions are undertaken upon triggers are fired.
    The update was made compiling Zabbix from sources with the exact same options of the older version:

    ./configure --enable-server --enable-agent --enable-java --with-oracle-include=/usr/include/oracle/11.2/client64/ --with-oracle-lib=/usr/lib/oracle/11.2/client64/lib --enable-ipv6 --with-net-snmp --with-libcurl --with-libxml2 --with-openssl --with-unixodbc

    We also tried configuring a new TEST action for all events and all hosts but the result is the same!

    Is there something we are missing?

    Thanks in advance.
  • zux
    Member
    • Sep 2018
    • 93

    #2
    can you show some of those triggers? I have not heard that there where any syntax changes.
    What you can try, is the expression calculator (available under expression constructor in triggers)

    Comment

    • ducatimonster900ie
      Junior Member
      • Oct 2018
      • 6

      #3
      Hi

      we have problems with "Actions" not "Triggers".
      Triggers are fired correctly but no configured Actions, like email notifications, are undertaken since the update.

      Thanks.

      Comment

      • zux
        Member
        • Sep 2018
        • 93

        #4
        Sorry, I have no idea how I got to triggers
        Ok then, show us some actions.
        Is the alerter process running?
        ps aux | grep alerter

        increase alerter log:
        zabbix_server -R log_level_increse=alerter
        and look in log file.

        Comment

        • ducatimonster900ie
          Junior Member
          • Oct 2018
          • 6

          #5
          Thanks for your support.

          Yes, the alerter is running:
          The output for "ps aux | grep alerter" is the following:

          zabbix_+ 17939 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #1 started
          zabbix_+ 17940 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #2 started
          zabbix_+ 17941 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #3 started
          zabbix_+ 17942 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #4 started
          zabbix_+ 17943 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #5 started
          zabbix_+ 17944 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #6 started
          zabbix_+ 17945 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #7 started
          zabbix_+ 17946 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #8 started
          zabbix_+ 17947 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #9 started
          zabbix_+ 17948 0.0 0.0 5256244 5428 ? S 11:52 0:00 /usr/local/sbin/zabbix_server: alerter #10 started



          The "zabbix_server -R log_level_increse=alerter" command seems not to be supported by v4.0:

          zabbix_server [24765]: invalid runtime control option: log_level_increse=alerter

          Comment

          • ducatimonster900ie
            Junior Member
            • Oct 2018
            • 6

            #6
            Sorry

            corrected last command with:

            zabbix_server -R log_level_increase=alerter

            An "a" was missing!

            Comment

            • ducatimonster900ie
              Junior Member
              • Oct 2018
              • 6

              #7
              We found the following error in the zabbix server log after each trigger is fired:

              query failed: [-1] ORA-00979: not a GROUP BY expression [select e.eventid,e.source,e.object,e.objectid,e.clock,e.v alue,e.acknowledged,e.ns,e.name,e.severity,max(es. suppress_until) from events e left join event_suppress es on e.eventid=es.eventid where e.eventid in (5338685,5338686) group by e.eventid order by e.eventid]

              We are using Oracle in our environment.
              Maybe this is the cause why actions are not undertaken?
              Last edited by ducatimonster900ie; 24-10-2018, 12:52.

              Comment

              • ducatimonster900ie
                Junior Member
                • Oct 2018
                • 6

                #8
                The working query is:

                select e.eventid,e.source,e.object,e.objectid,e.clock,e.v alue,e.acknowledged,e.ns,e.name,e.severity,max(es. suppress_until) from events e left join event_suppress es on e.eventid=es.eventid where e.eventid in (5338685,5338686) group by e.eventid,e.source,e.object,e.objectid,e.clock,e.v alue,e.acknowledged,e.ns,e.name,e.severity order by e.eventid

                Maybe this should be reported as a bug?

                Thanks.

                Comment


                • vso
                  vso commented
                  Editing a comment
                  This is already fixed in 4.0.1
              Working...