Steve, Thanks for your response. I'm also puzzled as to why there's a /etc/init.d/nrpe, I believe it was installed when I installed binaries:
nagios-plugins-1.3.1_2-sol9-sparc-local and nrpe-1.9_5-sol9-sparc-local For now I ignore /etc/init.d/nrpe and edit /etc/inetd.conf to information that I found in README as well as to what you have described bellow. I also edited my path to point to all check_* and edited nrpe.cfg file accordingly, but I still get "CHECK_NRPE: Socket timeout after 10 seconds." from Nagios server and "daemon.error] Could not read request from client, bailing out..." from NRPE client. Executing #check_nrpe -H localhost Does work with the following output. NRPE v1.9 I've tried this on two Solaris9 boxes with the same results. Perhaps there is a problem with the built installation files that I'm installing. Thanks, Aleksey ----- Original Message ----- From: "Steve Shipway" <[EMAIL PROTECTED]> To: "'aleksey zakharov'" <[EMAIL PROTECTED]> Sent: Monday, March 06, 2006 8:46 PM Subject: RE: [Nagios-users] Cant get NRPE working on Solaris9 > > Modified /etc/init.d/nrpe to point to /etc/nrpe.cfg > > What? This doesn't sound right. You shouldn't have added anything in > /etc/init.d, but you should have a line added to your /etc/inetd.conf > similar to > > nrpe stream tcp nowait nobody /usr/local/nrpe/nrpe nrpe -i -c > /usr/local/nrpe/nrpe.cfg > > and then restart inetd. > > Steve > > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Nagios-users mailing list Nagios-users@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
