Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1876454 - NRPE start bofore network is online
Summary: NRPE start bofore network is online
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nrpe
Version: epel7
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Martin Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-09-07 09:09 UTC by Uwe Müssel
Modified: 2020-09-23 16:35 UTC (History)
7 users (show)

Fixed In Version: nrpe-4.0.3-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-09-23 16:35:08 UTC
Type: Bug

Attachments (Terms of Use)

Description Uwe Müssel 2020-09-07 09:09:09 UTC
Description of problem:
NRPE starts after is reahced. When configured with bind ip, it may fail because of unconfigured ip.

Version-Release number of selected component (if applicable):
RHEL 7.8

How reproducible:
Problem depens on timeing at startup. So it cannot be reliably reproduced.

Steps to Reproduce:
1. Configure server_address in /etc/nagios/nrpe.conf
2. Reboot system

Actual results:
Sep  4 19:01:42 lterm2001 nrpe[925]: Starting up daemon
Sep  4 19:01:42 lterm2001 nrpe[925]: Bind to port 5666 on failed: Cannot assign requested address.

Expected results:
NRPE daemon should start without error

Additional info:
Systemd service file contains:
it should contain:

Comment 1 Martin Jackson 2020-09-07 16:10:31 UTC
Please try the build for EPEL7 at if you can and let me know if this fixes it.  Apparently the old config (Requaires= but not After= is racy).  If this works for you I'll update the branches and get this into the stable pipeline.

Comment 2 Uwe Müssel 2020-09-08 06:33:17 UTC
Hello Martin,

thanks for your quick reply. I've tested the new package. I seems to solve our problem:

$ systemd-analyze critical-chain  nrpe.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

nrpe.service @4.043s
└─ @4.041s
  └─ @4.038s
    └─NetworkManager.service @2.995s +121ms

Comment 3 Fedora Update System 2020-09-08 14:43:22 UTC
FEDORA-EPEL-2020-67a5e75fa9 has been submitted as an update to Fedora EPEL 7.

Comment 4 Fedora Update System 2020-09-09 14:42:55 UTC
FEDORA-EPEL-2020-67a5e75fa9 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 5 Fedora Update System 2020-09-23 16:35:08 UTC
FEDORA-EPEL-2020-67a5e75fa9 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.