zabbix-agent2 on CentOS 7 ipv4 problem

[anmg]

Hi,

Installed zabbix-agent2 on CentOS 7 and get in stuck with:
it does not listen ipv4, the only ipv6

ListenIP=0.0.0.0

netstat -tulpn | grep zabbix
tcp6 0 0 :::10050 :::* LISTEN 11369/zabbix_agent2

error from log:

cannot parse "ListenIP" parameter: value of ListenIP not present on the host: "0.0.0.0"

[tim.mooney]

Does the behavior change if you comment out the "ListenIP" entry from the agent config and restart the agent2?

Does your /etc/hosts have both IPv4 and IPv6 entries for 'localhost'?

[anmg]

Does the behavior change if you comment out the "ListenIP" entry from the agent config and restart the agent2?

nothing changed

Does your /etc/hosts have both IPv4 and IPv6 entries for 'localhost'?

yes
usual zabbix-agent works

[Glukas]

Normally you doesn't need ListenIP directive, especially when you leave it as 0.0.0.0 - that is the default value.
Can you disable IPv6 on the host or you need it?
Even if you need it, you can try to disable just to test.

[prok_iv]

Hello, I faced with this moment with agent2 on Debian.... anmg , I will be very appreciate for sharing how you fixed this issue. It looks like very rary case after searching information.

[fblank]

Any solution to the issue of zabbix-agent2 not listening on IPV4?
I have the same issue as described above. IPV6 transport gets established when starting the agent2 but no IPV4 listener. I have an Oracle Linux 9 installation with docker compose based zabbix-server (v7.2.1) and another Oracle Linux 9 server with the zabbix-agent2 (v7.2.2) installed from the zabbix repo's (sudo yum install zabbix-agent2)

[fblank]

Solved!
turned out to be very simple: The ListenIP in the zabbix-agent2.conf file needs to be filled in with an IPV4 format (contrary to the regular zabbix agent, IPV6 seems to be the default. with the agent2)