Ad Widget

Collapse

Error: Not supported by Zabbix Agent ...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • augusstynr
    Junior Member
    • Jan 2009
    • 4

    #1

    Error: Not supported by Zabbix Agent ...

    Hi,
    I get a banch of errors in the logs any idea what to do about it?


    5748:20100121:175719.182 Item [Zabbix Server:kernel.maxproc] error: Not supported by Zabbix Agent
    5745:20100121:175721.512 Item [Zabbix Server:net.if.in[eth1,bytes]] error: Not supported by Zabbix Agent
    5748:20100121:175724.191 Item [Zabbix Server:net.if.out[eth1,bytes]] error: Not supported by Zabbix Agent
    5746:20100121:175742.491 Item [Zabbix Server:sensor[temp1]] error: Not supported by Zabbix Agent
    5747:20100121:175743.903 Item [Zabbix Server:sensor[temp2]] error: Not supported by Zabbix Agent
    5748:20100121:175744.297 Item [Zabbix Server:sensor[temp3]] error: Not supported by Zabbix Agent
    5747:20100121:175803.954 Item [Zabbix Server:vfs.file.cksum[/etc/inetd.conf]] error: Not supported by Zabbix Agent
    5747:20100121:175809.966 Item [Zabbix Server:vfs.file.cksum[/vmlinuz]] error: Not supported by Zabbix Agent
    5745:20100121:180106.825 Item [winxp-l1erf_counter[\Physical Disk(_Total)\Avg. Disk Read Queue Length]] error: Not supported by Zabbix Agent
    5747:20100121:180113.201 Item [winxp-l1roc_cnt[httpd]] error: Not supported by Zabbix Agent
    5746:20100121:180122.871 Item [winxp-l1:system.uptime] error: Not supported by Zabbix Agent
    5747:20100121:180123.214 Item [winxp-l1:system[procrunning]] error: Not supported by Zabbix Agent
    5748:20100121:180129.513 Item [winxp-l1:vfs.fs.size[d:,free]] error: Not supported by Zabbix Agent
    5744:20100121:180130.622 Item [winxp-l1:vfs.fs.size[d:,total]] error: Not supported by Zabbix Agent
    Last edited by augusstynr; 22-01-2010, 04:36.
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    You can simply disable those items in the frontend for that host. They have some default items in the templates and assumptions are made, such as the machine having a D: drive. If there is no D: drive, then it goes into an unsupported state.

    Comment

    • augusstynr
      Junior Member
      • Jan 2009
      • 4

      #3
      Originally posted by tchjts1
      You can simply disable those items in the frontend for that host. They have some default items in the templates and assumptions are made, such as the machine having a D: drive. If there is no D: drive, then it goes into an unsupported state.
      Thank you very much

      Comment

      • alfiere
        Member
        • May 2008
        • 51

        #4
        Let me resume the post please.

        I have more than 50 serves associated to the same template.

        As you can image some Items are not supported by some servers (the average is 5 for each server)

        50 * 5 means 250 log entries every checks...

        Can u suggest me a way to disable all this unsupported items?
        (server by server, manually, is very tedious!)

        Thanks a lot,
        Cheers,
        Alf

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          Is it the same 5 items for each server? Simple solution is to disable those 5 items at the template level. That then propogates down to all the hosts associated with that template.

          If it is different items on each server... then I see no easy way to do it.

          Comment

          Working...