Hi, Jordi…
Jordi Mallach wrote:
My use case was using it to monitor vservers (using Linux-VServer, available
in Debian) and the hosts.
One of the requirements for TCP/IP ports usage in a vserver is that the port
isn't bound to 0.0.0.0 in the host, so you typically bind to only the IPs
you
Issue reported upstream at: https://support.zabbix.com/browse/ZBX-1089
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Christoph,
On Sat, Oct 10, 2009 at 02:00:24PM +0200, Christoph Haas wrote:
mind if I ask what the possible use case of binding to multiple network
interfaces is? I can report it upstream and see if the developers are
willing to implement it. But usually the agent is queried from a single
Hi, Jordi...
mind if I ask what the possible use case of binding to multiple network
interfaces is? I can report it upstream and see if the developers are
willing to implement it. But usually the agent is queried from a single
Zabbix server. So binding to a single interface should suffice. Or am
Package: zabbix-agent
Version: 1:1.4.6-1
Severity: normal
Zabbix agent (and possibly zabbix_server, but I havent checked this)
doesn't appear to be able to bind to multiple network interfaces.
It's either all (0.0.0.0) or just one.
I have tried using:
ListenIP=127.0.0.1,192.168.1.10,10.0.0.1
5 matches
Mail list logo
