Bug 132866

 This is very strange - I've never seen this before, and we have 
 BIND installations here that run 24/7.

 Presumably you 'allow-update' to some zones and want to save
 the pending .jnl updates to the master zone files ? 
 If not, what is the reason you need to periodically restart named?
 
 Please download and install the latest bind-9.2.4rc8-14 .
 
 Please append further information to this bug:
    
 1. Turn on named tracing and gather debug data during restart:

 a. If you have selinux ENABLED and ENFORCING, run the command: 
       'setenforce 0',
    or 'setsebool named_write_master_zones 1'

 b. Enable core file generation:
    Edit /etc/profile :
    Comment out this line (@ line 28):
    '
    # ulimit -S -c 0 > /dev/null 2>&1 
    '
    and add this line:
    '
    ulimit -c unlimited 
    '

 c. Change the "service named restart" in your cron job to these
    commands:
    ' . /etc/sysconfig/named
      /bin/touch ${ROOTDIR}/var/named/named.run
      /bin/chown named:named ${ROOTDIR}/var/named/named.run
      /usr/sbin/rndc trace 99
      export OPTIONS='-d 99'
      bash -xf /etc/init.d/named restart  2>&1 \
           >> /tmp/named.init.dbg.`/bin/date '+%s'`.log 
      echo "/usr/sbin/rndc trace 0;                          \
            /usr/bin/gzip < ${ROOTDIR}/var/named/named.run > \
                  /tmp/named.dbg.\`/bin/date '+%s'\`.log.gz; \
            rm -f ${ROOTDIR}/var/named/named.run"   |        \
                  /usr/bin/at now+20min;                     \
    '

If the debug log shows named is still running 20 mins after restart,
but it still dies, remove the last 'echo ... | ... at ...;'  command;
tracing will then still be enabled when named exits ( a very large
debug file may be generated ). 

Then, the next day, if named is not running, please tar up the
resulting /tmp/named.dbg*.log.gz and any core files :
'
    . /etc/sysconfig/named
    gzip ${ROOTDIR}/var/named/core.[0-9]*
    tar -cpvf /tmp/named.dbg.tar /tmp/named/*.log.gz \    
         ${ROOTDIR}/var/named/core.*.gz
    rm -f ${ROOTDIR}/var/named/core.*.gz
'
and append the resulting  /tmp/named.dbg.tar to this bug.


 
    

I'm running bind 9.2.4 since September 24, 2004 and I'm not able to 
reproduce this problem, I had with 9.2.4rc7-12. I'll close this bug 
report and mark 9.2.4 as fix for it. But I'll feel free to reopen it, 
if I'm able to reproduce it (hopefully I'm not able to), again.

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.

http://rhn.redhat.com/errata/RHBA-2004-567.html