Bug 999753

Summary:	systemd files need After=network.target
Product:	[Fedora] Fedora	Reporter:	Jay Fenlason <fenlason>
Component:	ndjbdns	Assignee:	pjp <pj.pandit>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	jfeeney, negativo17, pj.pandit
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ndjbdns-1.05.8-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-11 01:58:14 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 Jay Fenlason 2013-08-22 03:48:53 UTC

Description of problem:
Because the systemd files lack an After= line, systemd attempts to start the services at the same time as the network.  Because dnscache and tinydns are small, they usually start before NetworkManager has had a chance to configure the interfaces, so they fail to start.

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


How reproducible:
Usually.  Sometimes NetworkManager initializes the interfaces before the djbdns servers start, but usually tinydns and/or dnscache start when their interfaces are not initialized and fail to bind to them.

Steps to Reproduce:
1.
2.
3.

Actual results:
dnscache and/or tinydns enter FAILED state and are not running.

Expected results:
dnscache and tinydns running and servicing DNS requests.

Additional info:

Comment 1 pjp 2013-08-22 05:04:55 UTC

Thanks so much for reporting this bug Jay, I'll fix this in the upcoming release soon.

Thank you. :)

Comment 2 pjp 2013-08-24 10:44:46 UTC

This has been fixed.

- https://github.com/pjps/ndjbdns/commit/f6dc90335d34edb7da2199f94c05d124e0ded44e

Comment 3 Fedora Update System 2013-09-02 09:39:34 UTC

ndjbdns-1.05.8-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ndjbdns-1.05.8-1.fc18

Comment 4 Fedora Update System 2013-09-02 09:40:05 UTC

ndjbdns-1.05.8-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ndjbdns-1.05.8-1.fc19

Comment 5 Fedora Update System 2013-09-02 23:28:33 UTC

Package ndjbdns-1.05.8-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ndjbdns-1.05.8-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15656/ndjbdns-1.05.8-1.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-09-06 13:42:49 UTC

ndjbdns-1.05.8-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/ndjbdns-1.05.8-1.el6

Comment 7 Fedora Update System 2013-09-06 13:43:50 UTC

ndjbdns-1.05.8-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/ndjbdns-1.05.8-1.el5

Comment 8 Fedora Update System 2013-09-11 01:58:14 UTC

ndjbdns-1.05.8-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-09-11 01:58:43 UTC

ndjbdns-1.05.8-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2013-09-23 18:11:13 UTC

ndjbdns-1.05.8-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2013-09-23 18:12:11 UTC

ndjbdns-1.05.8-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.