Ad Widget

Collapse

netloadin[ppp0] not supported?!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dfilion
    Junior Member
    • Apr 2005
    • 6

    #1

    netloadin[ppp0] not supported?!

    I've been trying to get Zabbix to monitor ppp0. So far no luck. I've based ppp0's setup on the netloadin15[eth0] configuration. zabbix_agentd is being used.

    When I first add the item, it's listed as inactive. I select it and choose "Activate selected" and it comes up Active. However, upon refreshing the page, it shows a status of "Not Supported". It's the same for netloadin1, netloadin10 and netloadin15.

    There is nothing in zabbix_agentd.log about ppp0 at all.
    Last edited by dfilion; 26-04-2005, 16:38.
  • dfilion
    Junior Member
    • Apr 2005
    • 6

    #2
    Interface not supported...Follow up

    Follow up:
    Setting the log level to 4, increased the info, but is still no help.

    Here is the contents of the zabbix_agentd.log:
    001714:20050426:101332 In check_security()
    001714:20050426:101332 Connection from [127.0.0.1]. Allowed servers [127.0.0.1,10.0.0.1,65.39.196.233,65.39.196.234,192 .168.7.2,192.168.0.1,69.28.196.239]
    001714:20050426:101332 Before read()
    001714:20050426:101332 After read() 2 [17]
    001714:20050426:101332 Got line:netloadin5[ppp0]
    001714:20050426:101332 Sending back:ZBX_NOTSUPPORTED

    Here is the contents of suckerd.log:
    001732:20050426:101332 slack netloadin15[ppp0]
    001732:20050426:101332 Sending [netloadin15[ppp0]
    ]
    001732:20050426:101332 Got string:[17] [ZBX_NOTSUPPORTED
    ]
    001732:20050426:101332 NOTSUPPORTED2 [ZBX_NOTSUPPORTED]
    001732:20050426:101332 GOT VALUE [(*),min(nextcheck) from items i,hosts h where (h.status=0 or (h.status=2 and h.disable_until<1114524808)) and h.hostid=i.hostid and i.status=0 and i.type not in (2) and i.itemid%1=0 and i.key_<>'status' and i.key_<>'icmpping' and i.key_<>'icmppingsec']
    001732:20050426:101332 Parameter [netloadin15[ppp0]] is not supported by agent on host [slack]
    001732:20050426:101332 In DBupdate_item_status_to_notsupported()
    001732:20050426:101332 SQL [update items set status=3 where itemid=17321]
    001732:20050426:101332 Executing query:update items set status=3 where itemid=17321
    001732:20050426:101332 In DBnum_rows
    001732:20050426:101332 Result of DBnum_rows [8]
    001732:20050426:101332 slack netloadin1[ppp0]
    001732:20050426:101332 Sending [netloadin1[ppp0]
    ]
    001732:20050426:101332 Got string:[17] [ZBX_NOTSUPPORTED
    ]
    001732:20050426:101332 NOTSUPPORTED2 [ZBX_NOTSUPPORTED]
    001732:20050426:101332 GOT VALUE [(*),min(nextcheck) from items i,hosts h where (h.status=0 or (h.status=2 and h.disable_until<1114524808)) and h.hostid=i.hostid and i.status=0 and i.type not in (2) and i.itemid%1=0 and i.key_<>'status' and i.key_<>'icmpping' and i.key_<>'icmppingsec']
    001732:20050426:101332 Parameter [netloadin1[ppp0]] is not supported by agent on host [slack]
    001732:20050426:101332 In DBupdate_item_status_to_notsupported()
    001732:20050426:101332 SQL [update items set status=3 where itemid=17319]
    001732:20050426:101332 Executing query:update items set status=3 where itemid=17319
    001732:20050426:101332 In DBnum_rows
    001732:20050426:101332 Result of DBnum_rows [8]
    001732:20050426:101332 slack netloadin5[ppp0]
    001732:20050426:101332 Sending [netloadin5[ppp0]
    ]
    001732:20050426:101332 Got string:[17] [ZBX_NOTSUPPORTED
    ]
    001732:20050426:101332 NOTSUPPORTED2 [ZBX_NOTSUPPORTED]
    001732:20050426:101332 GOT VALUE [(*),min(nextcheck) from items i,hosts h where (h.status=0 or (h.status=2 and h.disable_until<1114524808)) and h.hostid=i.hostid and i.status=0 and i.type not in (2) and i.itemid%1=0 and i.key_<>'status' and i.key_<>'icmpping' and i.key_<>'icmppingsec']
    001732:20050426:101332 Parameter [netloadin5[ppp0]] is not supported by agent on host [slack]
    001732:20050426:101332 In DBupdate_item_status_to_notsupported()
    001732:20050426:101332 SQL [update items set status=3 where itemid=17320]
    001732:20050426:101332 Executing query:update items set status=3 where itemid=17320
    001732:20050426:101332 In DBnum_rows
    001732:20050426:101332 Result of DBnum_rows [8]

    I've confirmed Zabbix has access to /proc/net/dev:
    $ cat /proc/net/dev
    Inter-| Receive | Transmit
    face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
    lo:795290411 12781243 0 0 0 0 0 0 795290411 12781243 0 0 0 0 0 0
    teql0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    eth0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    eth1:1913763860 9315936 0 0 0 0 0 0 1965343548 8229804 0 0 0 0 0 0
    dummy0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    eth2:3137516751 9237294 0 0 0 0 0 0 1182317220 13247091 0 0 0 0 0 0
    tunl0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    gre0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    ppp0:377961165 821777 0 0 0 0 0 0 69489025 855510 0 0 0 0 0 0


    Querying the FAQ and the forums only turns up my own posts on the subject.

    Zabbix is version 1.0.

    Comment

    • dfilion
      Junior Member
      • Apr 2005
      • 6

      #3
      Follow-up

      Upgrading to 1.1a7 fixed the problem, though I'm still curious why 1.0 didn't work.

      Comment

      • k3nny

        #4
        Even more curios is that all my agents worked perfectly for monitoring ppp0, and on one multi-homed box with both ppp0 and ppp1.

        Suddenly, from this weekend, ppp0 is not supported on one of my agents. It's been working for weeks priors to this...

        Comment

        • btriem
          Member
          • Apr 2006
          • 30

          #5
          similar problem with eth0 and other services

          I am having the same problem with 1.1beta9, its not coming up with anything for eth0 and the debugging logs give me: Sending back:ZBX_NOTSUPPORTED, nothing else.

          But in version 1.0 it worked just dandy. Also hda queries, filesystem size queries, and a couple others that once worked on the same server with 1.0, no longer work with 1.1beta9. And I did not upgrade, I completely replaced.

          Has anyone else run into this problem and has anyone found a resolution?

          Comment

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

            #6
            1.1 uses completely different naming for item keys. Please check documentation.
            Alexei Vladishev
            Creator of Zabbix, Product manager
            New York | Tokyo | Riga
            My Twitter

            Comment

            Working...