check_oracle fails executing with nrpe

[Daniel Bareiro]

On Monday, 03 December 2007 15:22:03 -0600,
Marc Powell wrote:

> > I've some problems executing check_oracle plugin via check_nrpe.
 
> > In the Oracle server:
 
> > sdptest:/usr/local/nagios/etc# cat /usr/local/nagios/etc/nrpe.cfg | \
> > grep check_sysaux
> > command[check_sysaux]=/usr/local/nagios/libexec/check_oracle
> > --tablespace xxxxx yyyyy zzzzz SYSAUX 90 80

> > sdptest:/usr/local/nagios/etc# /usr/local/nagios/libexec/check_oracle \
> > --tablespace xxxxx yyyyy zzzzz SYSAUX 90 80
 
> > xxxxx : SYSAUX OK - 40.50% used [ 476 / 800 MB available
> > ]|SYSAUX=40.50%;80;90;0;100

> > Any idea to resolve this issue?
 
> Yes, try running the above test as the user that NRPE runs as. It's
> almost certainly not root and doesn't have root environment or privs.

NRPE run as nagios user. Since it hasn't a valid shell I can't try the
above test with this user. I put the nagios user in oinstall group and
check_oracle via check_nrpe works!

Thanks for your response, Marc.

Regards,
Daniel
-- 
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Etch - Linux user #188.598
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071208/b1423386/attachment.sig>
-------------- next part --------------
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
-------------- next part --------------
_______________________________________________
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