nagios-nrpe (3.0.1-2) includes a systemd service file which should
resolve this issue.
** Changed in: nagios-nrpe (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: nagios-nrpe (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838437
Title:
nrpe server starts too early and fails to bind on IP
To manage not
Surprised to see the bug is so old. It only affects people who use
server_address directive. We have a Nagios server with ~30 clients
connected via OpenVPN and only recently started adding the
server_address directive to NRPE configs on clients. All of them will
fail to start NRPE on boot since nat
** Changed in: nagios-nrpe (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838437
Title:
nrpe server starts too early and fails to bind on IP
To manage notifica
** Bug watch added: Debian Bug tracker #665422
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665422
** Also affects: nagios-nrpe (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665422
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
This bug also affects Lucid and Precise and fix/workaround would be
greatly appreciated. Maybe converting the initscript to an upstart job
would avoid this race ?
** Summary changed:
- startup script reports success, but nrpe server fails to start
+ nrpe server starts too early and fails to bind
