Red Hat Bugzilla – Bug 178300
bind-chroot does not update /etc/sysconfig/named during %post
Last modified: 2007-11-30 17:07:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7
Description of problem:
When I removed bind-chroot RPM, the server failed to restart. There was nothing in the logs, so I needed to dig around.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install all bind-related packages
2.Remove bind-chroot rpm
3. Try restarting bind (additional step)
Actual Results: After step #2, /etc/sysconfig/named still had ROOTDIR=/var/named/chroot, which prevented named to restart. When I manually commented that line, bind successfully restarted.
Expected Results: ROOTDIR line in /etc/sysconfig/named needs to be removed after the uninstallation of bind-chroot packages.
Yes, this problem has already been fixed, both with the latest bind RHEL-4
update release candidate, bind-9.2.4-16.EL4, available from:
and with bind-9.3.2 for RHEL-4, available from:
Hopefully, a new bind release will be in the next RHEL-4 update release that
will fix this problem.
No one has suggested re-basing bind to fix this bug.
Changing Dev NAK to Dev ACK.
This issue is on Red Hat Engineering's list of planned work items
for the upcoming Red Hat Enterprise Linux 4.4 release. Engineering
resources have been assigned and barring unforeseen circumstances, Red
Hat intends to include this item in the 4.4 release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.