Bug 45484 - named not OK with broken /etc/named.conf
Summary: named not OK with broken /etc/named.conf
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-21 22:30 UTC by Stacy Pennington
Modified: 2007-04-18 16:33 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-06-21 22:31:02 UTC


Attachments (Terms of Use)

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.


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