-----Original Message----- From: Marc Powell [mailto:[email protected]] Sent: Monday, June 01, 2009 6:40 PM To: Nagios Users Mailinglist Subject: Re: [Nagios-users] Trouble with check_nrpe+check_hpasm
On Jun 1, 2009, at 4:45 PM, <[email protected]> <[email protected] > wrote: > > I am monitoring system named locsys from NAGIOS server named Nagios. > > I can get check_hpasm to work locally on the system being monitored > (locsys) but I am unable to get check_hpasm to work with check_nrpe > when monitored through NAGIOS server. Other monitoring commands work > fine with check_nrpe with the same combination. Here are some > command outputs to provide a better understanding. > > [r...@locsys ~]# /usr/local/nagios/libexec/check_hpasm > OK - System: 'proliant dl360 g3', S/N: 'xxxxxx', ROM: 'P31 > 09/15/2004', hardware working fine, da: 1 logical drives, 2 physical > drives Does this work as the user NRPE runs as? You should never test nagios- related tasks as root. Permission differences will lead you down wrong paths and waste a lot of time. > Any clues would be appreciated. http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf - Troubleshooting section. If the first part doesn't help, NRPE's debug mode may. -- Marc Thanks for your suggestion. I was able to get it fixed. Check_hpasm plugin needs to be run with root privileges. So, on locsys, 1. I had to allow the user NRPE runs as (xyzuser), privileges to the command /usr/local/nagios/libexec/check_hpasm in /etc/sudoers xyzuser ALL=NOPASSWD:/sbin/hpasmcli,/usr/local/nagios/libexec/check_hpasm (Note that check_hpasm documentation already mentions giving sudo access to nrpe user for /sbin/hpasmcli). and 2. Define the check_hpasm command in nrpe.cfg prefixed with sudo as follows: command[check_hpasm]=sudo /usr/local/nagios/libexec/check_hpasm Regards, Charan ------------------------------------------------------------------------ ------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Nagios-users mailing list [email protected] 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 This email is intended only for the named person or entity to which it is addressed and contains valuable business information that is proprietary, privileged, confidential and/or otherwise protected from disclosure. Dissemination, distribution or copying of this email or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this email by mistake, please delete it from your system immediately and notify the sender. Email transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Nagios-users mailing list [email protected] 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
