Bug 45484

Summary:	named not OK with broken /etc/named.conf
Product:	[Retired] Red Hat Linux	Reporter:	Stacy Pennington <spenning>
Component:	bind	Assignee:	Bernhard Rosenkraenzer <bero>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	bugs.michael, karl
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-06-21 22:31:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stacy Pennington 2001-06-21 22:30:58 UTC

Description of Problem:
If an error exists in the /etc/named.conf file, running the "service named
start" command, causes an "OK" message for starting the service. In
actuality, the service is not started, so it is not "OK".

How Reproducible:
Always

Steps to Reproduce:
1. Stop named (type "service named stop" as root)
2. Open the previous working /etc/named.conf in an editor and add some
random text. Save the file.
3. Start named (type "service named start" as root)
You will see OK but the service is not running. The error is correctly
posted in /var/log/messages

Actual Results:
The service is not started when the user thinks it is started.

Expected Results:
The service should report back that it "Failed" letting the user know that
it is not running.

Additional Information:

Comment 1 Bernhard Rosenkraenzer 2001-07-19 10:40:24 UTC

The problem is that the named parent process returns 0 even if the config 
files are broken (because the config files are parsed later by the various 
child processes).
I've added a workaround to the startup scripts in 9.1.3-3.

Comment 2 Karl schmidt 2001-07-30 17:40:36 UTC

I can confir this bug

Comment 3 Charles Curley 2001-09-27 16:06:55 UTC

Perhaps users should use named-checkconf to test their configurations instead of
re-starting the server? I sure wish I'd known about it when I upgraded from bind
8 to 9.

Comment 4 Karl schmidt 2001-09-28 05:23:44 UTC

Yes both named-checkconf and named-checkzone are useful - but that is not the 
bug here - this bug most often shows up in linuxconf thinking that named is not 
running when it really is and tries to start a second copy.