Raising a virtual interface completely kills Zabbix's ability to monitor agents

[ahxcjb]

Here's one for a developer to look over...(I can't quite believe this!)

On the Zabbix server: ifconfig eth0:1 192.168.4.200 up

Now lets look at my zabbix server log:

14325:20070915:034024 Assuming that agent dropped connection because of access permissions
14325:20070915:034024 Host [solo] will be checked after 60 seconds
14325:20070915:034024 Get value from agent failed. Error: ZBX_TCP_READ() failed [Connection reset by peer]
14325:20070915:034024 Host [jabba] will be checked after 60 seconds
14304:20070915:034048 Got empty string from [zahn] IP [8.65] Parameter [net.tcp.port, 587]]
14304:20070915:034048 Assuming that agent dropped connection because of access permissions
14304:20070915:034048 Host [zahn]: first network error, wait for 15 seconds
14304:20070915:034048 Parameter [net.tcp.port[solo, 587]] will be checked after 120 seconds on host [zahn]

I then drop the virtual interface..

14325:20070915:034125 Enabling host [solo]
14325:20070915:034125 Enabling host [jabba]

Now someone explain that to me please!

UPDATE: It appears that if you put the new iface in the agentd.conf on the client machines, it starts working again. But, what happens when I deploy this into our production environment which consists of around 5 NICs going to different networks? Should I be concerned?

[alj]

UPDATE: It appears that if you put the new iface in the agentd.conf on the client machines, it starts working again. But, what happens when I deploy this into our production environment which consists of around 5 NICs going to different networks? Should I be concerned?

IMO this has nothing to do with zabbix.
if you changed default interface on your machine you should put it's IP into agentd.conf prior to changing.
Any other software that requires IP ACL should be reconfigured as well.