Ad Widget

Collapse

Status value not updating

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • disgruntleddutch
    Member
    • Oct 2006
    • 34

    #1

    Status value not updating

    Ok this problem has completely gotten the best of me.

    I am monitoring 23 hosts on our external Zabbix server (monitoring hosts not located in our network). However it seems that the status value is not updating for 20 servers, only for 3 servers.

    There is an error on the servers that are not updating that says: "Not supported by agent". The log files on these machines do not state the reason why.


    This is what I know:

    The 3 servers that are working have the following in common:
    same kernel (2.6.8-2-686-smp)
    same subnet

    All 23 servers are debian machines running a variety different kernels (2.4.25, 2.6.8 & 2.6.17). Other servers running 2.6.8 in the same subnet are not reporting the status value as well.

    The zabbix_agentd was compiled on a 2.6.17 (the zabbix server) with --enable-static flag. This binary has been distributed to all the 23 servers.

    All servers are now running agent 1.1.3, however this problem was also present in agent 1.1.2 and the precompiled agent (ver 1.1) on zabbix.com.

    What am I doing wrong and what can I do to fix this. RIght now if the agent were to be disabled or the machine were to go down, all items that the zabbix server is monitoring (including simple checks such as ping) show as "not supported" thus I don't get paged when a machine goes down. I can't do any SNMP related checks as our multiple firewalls wont allow it (had to go through great lengths to get port 10050 and 10051 opened).
  • disgruntleddutch
    Member
    • Oct 2006
    • 34

    #2
    This is what the agent log on the machine running zabbix itself
    030817:20061030:142942 In send_value([ZBX_NOTSUPPORTED])
    030817:20061030:142942 XML before sending [<req><host>bG9jYWxob3N0</host><key>c3RhdHVz</key><data>WkJYX05PVFNVUFBPUlRFRA==</data></req>]
    030817:20061030:142942 NOT OK [localhost:status]
    030817:20061030:142942 Sleeping for 10 seconds

    Comment

    • disgruntleddutch
      Member
      • Oct 2006
      • 34

      #3
      So im an idiot.

      Read the documentation a few times and saw on one page that the status flag requires something else in order to stay working (makes sense, to compare it to a value that it is still being read). So I have setup fping and icmpping to all my servers. Since its all within the same WAN, ping reliability isn't a problem (i have my trigger setup so it will alert me after two failures, just in case).

      Comment

      • Alexei
        Founder, CEO
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Sep 2004
        • 5654

        #4
        Note that the "status" is a special item updated by ZABBIX Server itself depending on network errors occuring while communicating with a monitored host.
        Alexei Vladishev
        Creator of Zabbix, Product manager
        New York | Tokyo | Riga
        My Twitter

        Comment

        • Calimero
          Senior Member
          • Nov 2006
          • 481

          #5
          Hi,

          I'd like to know what kind of data is used to define "status". So far my tests show (or at least seem to show) that only SNMP queries and Agent checks are used to determine whether status' value. Neither Ping nor simple checks influence status.

          Can anyone confirm ?

          Thanks.

          Comment

          • Alexei
            Founder, CEO
            Zabbix Certified Trainer
            Zabbix Certified SpecialistZabbix Certified Professional
            • Sep 2004
            • 5654

            #6
            Yes, you're absolutely right!
            Alexei Vladishev
            Creator of Zabbix, Product manager
            New York | Tokyo | Riga
            My Twitter

            Comment

            Working...