Ad Widget

Collapse

Zabbix server agent.ping is failing to itself

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • moshikoy
    Member
    • Aug 2017
    • 56

    #1

    Zabbix server agent.ping is failing to itself

    Hi,
    My zabbix server is failing to run agent.ping to itself.

    root@zabbixsrv:/etc/zabbix# zabbix_get -s zabbixsrv -k agent.ping
    zabbix_get [29171]: Check access restrictions in Zabbix agent configuration


    On zabbix GUI the server is set to use this interface
    192.168.16.121:10050

    Zabbix agent config
    root@zabbixsrv:/etc/zabbix# cat zabbix_agentd.conf| grep Server
    Server=192.168.16.121,127.0.0.1
    ServerActive=192.168.16.121



    Any idea why is this happening?

    - Mosh



  • brunohl
    Senior Member
    Zabbix Certified Specialist
    • Mar 2019
    • 215

    #2
    I guess that either the name of the host must be in the zabbix_agentd.conf (e.g. Server=192.168.16.121,127.0.0.1,zabbixsrv), don't know if it will work, or use your zabbix_get to 127.0.0.1 (e.g. zabbix_get -s 127.0.0.1 -k agent.ping

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #3
      Other thing is that if in this case agent is really used in active mode opening passive port is kind of incorrect because:
      - active monitoring is used to have better scaleability
      - active mode is used to use secure monitoring strategy (communication is only allowed from agents to serve/proxies) and in such case keeping allowed traffic in reverse direction violates what active monitoring gives.

      If rally in this case is used active monitoring using agent.ping item should be dropped.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      • moshikoy
        Member
        • Aug 2017
        • 56

        #4
        Thanks for all your help
        it appears that zabbix_get was version 3.4 while zabbix server/agent is 4.0.2
        after upgrading zabbix_get the issue resolved

        - Mosh

        Comment

        Working...