Ad Widget

Collapse

zabbix_agent -p reports thing that do not work when pooled

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ghislain
    Senior Member
    • Jun 2005
    • 160

    #1

    zabbix_agent -p reports thing that do not work when pooled

    Hello,

    I used zabbix_agent -p to see what can be pooled from a host. But when i try to add one of the agent item that works with the -p i get "unsupported item" in the frontend .

    Do you know why the command line report semathing and the server cannot poll it ?

    I use linux beta2 on the server and the Freebsd 4.11 beta2 agentd precompiled (i use agentd ). The server is linux debian (compiled, no error, works fine on localhost monitoring).


    ex:

    inthe frontend i got :

    17632 vfs.fs.pfree[/] Espace dique libre 3600 7 365 ZABBIX agent (active) Not supported Not supported by ZABBIX agent

    but online with -p i got:
    fs.fs.free[*] [/] [20343876.000000]
    vfs.fs.total[*] [/] [30548966.000000]
    vfs.fs.used[*] [/] [7761173.000000]
    vfs.fs.pfree[*] [/] [66.594319]
    vfs.fs.pused[*] [/] [25.405681]



    so it return 66% in command line but unsupported in the frontend

    Any idea ?

    regards,
    Ghislain.
    Last edited by ghislain; 15-10-2005, 18:28.
    Regards,
    Ghislain.
  • James Wells
    Senior Member
    • Jun 2005
    • 664

    #2
    Greetings,

    First thing I would suggest is changing it from Zabbix Agent (Active) to just a regular Zabbix Agent query. The server is saying 'Not Supported' because it is not actually polling the agent for the information.
    Unofficial Zabbix Developer

    Comment

    • ghislain
      Senior Member
      • Jun 2005
      • 160

      #3
      humm,

      i have some problems with active checks. I guess if the passive one are going right then it cannot be firewall problem so perhaps i miss something.

      i think i will return to normal agent polling as active seems to fail. i don't know how to say to the agent to reread the configuration from the server. It seems restarting does not change the effect. I will test more but for now i go back to normal agent check.

      for exemple on one host i have a

      active check_service[http that works and a
      check_service[ftp active that does not (while of course ftp works)

      of course if i put it into normal polling then it works but the fact that the httpd check works in active and not the ftp lead me to think that this is plainly a problem of synchronisation between the agent and the server.

      Is there a way to say to the agent AND the server, okay lets start again from the start and read the config ?

      best regards,
      Ghislain.
      Last edited by ghislain; 17-10-2005, 09:57.
      Regards,
      Ghislain.

      Comment

      • rickardp
        Junior Member
        • Dec 2004
        • 27

        #4
        Active checks

        Running active checks means that the agent must be able to connect a socket back to the zabbix server, if there is a firewall inbetween as it should be in a DMZ it will not work (my network people told me I would be forced to wear a silly hat for just suggesting such an exception in the firewall).

        Use active checks when you have no firewall inbetween your agent and server

        Comment

        • ghislain
          Senior Member
          • Jun 2005
          • 160

          #5
          the funny thing here is that some active checks works, some not.
          Regards,
          Ghislain.

          Comment

          • cameronsto
            Senior Member
            • Oct 2005
            • 148

            #6
            I'm having similar issues in that 'zabbix_agentd -p' prints out my UserParameter values fine, but the web interface reports them as 'not supported' when I try to query them. They don't work as active checks either. Not sure what I'm doing wrong.

            One issue I had that I was able to fix on a few of them, was providing the full path to the executable (thanks James!). For example, for the mysql checks I needed to change 'mysqladmin' to '/usr/bin/mysqladmin'. Maybe this will help...

            -cameron

            Comment

            Working...