Error while configuring NRPE on solaris

[Luc I. Suryo]

fyi

I have been using nagios and nrpe 9-10 years now; sparc and x86, started back with solaris 7
and now soalris 10, zero error.... mix solaris, aix, hpux, linux.
The server has always been Solaris (sparc or x86), use inetd/xinetd/deamon mode
again zero error

The one 'problem' i have seen people complain about is ssl and nrpe, read the manual and it should pretty
clear what todo, 99.9% is almost the use not having doing some RTFM thingy :)
The other one is tcp-wrapper and nrpe, nrpe has a access control buildt-in
so I never understood one would need to use tcp-wrapper :)

-ls


> 
> >From: N Patil
> >To: Eric Pearce
> >Cc: Nagios Users Mailinglist
> >Sent: Thursday, May 28, 2009 9:13 PM
> >Subject: Re: [Nagios-users] Error while configuring NRPE on solaris
> >
> >Thanks Eric,
> >I have followed the same article but it dint help. This problem is 
> >something which occured at the end, i mean while testing connectivity.
> >
> >Thanks,
> >Nilesh
> 
> >May 28 19:15:27 solaris10.remotehost.com inetd[24241]: [ID 702911 
> >daemon.error] Failed to set credentials for the inetd_start method of 
> > >instance svc:/network/nrpe/tcp:default (chdir: No such file or directory)
> 
> I'm just guessing, but do you have a home directory for the nagios user 
> (with owner and group set to nagios)?
> The "chdir" error might come from this.
> -e

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-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