+++ This bug was initially created as a clone of Bug #457533 +++

Description of problem:
named crashes (process terminates) on incorrect usage of the rndc reload 
command


Version-Release number of selected component (if applicable):
[root@server /etc/yum.repos.d]# rpm -qa bind*
bind-utils-9.2.4-30.el4_8.4
bind-9.2.4-30.el4_8.4
bind-devel-9.2.4-30.el4_8.4
bind-libs-9.2.4-30.el4_8.4
[root@server /etc/yum.repos.d]# 


How reproducible:
every time

Steps to Reproduce:
Server A is the master of a dom.tld zone
Server B is a slave of the dom.tld zone

On server B type: rndc reload hostname.dom.tld
(the correct syntax would have been: rndc reload dom.tld)

The commandline now gives:
[root@yyyy ~]# rndc reload hostname.dom.tld
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of 
the command protocol, this host is not authorized to connect,
or the key is invalid.

The /var/log/messages log gives the following messages:
Aug  1 13:44:01 infiltrator named[8108]: view.c:1135: INSIST(result == 0 || 
result == 23) failed
Aug  1 13:44:01 infiltrator named[8108]: exiting (due to assertion failure)

After this the named process terminates.
 
Expected results:
Error messages from RNDC but no crashes of named

--- Additional comment from atkac on 2008-08-04 12:01:01 EDT ---

Right you are, thanks for report.

--- Additional comment from jsulman on 2008-12-05 11:24:37 EDT ---

I have verified this bug on Red Hat Enterprise Linux ES release 4 (Nahant Update 7), running bind-9.2.4-30.el4.

--- Additional comment from atkac on 2008-12-08 07:02:59 EDT ---

(In reply to comment #5)
> I have verified this bug on Red Hat Enterprise Linux ES release 4 (Nahant
> Update 7), running bind-9.2.4-30.el4.

Right you are. If you are interested in RHEL4 fix please clone this bug for RHEL4 ("Clone This Bug" in top right corner of this page)

--- Additional comment from errata-xmlrpc on 2009-01-20 17:16:39 EDT ---

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-2009-0246.html

--- Additional comment from atkac on 2009-03-11 06:25:23 EDT ---

*** Bug 489662 has been marked as a duplicate of this bug. ***