Ad Widget

Collapse

1.8.1 items not supported

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sbadger
    Member
    • Dec 2005
    • 81

    #1

    1.8.1 items not supported

    With a new install of 1.8 (and updated to 1.8.1), I haven't bee able to make item, either custom or built-in, work correctly.
    Zabbix_get seems to be able to get it from the host, even the agent is able to pull the items, but in the web front end I keep getting "Not supported"


    From the zabbix server:
    Code:
    [root@cc1lxa10 zabbix-1.8.1]# tail -f /var/log/zabbix/zabbix_server.log| grep Cc1lnx1
      5460:20100201:122047.943 Item [Cc1lnx1:net.if.out[bond0,bytes]] error: Not supported by Zabbix Agent
      5460:20100201:122047.943 Parameter [Cc1lnx1:net.if.out[bond0,bytes]] is not supported by agent Old status [0]
      5459:20100201:122051.863 Item [Cc1lnx1:net.if.in[bond0,bytes]] error: Not supported by Zabbix Agent
      5459:20100201:122051.863 Parameter [Cc1lnx1:net.if.in[bond0,bytes]] is not supported by agent Old status [0]
    
    [root@cc1lxa10 zabbix-1.8.1]# zabbix_get -s Cc1lnx1 -k net.if.out[bond0,bytes]
    39443331162366
    [root@cc1lxa10 zabbix-1.8.1]# zabbix_get -s Cc1lnx1 -k net.if.in[bond0,bytes]
    261724664984488
    [root@cc1lxa10 zabbix-1.8.1]#
    From the client:
    Code:
    [zabbix@cc1lnx1 ~]$ /usr/local/sbin/zabbix_agentd -t net.if.in[bond0,bytes]
    net.if.in[bond0,bytes]                        [u|261791676033145]
    [zabbix@cc1lnx1 ~]$ /usr/local/sbin/zabbix_agentd -t net.if.out[bond0,bytes]
    net.if.out[bond0,bytes]                       [u|39451261554551]
    [zabbix@cc1lnx1 ~]$
  • alj
    Senior Member
    • Aug 2006
    • 188

    #2
    I had similar problem, it got resolved by building zabbix server and client without ipv6 support.

    Comment

    • sbadger
      Member
      • Dec 2005
      • 81

      #3
      Originally posted by alj
      I had similar problem, it got resolved by building zabbix server and client without ipv6 support.
      Thanks for the suggestion, but I checked my config and I don't have IPv6 enabled in either the server or the clients.

      Comment

      • alj
        Senior Member
        • Aug 2006
        • 188

        #4
        Originally posted by sbadger
        Thanks for the suggestion, but I checked my config and I don't have IPv6 enabled in either the server or the clients.
        Config has nothing to do with it. I'm talking about ./configure options during build.
        With some libc libraries (as in my case with debian etch version) if you enable ipv6 during compilation time you need to specify ipv4 server address in ipv6 form in agent/server config like this ::ffff:x.x.x.x.
        i e agent will not recognize your server address in form x.x.x.x and server will see all items as unsupported.

        You can see for yourself if you enable debug log for the agent that when it reports any IP address it is listed in ipv6 form.

        You can test if it is true by specifying server ip address in this form:
        ::ffff:1.2.3.4
        instead of
        1.2.3.4
        And check if problem went away.

        Comment

        • sbadger
          Member
          • Dec 2005
          • 81

          #5
          Sorry about that, I was talking about the ./configure.
          Here is the what I used to compile the options with:
          Code:
          [zabbix@cc1lxa10 zabbix-1.8.1]$ ./configure --enable-server --enable-agent --with-mysql --with-net-snmp --with-libcurl --with-openipmi --with-ldap
          and after that runs it says:
          Code:
          Configuration:
          
            Detected OS:           linux-gnu
            Install path:          /usr/local
            Compilation arch:      linux
          
            Compiler:              gcc
            Compiler flags:        -g -O2   -I/usr/include/mysql  -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv -fPIC   -DUNIV_LINUX -DUNIV_LINUX     -I/usr/include/rpm -I/usr/local/include -I/usr/include/gdbm -I/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -I. -I/usr/include/net-snmp   -I/usr/include  -I/usr/include
          
            Enable server:         yes
            With database:         MySQL
            WEB Monitoring via:    cURL
            Native Jabber:         no
            SNMP:                  net-snmp
            IPMI:                  openipmi
            Linker flags:           -L/usr/lib -lldap   -L/usr/lib -lOpenIPMI -lOpenIPMIposix     -L/usr/lib64/mysql    -L/usr/kerberos/lib64 -lcurl -ldl -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lidn -lssl -lcrypto -lz  -L/usr/lib64 -L/usr/lib64 -lnetsnmp -lcrypto -lm -L/usr/lib64/lib -lwrap -lcrypto  -L/usr/lib64 -L/usr/lib64 -lnetsnmp -lcrypto -lm -L/usr/lib64/lib -lwrap -lcrypto 
            Libraries:             -lm  -lresolv     -lmysqlclient    -lcurl  -lnetsnmp  
          
            Enable proxy:          no
          
            Enable agent:          yes
            Linker flags:           -L/usr/lib -lldap   -L/usr/lib -lOpenIPMI -lOpenIPMIposix
            Libraries:             -lm  -lresolv 
          
            LDAP support:          yes
            IPv6 support:          no
          
          ***********************************************************
          *            Now run 'make install'                       *
          *                                                         *
          *            Thank you for using Zabbix!                  *
          *              <http://www.zabbix.com>                    *
          ***********************************************************
          I will still set the logs to debug to see if I am seeing the IPv6 address though just in case.

          Comment

          • sbadger
            Member
            • Dec 2005
            • 81

            #6
            So after some further digging around
            It seems that the client wasn't even being polled.
            As it turns out I over looked the fact that even though I didn't give it an IP to use it chose to use the IP address instead of the DNS name that I gave it for the host.

            The front end reported the host reachable and was able to pull some data, but I'm not sure what data that would be coming from 0.0.0.0.

            Either way it is working properly now and I am a little embarrassed I missed that.

            Thanks for everyone's help

            Comment

            Working...