Bug 455564

Summary: named init script doesn't wait for server terminaton
Product: Red Hat Enterprise Linux 5 Reporter: Adam Tkac <atkac>
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 5.0CC: ovasik
Target Milestone: rcKeywords: EasyFix
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-14 10:00:22 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:
Bug Depends On: 455540    
Bug Blocks:    

Description Adam Tkac 2008-07-16 08:53:28 UTC 
+++ This bug was initially created as a clone of Bug #455540 +++

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.

-- Additional comment from atkac on 2008-07-16 04:52 EST --
Right you are. Thanks for your report
Comment 2 Adam Tkac 2008-08-14 10:00:22 UTC 
Hm, after inspection this bug affects only RHEL4 systems. RHEL5 initscript is already sane. Closing