[Bug 1126890] Re: nrpe removes its PID when scanned by nmap

[Jamon Camisso]

This bug breaks monitoring for me on over 30 production 12.04 servers.
The patch should be reviewed for SRU inclusion since nagios3 (in main)
and icinga (universe) are both affected by it. It requires manual
intervention to bring the service back on each individual host, so this
patch is fairly important to have back ported.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1126890

Title:
  nrpe removes its PID when scanned by nmap

Status in “nagios-nrpe” package in Ubuntu:
  Confirmed

Bug description:
  During a nmap scan, NRPE logs this error and removes its PID :

  Feb 15 22:35:05 pm nrpe[2917]: Error: Network server getpeername() failure (107: Transport endpoint is not connected)
  Feb 15 22:35:05 pm nrpe[2917]: Daemon shutdown

  Despite what it logs, the daemon is still running but since the PID
  file is gone, the init script stop working:

  # ps aux| grep nrpe
  nagios    2908  0.0  0.3  25344  1144 ?        Ss   22:34   0:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d

  # /etc/init.d/nagios-nrpe-server status
   * nagios-nrpe is not running

  Scanning the NRPE port again with nmap further confirms the PID
  removal behaviour (the PID logged is incremented too?):

  Feb 15 22:36:19 pm nrpe[2922]: Error: Network server getpeername() failure (107: Transport endpoint is not connected)
  Feb 15 22:36:19 pm nrpe[2922]: Cannot remove pidfile '/var/run/nagios/nrpe.pid' - check your privileges.
  Feb 15 22:36:19 pm nrpe[2922]: Daemon shutdown

  # ps aux| grep nrpe
  nagios    2908  0.0  0.3  25344  1144 ?        Ss   22:34   0:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d

  This problematic behaviour was confirmed on Lucid, Precise, Quantal
  and Raring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1126890/+subscriptions