[Nagiosplug-help] Install NRPE on Solaris

[cesar pacheco]

Hi Stevens,				

Great, you're a genius. It works perfectly. You saved my life.

I changed the file /etc/inetd.conf as you said, restarted the inetd daemon and ...

#/usr/local/nagios/libexec/check_nrpe -n -H localhost
NRPE v2.8

Thanks a lot for your help.




- cesar pacheco (cpachecofer)

-----------------------
This thread is located in the archive at this URL:
http://www.nagiosexchange.org/nagiosplug-help.32.0.html?&tx_maillisttofaq_pi1[showUid]=8881
					
> I think you've missed a field in your inetd.conf.  It should be:
> 
> nrpe    stream  tcp     nowait  nagios /usr/local/nagios/bin/nrpe \
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -i
> 
> Note the second instance of /usr/local/nagios/bin/nrpe.
> 
> --
> Mike
> 
> > -----Original Message-----
> > From: nagiosplug-help-bounces at lists.sourceforge.net
> [mailto:nagiosplug-
> > help-bounces at lists.sourceforge.net] On Behalf Of cesar pacheco
> > Sent: Tuesday, January 29, 2008 5:51 AM
> > To: nagiosplug-help at lists.sourceforge.net; cpachecofer at gmail.com
> > Subject: [Nagiosplug-help] Install NRPE on Solaris
> >
> > Hi list
> >
> > I'm trying to install NRPE daemon on Sun Solaris 9, following NRPE.pdf
> > instructions.
> >
> > I'm using Solaris9 as remote host. I've installed
> nagios-plugins-1.4.6,
> > and nrpe-2.8 with next commands:
> >
> > #cd /tmp/downloads/nrpe-2.8
> > #./configure --disable-ssl (Since I haven't Open SSL installed on my
> > machine)
> > make all
> > #make install-plugin
> > #make install-daemon
> > #make install-daemon-config
> >
> > Next, I edited my /etc/inetd.conf file and added ..
> > nrpe    stream  tcp     nowait  nagios /usr/local/nagios/bin/nrpe -c
> > /usr/local/nagios/etc/nrpe.cfg -i
> >
> > Next, I edited /etc/services file, adding ...
> > nrpe            5666/tcp                        # NRPE
> >
> > Afterwards, I restart inetd
> > #pkill -HUP inetd
> >
> > And I test the nrpe service state:
> > #netstat -a | grep nrpe
> >  *.nrpe               *.*                0      0 49152      0 LISTEN
> >
> > Everything seems working perfectly, but when I check the deamon ...
> > #/usr/loca/nagios/libexec/check_nrpe -n -H localhost
> >
> > I get ...
> > CHECK_NRPE: Received 0 bytes from daemon.  Check the remote server
> logs
> > for error messages.
> >
> > My log says ...
> > Jan 29 15:00:14 host1 nrpe[15449]: [ID 301881 daemon.error] Unable to
> open
> > config file '//nrpe.cfg' for reading
> > Jan 29 15:00:14 host1 nrpe[15449]: [ID 576867 daemon.error] Config
> file
> > '//nrpe.cfg' contained errors, aborting...
> >
> > These are nrpe.cfg permissions:
> > #ls -l etc/nrpe.cfg
> > -rw-r--r--   1 nagios   nagios      7102 Jan 29 14:41 etc/nrpe.cfg
> >
> > Any idea?
> >
> >
> > Thanks in advance.
> >
> >
> > - cesar pacheco (cpachecofer)
> >
> > -----------------------
> > The mailing list archive is found here:
> > http://www.nagiosexchange.org/nagiosplug-help.32.0.html
> >
> >
> >
> ------------------------------------------------------------------------
> -
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Nagiosplug-help mailing list
> > Nagiosplug-help at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> > ::: Please include plugins version (-v) and OS when reporting any
> issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>