[Samba4] Named reload causes DLZ shutdown

[Brian C. Huffman]

Amitay,

I applied both patches related to bind9 (named reload and talloc).

Named no longer appears to crash, but is it correct that I still see the 
dlz shutdown at the end of the reload?
May 23 15:29:22 samba01 named[3737]: reloading configuration succeeded
May 23 15:29:22 samba01 named[3737]: reloading zones succeeded
May 23 15:29:22 samba01 named[3737]: samba_dlz: shutting down

Thanks,
Brian

On 05/22/2012 09:59 PM, Amitay Isaacs wrote:
> Hi Brian,
>
> On Tue, May 22, 2012 at 1:18 AM, Brian C. Huffman
> <bhuffman at etinternational.com>  wrote:
>> I've seen this a few times, and it seems to be repeatable.  If I do a named
>> reload, it causes DLZ for samba to shut down, and shortly afterwards named
>> itself dies:
>>
>> [root at samba01 cron.daily]# /sbin/service named reload
>> Reloading named:                                           [  OK  ]
>> [root at samba01 cron.daily]# tail -21 /var/log/messages
>> May 21 11:14:01 samba01 named[17989]: received control channel command
>> 'reload'
>> May 21 11:14:01 samba01 named[17989]: loading configuration from
>> '/etc/named.conf'
>> May 21 11:14:01 samba01 named[17989]: reading built-in trusted keys from
>> file '/etc/named.iscdlv.key'
>> May 21 11:14:01 samba01 named[17989]: using default UDP/IPv4 port range:
>> [1024, 65535]
>> May 21 11:14:01 samba01 named[17989]: using default UDP/IPv6 port range:
>> [1024, 65535]
>> May 21 11:14:01 samba01 named[17989]: no IPv6 interfaces found
>> May 21 11:14:01 samba01 named[17989]: sizing zone task pool based on 6 zones
>> May 21 11:14:01 samba01 named[17989]: Loading 'AD DNS Zone' using driver
>> dlopen
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: started for DN
>> DC=xmen,DC=eti
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: starting configure
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: configured writeable zone
>> '15.168.192.in-addr.arpa'
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: configured writeable zone
>> 'xmen.eti'
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: configured writeable zone
>> '_msdcs.xmen.eti'
>> May 21 11:14:01 samba01 named[17989]: using built-in DLV key for view
>> _default
>> May 21 11:14:01 samba01 named[17989]: Warning:
>> 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty
>> zones
>> May 21 11:14:01 samba01 named[17989]: zone 15.168.192.in-addr.arpa/NONE:
>> (other) removed
>> May 21 11:14:01 samba01 named[17989]: zone xmen.eti/NONE: (other) removed
>> May 21 11:14:01 samba01 named[17989]: zone _msdcs.xmen.eti/NONE: (other)
>> removed
>> May 21 11:14:01 samba01 named[17989]: reloading configuration succeeded
>> May 21 11:14:01 samba01 named[17989]: reloading zones succeeded
>> May 21 11:14:01 samba01 named[17989]: samba_dlz: shutting down
>>
>> Any ideas why this might happen?
> Named crash was caused by incorrectly freeing the state information in
> DLZ_BIND9 module. The patches to fix this error are in my dns-wip
> branch.
>
>     http://git.samba.org/?p=amitay/samba.git;a=shortlog;h=refs/heads/dns-wip
>
> Please let me know if the patch fixes the named crash.
>
> Amitay.
>