Hi,
I just saw the notice the Zabbix 3.0.0 LTS was released and I was already running the Alpha2 version, so I just went quickly and updated on my test environment to see how it goes.
The test environment consists in a small hardware machine as zabbix server, an openstack instance serving as zabbix proxy, and several agents on hardware and virtuals.
I run a discovery process on the proxy instance, to search for other openstack machines on a certain network, if a discoverer child start, he instantly kills the whole proxy, the error I see when Debug=4 is:
9087:20160216:105644.157 process_rule() ip:'10.0.0.2'
Assertion 'nl->fd > 0' failed at src/libsystemd/sd-netlink/netlink-socket.c:55, function broadcast_groups_get(). Aborting.
If I disable the discovery, it doesn't help, because he still trying to run a discovery. I need to disable completely the discovererer instances on the proxy configuration, then he is able to load.
I tested the problem on the server and the same occurs, if I enable a simple discovery , he simple dies on the same error.
Anyone seen anything similar?
I just saw the notice the Zabbix 3.0.0 LTS was released and I was already running the Alpha2 version, so I just went quickly and updated on my test environment to see how it goes.
The test environment consists in a small hardware machine as zabbix server, an openstack instance serving as zabbix proxy, and several agents on hardware and virtuals.
I run a discovery process on the proxy instance, to search for other openstack machines on a certain network, if a discoverer child start, he instantly kills the whole proxy, the error I see when Debug=4 is:
9087:20160216:105644.157 process_rule() ip:'10.0.0.2'
Assertion 'nl->fd > 0' failed at src/libsystemd/sd-netlink/netlink-socket.c:55, function broadcast_groups_get(). Aborting.
If I disable the discovery, it doesn't help, because he still trying to run a discovery. I need to disable completely the discovererer instances on the proxy configuration, then he is able to load.
I tested the problem on the server and the same occurs, if I enable a simple discovery , he simple dies on the same error.
Anyone seen anything similar?
Comment