Description of problem: It looks like this is was likely addressed in bug 426382, however there is no fix incorporated into RH 4 (and presumably 5, though I have not verified). If named is stopped via rndc, it won't exit immediately and as such the 'start' of a 'restart' will be attempted before the prior instance had completed shutdown. Version-Release number of selected component (if applicable): bind-9.2.4-28.0.1.el4 How reproducible: Get a reasonably loaded bind instance going (~200mb of heap in this case) and execute a restart via the stock init script. Most of the time the start will fail due to the daemon still exiting. A fix as trivial as: 128a129,131 > while pidofproc named >/dev/null 2>&1; do > sleep 1 > done 158,159d160 < # wait a couple of seconds for the named to finish closing down < sleep 2 ...resolves the issue.
Right you are. Thanks for your report
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
re comment 2 -- Applying RHSA-2009:0020 resulted in yet another service outage due to this bug. Could Red Hat Product Management perhaps re-consider the implications of this 3 line patch?
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * the named init script did not wait for proper named termination before attempting to restart named, which, when the name server was under moderate or high load, could have caused a failure to start. With this update, the named init script waits for named termination before attempting to restart the name server.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -* the named init script did not wait for proper named termination before attempting to restart named, which, when the name server was under moderate or high load, could have caused a failure to start. With this update, the named init script waits for named termination before attempting to restart the name server.+The named init script did not wait for proper named termination before attempting to restart named, which, when the name server was under moderate or high load, could have caused a failure to start. With this update, the named init script waits for named termination before attempting to restart the name server.
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 therefore 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. http://rhn.redhat.com/errata/RHBA-2011-0223.html