> > Not just /var/log/messages. Doesn't nrpe have a log file? Maybe even > secure. Hmmm I don't find any log specific to nrpe. In other words I don't see /var/log/nrpe.log or whatever. :) And when I tail -f /var/log/secure or /var/log/messages I don't see any entries turning up in them when I hit the client with check_nrpe. I was checking the logs on the client itself. > > >> Also nrpe needs to be told from where connections are allowed whether > >> running under an inetd or self-daemonized. > > > >Yep! I've set the only_from to have only the loopback address and the IP > >for the monitoring host in /etc/xinetd.d/npre. > > Not the xinetd config, the nrpe config (too). Hmmmm. but the nrpe.confg file is ignored in the case of allowed hosts. >From the nrpe config: # NOTE: This option is ignored if NRPE is running under either inetd or xinetd allowed_hosts=127.0.0.1 Thanks for the input tho, I genuinely appreciate it! On Sat, May 2, 2015 at 4:05 PM, Mark Milhollan <mlm at pixelgate.net> wrote: > On Sat, 2 May 2015, Tim Dunphy wrote: > > >>>It's only when checking from the monitoring host that nrpe fails: > >>Check /var/log/messages to see if xinetd says anything. > > > >I tailed /var/log/messages while hitting the client with check_nrpe from > >the monitoring host. However, that didn't cause an entry in the messages > >log. > > Not just /var/log/messages. Doesn't nrpe have a log file? Maybe even > secure. > > >> Also nrpe needs to be told from where connections are allowed whether > >> running under an inetd or self-daemonized. > > > >Yep! I've set the only_from to have only the loopback address and the IP > >for the monitoring host in /etc/xinetd.d/npre. > > Not the xinetd config, the nrpe config (too). > > > /mark > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B