Hi,
I'm starting a new thread to highlight the major problems with Zabbix v1.1.x running on FreeBSD. My goals are to bring this to a higher profile, but also to get any feedback from other users who are using Zabbix on FreeBSD.
The biggest problems are:
* v1.1.x zabbix_server: When there is a network error or a connection to a client host times out, the clients metrics all say [no data] - which is expected. The problem is that when the client host comes back, zabbix server never updates that the host is available, and so never starts monitoring it again. Furthermore, zabbix_server has the dead client listed as status: monitored and Availability: available the whole time regardless of whether the client is up and running, dead, or timing out for some reason.
The only way to make zabbix_server start monitoring the host again is to massage the database manually by doing this:
mysql -u root -D zabbix -e 'update hosts set errors_from=0'
- This means that if a host client goes into [no data] and then crashes, you will not recieve any alerts from Zabbix.
* v1.1.x zabbix_agentd will build without errors, but will not start. Stack tracing with truss or strace do not produce any output.
- I have had to use v1.1beta9+ agents on FreeBSD.
* v1.1.x zabbix_server builds without errors, but will not start if you are have debug=4 set. I have provided stack traces of this behavior and can again.
As a stab in the dark, I would consider migrating my zabbix_server to Linux if it looked like that would solve some of the server issues.
Let me state that I think Zabbix is an awesome monitoring platform, this post is not meant as a complaint. It's meant to be constructive and help solve these problems.
Also, before you say it, yes I realize it's open source, and yes I am presenting the option of purchasing commercial Zabbix support to my boss - and we may end up doing that.
Thanks for everyones time,
Daniel
I'm starting a new thread to highlight the major problems with Zabbix v1.1.x running on FreeBSD. My goals are to bring this to a higher profile, but also to get any feedback from other users who are using Zabbix on FreeBSD.
The biggest problems are:
* v1.1.x zabbix_server: When there is a network error or a connection to a client host times out, the clients metrics all say [no data] - which is expected. The problem is that when the client host comes back, zabbix server never updates that the host is available, and so never starts monitoring it again. Furthermore, zabbix_server has the dead client listed as status: monitored and Availability: available the whole time regardless of whether the client is up and running, dead, or timing out for some reason.
The only way to make zabbix_server start monitoring the host again is to massage the database manually by doing this:
mysql -u root -D zabbix -e 'update hosts set errors_from=0'
- This means that if a host client goes into [no data] and then crashes, you will not recieve any alerts from Zabbix.
* v1.1.x zabbix_agentd will build without errors, but will not start. Stack tracing with truss or strace do not produce any output.
- I have had to use v1.1beta9+ agents on FreeBSD.
* v1.1.x zabbix_server builds without errors, but will not start if you are have debug=4 set. I have provided stack traces of this behavior and can again.
As a stab in the dark, I would consider migrating my zabbix_server to Linux if it looked like that would solve some of the server issues.
Let me state that I think Zabbix is an awesome monitoring platform, this post is not meant as a complaint. It's meant to be constructive and help solve these problems.
Also, before you say it, yes I realize it's open source, and yes I am presenting the option of purchasing commercial Zabbix support to my boss - and we may end up doing that.
Thanks for everyones time,
Daniel


Comment