Ad Widget

Collapse

[BUG] Agent.ping problems and update intervals

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [BUG] Agent.ping problems and update intervals

    Hi there.

    I've noticed the following:
    - there is item in templates "Template App Zabbix Agent: Agent ping" which pings if agent is reachable - however the problem is that no matter how much you set update interval, it will still send notifications every 1 minute.

    Any idea why is that? If I configure to check this item 300 - 600 seconds - there is no difference. I still get email every 60 seconds.

    I've enabled debug level 4 and here are the entries.
    21215:20191106:092900.239 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:092900.240 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:092900.240 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:092930.250 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:092930.252 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:092930.252 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093000.261 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093000.273 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093000.275 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093030.287 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093030.290 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093030.291 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093100.300 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093100.302 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093100.303 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093130.336 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093130.341 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093130.343 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093200.360 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093200.365 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093200.367 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093230.383 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093230.397 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093230.399 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093300.412 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093300.419 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093300.421 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093330.431 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093330.433 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093330.434 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093400.447 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093400.452 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093400.454 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093430.467 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093430.479 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093430.481 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21231:20191106:093455.303 In get_value_agent() host:'SERVER_NAME - SERVER_IP' addr:'SERVER_IP' key:'agent.ping' conn:'unencrypted'
    21215:20191106:093500.498 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093500.502 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093500.504 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21231:20191106:093525.303 Item [SERVER_NAME - SERVER_IP:agent.ping] error: Get value from agent failed: cannot connect to [[SERVER_IP]:10050]: [4] Interrupted system call
    21215:20191106:093530.523 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093530.528 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093530.530 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093600.542 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093600.543 End of evaluate() error:'Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".'
    21215:20191106:093600.544 evaluate_expressions():expression [(ZBX_UNKNOWN0)=1] cannot be evaluated: Cannot evaluate expression: "Cannot evaluate function "SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)": item does not have enough data after server start or item creation.".
    21215:20191106:093630.563 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21222:20191106:093632.966 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21222:20191106:093632.976 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21215:20191106:093700.616 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21222:20191106:093702.031 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21222:20191106:093702.042 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21215:20191106:093730.670 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21222:20191106:093732.079 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21222:20191106:093732.086 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21215:20191106:093800.709 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21222:20191106:093802.137 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    21222:20191106:093802.145 End of DCexpand_trigger_expression() expression:'{SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1'
    Trigger expression: {SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)}=1
    And second:
    21215:20191106:093800.708 In zbx_evaluate_item_functions() funcs_num:29
    21215:20191106:093800.709 In evaluate_function() function:'SERVER_NAME - SERVER_IP:agent.ping.nodata(10m)'
    21215:20191106:093800.709 In evaluate_NODATA()
    21215:20191106:093800.709 In get_function_parameter_int() parameters:'10m' Nparam:1
    21215:20191106:093800.709 In substitute_simple_macros() data:'10m'
    21215:20191106:093800.709 get_function_parameter_int() type:sec value:600
    21215:20191106:093800.709 End of get_function_parameter_int():SUCCEED
    21215:20191106:093800.709 In zbx_vc_get_value_range() itemid:28495 value_type:3 seconds:600 count:1 timestamp:1573029480
    21215:20191106:093800.709 End of zbx_vc_get_value_range():SUCCEED count:0 cached:1
    21215:20191106:093800.709 End of evaluate_NODATA():SUCCEED
    21215:20191106:093800.709 End of evaluate_function():SUCCEED value:'1'
    I've noticed same problem on different Zabbix servers version:
    3.4.15
    4.2.8

    Seems like there is some issue with this evaluate functions?

    How to fix this?

    #2
    UP!

    Still have issues with this.

    Comment


      #3
      You wrote that an email is sent every 60 seconds, is that during the failure? If so, have you configured the action to send email continuously during the failure? Please check the action settings.

      Comment


        #4
        Originally posted by Atsushi View Post
        You wrote that an email is sent every 60 seconds, is that during the failure? If so, have you configured the action to send email continuously during the failure? Please check the action settings.
        During the failure - correct. Also yes - but that doesn't mean it should send email every 60secs if I'm checking it e.g. every 5 minutes.
        If event is down 1 hour - I should get only 12 emails (5 min checks * 12 = 60) and not 60 emails (every 60 seconds), correct?

        Comment


          #5
          Please check your action settings.
          The setting that keeps sending emails during a failure may be configured to do so in the action settings.

          Comment


            #6
            Under actions I only have options set to send message to zabbix administrators and to execute script, nothing else. There is no 60sec timer there. Recovery is disabled.
            First I noticed that under host I have defined agent.ping.nodata to 300sec, but on zabbix template agent this was set to 60 - so I though...ok, maybe this is overwriting the host value and changed it also there. Now I'm not to find any agent ping value with 60 sec, however emails are still sent that frequently.

            Comment


              #7
              Is the step set in the operation details of the action settings? How are the steps set now?

              It seems that the argument of nodata() has been changed, but it does not match the contents output to the log. If the settings do not match the resulting log, I don't know what settings you are currently doing.

              Comment


                #8
                Operation details:
                Steps 1-1 (0 - infinitely)
                Step duration (0 - use action default)
                Operation type - Send message
                Send to User groups - Zabbix administrators
                Send only to - Email with SMTP Auth (this is simple script that send emails via SMTP, not plain)
                Default message - CHECKED

                Comment


                  #9
                  Thank you for telling me what the action settings are.

                  Are you using the trigger “Zabbix agent on {HOST.NAME} is unreachable for 5 minutes” in the default template? Which is selected for “PROBLEM event generation mode”?
                  If Mulliple is selected, nodata() will evaluate the conditional expression once every 30 seconds regardless of the argument specification, so an event will occur and the action will be executed each time. If you want to be notified by e-mail at a longer time interval while the failure continues, you should set the event generation mode to single and specify the steps in the action settings.

                  Comment


                    #10
                    It's multiple indeed. So I should configure exactly what in action settings? New step(s)? How many?
                    This is something that has changed in latest versions of zabbix - I've been using this in past in 2.x versions and it worked as expected.

                    Comment

                    Announcement

                    Collapse
                    No announcement yet.
                    Working...
                    X