Home / server / Questions / 252011
In Process
brandizzi
Asked: 2011-03-26 13:44:12 +0800 CST

Zabbix 1.8.2 agent does not work when monitored Debian system has IPv6 enabeld

  • 772

We have a Zabbix Server 1.8.2 running on an Debian VM - installed from the repositories of Squeeze. Also, we are installing Zabbix 1.8.2 agents in various other VMs, most of them running Debian, installed through apt-get, too.

Once we installed the agent in the host and create the corresponding host in server, we cannot make the server collect info from the agent if the monitored host does support IPv6. If we disable IPv6 on the monitored host, the agent works well and the server monitors it flawlessly.

The question is: why does this happen? Is there another way to avoid this problem? There has some way of "disabling IPv6" out of Zabbix agent?

Thanks in advance!

debian ipv6 zabbix zabbix-agent

2 Answers

  1. Hard to say why this might be happening without some more debugging information. Some questions and commands that will help people better troubleshoot:

    • Are you disabling IPv6 on just the agent host or both the agent and the server?
    • If only the agent, is IPv6 running on the server?
    • Are the server and agent hosts within the same subnet or do they route between each other?
    • When IPv6 is enabled, are you configuring a static address or using the automatic neighbor detection?

    With IPv6 enabled, run the following commands as root on the server and client and post the output here.

    ifconfig -a
netstat -anp
route -n
cat /etc/hosts

    It could be something simple like the hostname of the machines resolving to the IPv6 address when IPv6 is enabled but it is not able to route between each other using the IPv6 address. This information would help me and likely others figure out what is happening.

    • 1

  2. This was a bug in zabbix_agentd that was fixed in 1.8.5.

    This will be available in wheezy. It's been proposed for squeeze-backports, though nothing has happened so far.

    If you can't update, you can work around it by specifically setting the ListenIP directive to your exact IPv4 address, for example:

    ListenIP=198.51.100.30
    • 1