Bug 896702 - Does not start with systemd
Summary: Does not start with systemd
Keywords:
Status: CLOSED DUPLICATE of bug 860982
Alias: None
Product: Fedora
Classification: Fedora
Component: nrpe
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 19:41 UTC by Ben Webb
Modified: 2013-01-18 07:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-17 21:56:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ben Webb 2013-01-17 19:41:10 UTC
Description of problem:
The NRPE daemon in Fedora 18 does not start up automatically (with systemd).

Version-Release number of selected component (if applicable):
nrpe-2.13-1.fc18.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. yum install nrpe
2. systemctl start nrpe
  
Actual results:
systemctl reports:
Job for nrpe.service failed. See 'systemctl status nrpe.service' and 'journalctl -n' for details.

Expected results:
nrpe is started.

Additional info:
This is because /usr/lib/systemd/system/nrpe.service tries to start /usr/bin/nrpe, but nrpe is actually installed in /usr/sbin/. Correcting the path here fixes the problem for me.

Comment 1 Jose Pedro Oliveira 2013-01-17 21:56:36 UTC

*** This bug has been marked as a duplicate of bug 860982 ***

Comment 2 Mark Chappell 2013-01-18 07:19:44 UTC
Ben,

Package nrpe-2.13-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
Update it with:
# su -c 'yum update --enablerepo=updates-testing nrpe-2.13-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-0815/nrpe-2.13-2.fc18
then log in and leave karma (feedback).

If you can leave more positive karma then it'll go into stable with the next round of Fedora updates


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