Topic: New contrib : zabbix_agentd-1.6.2

[Fof]

I hope that could be useful for anybody.

I have just packaged the zabbix agent (deamon) which is similar as Nagios. Currently, it's not zabbix but just a piece of zabbix which is called the agent.

Wikipedia :
ZABBIX is a network management system application created by Alexei Vladishev. It is designed to monitor and track the status of various network services, servers, and other network hardware.

Binary :
http://www.deblogtoi.com/public/informatique/SME_Server/zabbix_agentd-1.6.2-3.i386.rpm

Source :
http://www.deblogtoi.com/public/informatique/SME_Server/zabbix_agentd-1.6.2-3.src.rpm

[Daniel B.]

Hi.

I'm actually working on the same developpement.

It's still young, that's why I haven't annouced it.

You can find both zabbix-server and zabbix-agent in my developpement repository:

http://repo.firewall-services.com/sme-testing/

(noarch directory for the integration package, i386 for zabbix packages and SRPMS for source RPMS)

Cheers

[jahlewis]

I'm very excited to hear this.  I was running 1.4 for a while, compiled from scratch, but since moving to new hardware, have not rebuilt it.  I'm especially interested in the proxy part of 1.6, which will allow zabbix to monitor multiple systems behind a remote firewall... similar to what nrpe does for Nagios.  I was just about to start compiling it all from scratch, but would much rather support your efforts by testing etc.

are they ready for us to test with? install everything but the proxy files on the host server? then the proxy files on a remote server? 

can we add your sme-testing as a repo so we can yum updates?  I'd be happy to help test etc.

[Daniel B.]

My testing repo can be configured for yum with:

Code: [Select]

db yum_repositories set fws-testing repository BaseURL http://repo.firewall-services.com/sme-testing EnableGroups no GPGCheck no Visible yes status disabled
signal-event yum-modify

But be aware that package here might not be stable. I sometime upload an update which can breack the packages.
For the proxy, you can find the base package in the repo, but I haven't started the integration one, I'll try to work on it when both server and agent are ok.

For the agent package, I'm working hard to add some UserParameters which I think are missing from the standard agent (like used memory, ups status, mysql stats, mails stats soon etc...). Just look at /etc/zabbix/zabbix_agentd.conf file to know which item you should add on the server.

last, here how-to install:
For the server part, you need php-bcmath extension. I don't know if it's available for php4, so I've updated my server to php5 of centosplus repo. You can follow this how-to for this part:

http://sme.firewall-services.com/spip.php?article64

Then, install the server:

Code: [Select]

yum --enablerepo=centosplus --enablerepo=fws-testing install smeserver-zabbix-server

For the agent:

Code: [Select]

yum --enablerepo=fws-testing install smeserver-zabbix-agent

And finish with a :

Code: [Select]

signal-event zabbix-agent-update
signal-event zabbix-server-update


[Fof]

hi VIP-ire,

I just had a look on your zabbix agent package and I have a question :

How do you raise the agent informations through your network from your agent to your zabbix server without to open the TCP port 10050 ?
Check your package and if there is an issue, look at my agent package in order to see my netfilter custom rule or you can contact me (in french if you wish)

Cheers.

[Daniel B.]

How do you raise the agent informations through your network from your agent to your zabbix server without to open the TCP port 10050 ?

I configure the agents to work in active mode, so they don't need to have port 10050 open, instead, they originate connexions to the server (and of course, the server must have port 10051 open)
Just look at zabbix documentation to see how active and passive mode works. With my integration package, you can enable one, the other or both mode with the keys active and passive. If you choose to use passive mode, you'll need to open the port from your zabbix server with something like:

Code: [Select]

db configuration setprop zabbix-agent passive enabled access public AllowHost w.x.y.z
signal-event zabbix-agent-update
signal-event remoteaccess-update
if w.x.y.z is your central zabbix server