problem with check_yum

Seth Simmons ssimmons at cymfony.com
Wed Apr 15 18:09:46 CEST 2009


Thanks
This version is more verbose and has more options available; I'll see how this works.


-----Original Message-----
From: Hari Sekhon [mailto:hpsekhon at googlemail.com] 
Sent: Wednesday, April 15, 2009 9:56 AM
To: Seth Simmons
Cc: Nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] problem with check_yum

Seth Simmons wrote:
>
> I’m running nagios 3.0.6 and using check_yum on my red hat/centos boxes.
>
> Today I’ve had all my centos boxes show yum warnings about needed 
> updates; found out centos 5.3 was released.
>
> I have one red hat 5.2 box. The problem is, check_yum within nagios 
> shows ‘o/s is up to date’ as of last check (10 min ago).
>
> If I run it manually from the machine, it gives a warning that updates 
> are needed (verified through yum and rhn).
>
> How can nagios be reporting that yum is ok when it isn’t?
>
Fyi, see

http://www.nagiosexchange.org/cgi-bin/page.cgi?g=Detailed%2F2577.html;d=1

for a better check_yum plugin. I wrote it, the one you are using really 
was too primitive I thought...

I've not seen this behaviour with this plugin, but it gives better 
visibility on how many updates, whether they are security or just 
regular non-critical updates etc...
There is also a note about update check reliability when running as a 
non root user.

-h

-- 
Hari Sekhon
Always open to interesting opportunities
http://www.linkedin.com/in/harisekhon

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null


More information about the Users mailing list