CentOS 5 (and RHEL) RPMs for Zabbix 1.8

[Farley]

Updated Jan 8, 2010: Fixed all problems everyone has complained about here, and in my blog. In summary: Added zabbix-proxy support, fixed 64-bit missing repodata, fixed file permissions, fixed problem with upgrading the package (thanks Tim!) added curl support (web scenarios work now, yay!).

Hey guys!

I built a spec file and RPMs for Zabbix 1.8 for CentOS and I'm hosting a repository for them for anyone to use. This might simplify some people's installation, especially on tons of servers (I manage lots of servers, installing anything via anything except RPMs is not scalable).

For instructions on how to perform this install, simply add my repository, and then install yum install zabbix-agent (or server).

Details are here: http://andrewfarley.com/sysadmin/rpm-repository-online

NOTE: If you have problems installing zabbix-web, please visit: http://www.zabbix.com/forum/showpost...36&postcount=7

Your feedback and input is welcome. And any recommended changes to my specfile are welcome also, preferably in the form of a patch, but if you're not a nerd just let me know and I can revise it.

Cheers!

[ericgearhart]

I've got the zabbix and zabbix-agent RPMa installed on several CentOS 5.4 and RHEL 5.4 64-bit boxes at work and they're working great.

I'm going to setup an rpmbuild VM and roll my own RPMs using your spec file as well, so they already have their config files pre-built.

The only thing I noticed wrong with the RPMs was permission issues... I had to by hand 'chown zabbix:zabbix /etc/zabbix' and '/var/log/zabbix-agent'

Other than they they've been working great

[Farley]

Ahh good catch...

I'll post a update to the spec and RPM file over the next few days, I have to finish a project but good catch.

Cheers!

[ericgearhart]

Here's another small suggestion: add theZabbix ports to /etc/services. The lack of Zabbix services being registered in /etc/services won't break anything, it's more just being a perfectionist.

Now that I think of it, I guess you should do this in the zabbix-agent rpm, becuase servers that have the agents installed on them should have the Zabbix ports documented in /etc/services as well...

Setting up /etc/services is outlined in the installation guide (here) (under Section 2.4.3, Step 6 "Configure /etc/services")

Step 6

Configure /etc/services

The step is optional. However, it is recommended. 
On the client (monitored) machines, add the following lines to /etc/services:

zabbix-agent    10050/tcp  Zabbix Agent
zabbix-agent    10050/udp  Zabbix Agent
zabbix-trapper  10051/tcp  Zabbix Trapper
zabbix-trapper  10051/udp  Zabbix Trapper 

Note that the port numbers are offical Zabbix ports registered in IANA.

[raddy]

Hello Everybody

Farley Zabbix rpms appears to be missing libcurl support.
That is the reason for Web Monitoring function to stop working.

I hope Farley will roll-out new RPMs after updating the spec file.

[krimson]

I thought this is a cookbook i can download

Nuke this guy, he's a spammer.

[Farley]

RPMs updated!

I've got the zabbix and zabbix-agent RPMa installed on several CentOS 5.4 and RHEL 5.4 64-bit boxes at work and they're working great.

I'm going to setup an rpmbuild VM and roll my own RPMs using your spec file as well, so they already have their config files pre-built.

The only thing I noticed wrong with the RPMs was permission issues... I had to by hand 'chown zabbix:zabbix /etc/zabbix' and '/var/log/zabbix-agent'

Other than they they've been working great

The latest version of my RPMs have fixed the permissions. Feel free to check 'em out!

Hello Everybody

Farley Zabbix rpms appears to be missing libcurl support.
That is the reason for Web Monitoring function to stop working.

I hope Farley will roll-out new RPMs after updating the spec file.

Raddy, the latest version of my RPMs have libcurl support. Check 'em up! Should just have to yum update and then yum upgrade and grab the latest revision of the package to fix this up for you!

I also added a patch from Tom which fixes some upgrade problems, fixed some permission problems, fixed 64-bit yum (was missing the repodata!), fixed build requirements, AND added a new RPM for zabbix proxy support. So, all in all it's looking great. Again, your feedback is always welcome!

Cheers guys!

[ericgearhart]

OpenSUSE build service

I threw the spec file and tarball onto the OpenSUSE build service for CentOS and RHEL, and the rpms were built successfully!

CentOS i586 didn't build, but RHEL i586 DID build, which is weird... but anyway here is the URL: http://download.opensuse.org/reposit...rhart:/zabbix/

[Farley]

I threw the spec file and tarball onto the OpenSUSE build service for CentOS and RHEL, and the rpms were built successfully!

CentOS i586 didn't build, but RHEL i586 DID build, which is weird... but anyway here is the URL: http://download.opensuse.org/reposit...rhart:/zabbix/

Awesome, if you don't mind I'm going to add your builds to my repository (with a mention to you of course). Could you tell me what you saw wrong with the CentOS build? What version of CentOS? I'm using 5.4 and I built them without problems on 32 and 64-bit.

When did you grab my spec file by the way? I updated it about a week and a half ago when I updated my RPMs, there were some build dependencies missing.

Let me know if you can help me narrow down the problem, so I can fix it.

Cheers!

[ericgearhart]

Awesome, if you don't mind I'm going to add your builds to my repository (with a mention to you of course). Could you tell me what you saw wrong with the CentOS build? What version of CentOS? I'm using 5.4 and I built them without problems on 32 and 64-bit.

When did you grab my spec file by the way? I updated it about a week and a half ago when I updated my RPMs, there were some build dependencies missing.

Let me know if you can help me narrow down the problem, so I can fix it.

Cheers!

OK ignore what I said about CentOS i586 not building... when I went into the build log, it looks like the OpenSUSE build service hit a snag when it tried to setup the virtual machine the CentOS package was being built in.

I forced it to try building again, and it was successful! There wasn't a problem with your spec, it was just the build service being wonky

So here are the packages:
CentOS:

http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/CentOS_5/i386/

http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/CentOS_5/x86_64/

RHEL 5:

http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/RHEL_5/i386/

http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/RHEL_5/x86_64/

Open source collaboration is cool

[ericgearhart]

Automatically generated repo files

I have to test this, but I think you can setup yum repos really easily with the buildservice as well

e.g. for CentOS:

cd /etc/yum.repos.d
wget http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/CentOS_5/home:ericgearhart:zabbix.repo

for RHEL:

cd /etc/yum.repos.d
wget http://download.opensuse.org/repositories/home:/ericgearhart:/zabbix/RHEL_5/home:ericgearhart:zabbix.repo

... should be all you have to do to setup the repo. That will setup automatic dependency handling, updates in the future, etc etc

[hogeloarienna]

CentOS 5 and RHEL RPMs for Zabbix 1 8

I would love to have the configuration or documentation on how to do it.

I am trying to setup zabbix on two separate sites that replicate to one another and each site has a T1 connected to the internet and a VPN establishes the traffic between the two systems.

One question though, when you setup and agents on the servers, to which zabbix server do you point and how does the agent handle the failover to the other server?

Regards,

Paul

[Farley]

I would love to have the configuration or documentation on how to do it.

I am trying to setup zabbix on two separate sites that replicate to one another and each site has a T1 connected to the internet and a VPN establishes the traffic between the two systems.

One question though, when you setup and agents on the servers, to which zabbix server do you point and how does the agent handle the failover to the other server?

Regards,

Paul

Hey Paul,

That question is really out of the scope of this post, but I'll try to help anyway. I recommend in the future asking it elsewhere, as this is the "cookbook" thread where we share working solutions, monitors, etc. Not asking technical questions.

ANYWAY, you have to setup your own Zabbix servers, one at each site. Preferably all items at that site would get logged and monitored locally. Regarding how to do failover or clustering though, I have not had the need to do this, or tried. So I'm not exactly sure. Most things are in the manual, but I agree I don't see a clear straightforward way for an agent to specify a failover server IP. Maybe another expert can help, but again it might not be seen in this forum, you might want to redirect your question to the appropriate forum.

Cheers!

[ericgearhart]

Zabbix 1.8.1 RPMs

I've updated the buildservice repository I previously built Zabbix 1.8 on to Zabbix 1.8.1 using Andrew Farley's specfile (originally available here)

CentOS 5
32 bit: http://download.opensuse.org/reposit...CentOS_5/i386/
64 bit: http://download.opensuse.org/reposit...ntOS_5/x86_64/

RHEL 5
32 bit: http://download.opensuse.org/reposit...x/RHEL_5/i386/
64 bit: http://download.opensuse.org/reposit...RHEL_5/x86_64/

[tpoder]

RPM on rpmfore

Hi,
thanks for yours RPM. Do you thinking about publishing you rpm through Dag Weirs RPMforge site (http://dag.wieers.com/rpm/)? It could be a nice to have zabbix in the repository like that. If you would agree with that I can ask for adding it.

You have written in specfile that you are planning support for PgSQL an Oracle. Maybe you can overtake some ideas from the rpm placed on http://hawk.cis.vutbr.cz/~tpoder/SW/...5.0/cis/SRPMS/ or http://hawk.cis.vutbr.cz/~tpoder/SW/.../5.0/cis/i386/ (compiled version) where the support for PgSQL has been already done. I am using this rpm (originally taken from EPEL repository http://cvs.fedora.redhat.com/viewvc/rpms/zabbix/devel/), but the process of updating EPEL sources is too slow and I have to update it by myself witch each release of zabbix :-(.

Thanks for nice piece of work.