Ad Widget

Collapse

Active agents still broken in 1.6.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bluelinq
    Member
    • Feb 2008
    • 44

    #1

    Active agents still broken in 1.6.2

    Just upgraded to 1.6.2 form 1.6.1 and since 1.6 active agents are broken. All my remote servers use active agents and they don't report anything.

    If I switch the zabbix server code to the 1.4.6 release they start working again, so no change in the agents or the config files, just zabbix_server.

    Anyone in development have a solutions to this?

    Regards,

    Paul
  • ufocek
    Senior Member
    • Aug 2006
    • 161

    #2
    Hi,

    I'm upgrading today zabbix from 1.6.1 to 1.6.2 and I have this same problem. In log I have this:

    7488:20090119:075603 Item [noc:net.if.out[eth0,bytes]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:net.tc.port[93.12.50.18,22100]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:sensor[temp2]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:vfs.dev.read[sda1,operations]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:vfs.dev.write[sda1,operations]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:net.if.in[eth1,bytes]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:sensor[temp2]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:kernel.maxproc] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:net.if.out[eth1,bytes]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:sensor[temp3]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:system.cpu.util[,wait,avg1]] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:kernel.maxproc] error: Not supported by ZABBIX agent
    7488:20090119:075603 Item [noc:net.if.out[eth1,bytes]] error: Not supported by ZABBIX agent

    7494:20090119:075003 Send list of active checks to [213.25.112.2] failed: host [foo1] not found
    7517:20090119:075038 Send list of active checks to [192.168.1.211] failed: host [foo2] not found
    7492:20090119:075038 Send list of active checks to [83.13.221.238] failed: host [foo3] not found

    Comment

    • bluelinq
      Member
      • Feb 2008
      • 44

      #3
      Actually I found my problem. According to the documentation the name of the server in Zabbix should match the name of the HostName variable in the zabbix_agentd.conf file. What is missing is that both should also be in the same case, either both lower or both upper case.

      It used to work fine in 1.4.6, but I guess that was changed in 1.6 and so on.

      Regards,

      Paul

      Comment

      • Calimero
        Senior Member
        • Nov 2006
        • 481

        #4
        Indeed there was another topic related to that issue. It can be fixed quite easily in zabbix_server code so that you won't have to rename all of your hosts.

        Edit again: I confirm that 1.6.2 still is case sensitive.

        Code:
        if (0 == strcmp(item.host_name, values[i].host_name) && 0 == strcmp(item.key_orig, values[i].key)) {
        Line 216 from src/zabbix_server/trapper/trapper.c

        If you change it to:
        Code:
        if (0 == strcasecmp(item.host_name, values[i].host_name) && 0 == strcmp(item.key_orig, values[i].key)) {
        Then it won't be case sensitive anymore regarding hostname (key name will still be case sensitive).
        Last edited by Calimero; 19-01-2009, 11:02.

        Comment

        Working...