Hi folks,
Still one day behind (jet lag from Paris, France)…
Anyway I am using Zabbix in production on FreeBSD Servers (6.3p7 -
6.4p1 - 7.0p7) since a couple of month… and I have a very precise
overview of what's working and what's broken.
The main problem with zabbix (server and client) is that the startup
script does not work correctly, in fact the process stays in memory
(shared memory) without beeing removed on "stop".
This can be easily seen using command such as these:
# /usr/local/etc/rc.d/zabbix_agentd start
# /usr/local/etc/rc.d/zabbix_agentd status
# /usr/local/etc/rc.d/zabbix_agentd stop
# /usr/local/etc/rc.d/zabbix_agentd status
This will quite obviously start and stop zabbix with a little check
between the two to see if everything is ok. The second status will
show no processes but if you try to start It again, well, It simply
won't!!
Took me a while to realize why, in fact the process is still loaded in
shared memory.
You can check that with this command:
# ipcs
Message Queues:
T ID KEY MODE OWNER GROUP
Shared Memory:
T ID KEY MODE OWNER GROUP
m 131073 2052509788 --rw-rw-rw- zabbix zabbix
Semaphores:
T ID KEY MODE OWNER GROUP
s 196611 2052509788 --rw-rw-rw- zabbix zabbix
To make a clean "stop" just issue these commands:
# ipcrm -S 2052509788
# ipcrm -M 2052509788
# ipcs
The numbers following the -S and -M have to be taken from the output
of the "ipcs" command. "ipcs" should show you no process at all now.
You will then be able to start It properly.
A bit of tuning then to increase the shared memory (generaly needed in
the first place)…
# sysctl -w kern.ipc.shmall=16384
This is the unfortunate way of running zabbix (client & server) on
FreeBSD.
Beside these startup / memory related problem, I have had no
particular problem with any aspect of the product… Tunning is needed
to suit your precise need, but this is done in a much easier way than
on any other products I have tested (including: Nagios, Hobbit)…
The details / analysis obtained with zabbix are quite impressive.
I would really love to see hobbit on PFSense…
I don't know if this will be corrected anytime soon, I have warned the
person in charge of the port, but so far nothing has been done (I am
unfortunately not good enough to dig in the code and correct these
problems)…
Sincerly yours.
Le 6 janv. 09 à 20:20, Gary Buckmaster a écrit :
Is there anyone here who is actually using Zabbix in production and
monitoring FreeBSD boxes with it? I know it looks like a shiny toy,
but I'm telling you that the reality is far less. The monitoring is
limited at best for linux, and almost completely unusable without
major customization for FreeBSD. I agree that having a nice
centralized monitoring system to use with pfSense would be nice, but
our extensive experience evaluating Zabbix led us to the conclusion
that it's not ready for prime time.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Gregober ---> PGP ID --> 0x1BA3C2FD
bsd @at@ todoo.biz
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
P "Please consider your environmental responsibility before printing
this e-mail"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
