Bug 455564 - named init script doesn't wait for server terminaton
named init script doesn't wait for server terminaton
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: bind (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Adam Tkac
: EasyFix
Depends On: 455540
  Show dependency treegraph
Reported: 2008-07-16 04:53 EDT by Adam Tkac
Modified: 2013-04-30 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-14 06:00:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Tkac 2008-07-16 04:53:28 EDT
+++ 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):


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:

>               while pidofproc named >/dev/null 2>&1; do
>                       sleep 1
>               done
< # wait a couple of seconds for the named to finish closing down
<       sleep 2

...resolves the issue.

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

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