Bug 825467

Summary:	systemd fails to start named daemon due to error in PIDFile parameter in /usr/lib/system.d/system/named.service
Product:	[Fedora] Fedora	Reporter:	Sandro <gui1ty>
Component:	bind	Assignee:	Adam Tkac <atkac>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	atkac, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-01 14:53:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro 2012-05-26 16:45:56 UTC

Description of problem:

The named daemon fails to start with error message in /var/log/messages:

systemd[1]: PID file /run/named/named.pid not readable (yet?) after start.
systemd[1]: named.service operation timed out. Terminating.

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

bind-9.9.0-4.fc17.x86_64
systemd-44-12.fc17.x86_64

How reproducible:

always

Steps to Reproduce:
1. systemctl start|restart named.service
2.
3.
  
Actual results:

Named cannot be started using systemd. It runs well when started in a console using 'named -fg'.

Expected results:

systemd succeeds starting named

Additional info:

In /usr/lib/systemd/system/named.service (provided by bind package) there is a parameter 'PIDFile' that is set to '/run/named/named.pid'. When changed to '/var/run/named/named.pid' named can be started using systemctl after running 'systemctl --system daemon-reload'.

Comment 1 Adam Tkac 2012-06-01 14:53:22 UTC


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