Ad Widget

Collapse

Alarm clock for more than 3 sec

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • coffeecat
    Junior Member
    • Jul 2011
    • 7

    #1

    Alarm clock for more than 3 sec

    I want use zabbix instead nagios. I have a trouble, need help.

    I have many server, each server need to ping it's master/slave,so it's different for each server,I want exec this command to easier for insted.

    example:
    In nagios I write in nrep.conf.
    /usr/local/nagios/libexec/check_ping -H 192.168.1.1 -p 5 -w 1,20% -c 2,20%

    In zabbix I write:
    UserParameter=nagios.check_ping,/usr/local/nagios/libexec/check_ping -H 192.168.1.1 -p 5 -w 1,20% -c 2,20%

    And use this for test:
    /usr/local/zabbix/sbin/zabbix_agentd -c /usr/local/zabbix/zabbix_agentd.conf -t "nagios.check_ping"

    I found exec this must less 3 sec,more than 3 sec just view "alarm clock"
    Modify zabbix_agentd.conf of Timeout,but is not work.

    for 3 sec (-p 3)
    [root@localhost zabbix]# /usr/local/zabbix/sbin/zabbix_agentd -c /usr/local/zabbix/zabbix_agentd.conf -t "nagios.check_ping"
    nagios.check_ping [t|PING OK - Packet loss = 0%, RTA = 0.55 ms|rta=0.549000ms;1.000000;2.000000;0.000000 pl=0%;20;20;0]
    for 4 sec (-p 4)
    [root@localhost zabbix]# /usr/local/zabbix/sbin/zabbix_agentd -c /usr/local/zabbix/zabbix_agentd.conf -t "nagios.check_ping"
    Alarm clock
  • ghoz
    Senior Member
    • May 2011
    • 204

    #2
    check the timeouts for your agent. looks like your nagios check take more time than the agent is willing to wait for.
    on a related note if you have a lot of items that may take a long time, you should boost the number of agent processes as well. a check like this one, will block a process for the fill 4 seconds it needs...


    you could also use some integrated check like net.tcp.port[<ip>,port] on your hosts. I don't think the icmpping tests work on the agent unfortunately
    Last edited by ghoz; 11-07-2011, 09:39.

    Comment

    • coffeecat
      Junior Member
      • Jul 2011
      • 7

      #3
      I set agent timeouts again ,set 15 or 60 ,but is not work. if zabbix_agent test is not ok,the server is not ok.

      net.tcp.port is not good way for me, Becase I want check pingloss, is very useful for me.

      Thank you anyway

      Comment

      • ghoz
        Senior Member
        • May 2011
        • 204

        #4
        I'm sorry to insist, but did you change the timeout in the agent config file too ?

        by default the agent will wait 3secs for the command to complete... the coincidence with your problem is troubling...

        Comment

        Working...