Problem with new zabbix agent's Server= config token.

[alj]

At first I almost gave up to run 1.6.5 agent on my system (it just wouldn't work) but then i found that it requires ipv6 address in zabbix-agentd config.
i e old 1.4 zabbix works fine if config has
Server=1.2.3.4
But new one (1.6.5) doesn't unless you change that line to
Server=::ffff:1.2.3.4

Is there any way to disable ipv6 and revert it to old behavior? Otherwise i got too many config files to update.

UPDATE: fixed it now by recompiling without ipv6, but it should be fixed anyway permanently somehow probably because debian packages come compiled with ipv6 by default... i e zabbix probably should decetc that ip address is v4 and use v4 format if that is so.

[NOB]

At first I almost gave up to run 1.6.5 agent on my system (it just wouldn't work) but then i found that it requires ipv6 address in zabbix-agentd config.
i e old 1.4 zabbix works fine if config has
Server=1.2.3.4
But new one (1.6.5) doesn't unless you change that line to
Server=::ffff:1.2.3.4

Is there any way to disable ipv6 and revert it to old behavior? Otherwise i got too many config files to update.

UPDATE: fixed it now by recompiling without ipv6, but it should be fixed anyway permanently somehow probably because debian packages come compiled with ipv6 by default... i e zabbix probably should decetc that ip address is v4 and use v4 format if that is so.

Your work-around was our solution, too. Do not include --enable-ipv6 in the configure call !

But, there were other problems on RedHat Linux 5.3 and other distros.
The apache just listens on the IPv6-address, not on the IPv4 address, etc. pp.
So we disabled (blacklist) the ipv6 module, completely, to get it working.
Perhaps Debian is too early to adopt IPv6 on Linux ?

We had to specify :::1 as the IP-address of our (IPv6) localhost.
We don't have a different solution for now, but it might not only be
a ZABBIX problem.

Regards

Norbert.