search for: dlz_destroy

...e it is actually not "shutting down". Rather, samba_dlz, maintains a reference counted singleton of its state. What happens during reload is: 1) dlz_create is called. The refcount is upped, same internal instance returned to named and* nothing is logged.* 2) dlz_configure() is called. 3) dlz_destroy() is called. The refcount is decreased (from 2 to 1), nothing is destroyed, *but it incorrectly logs that it is shutting down!* Clearly, bind expects to start a new instance of its dlz, initialize it, and then destroy the old instance. I am hacking on this to figure out exactly where things fail...

To a user, samba_dlz just doesn't work correctly with bind. There are two obvious options a) bind is broken somehow and unloads all modules when reloading b) samba_dlz is somehow broken in the way that it interfaces with bind, perhaps it misinterprets the signal to 'reload' when it receives it from bind. As a user, i have no way of knowing which is it is, all that I know is that

Well, I had a cursory glance dlz_bind9.c and also the bind9 source code I could find ( http://users.isc.org/~each/doxygen/bind9/dlz__dlopen__driver_8c-source.html) and didn´t see any provision for 'reload' in there. bind is clearly calling the dlz_destroy() function and not dlz_create(), as one would expect, for a reload. So yes, it appears to be a shortcoming of bind. 1) I suggest that the wiki for AD DC be updated to point out this fact. logrotate scripts may use 'reload' which may be broken. a 'restart' is better in that case. 2)...

...tting down". > Rather, samba_dlz, maintains a reference counted singleton of its > state. What happens during reload is: > 1) dlz_create is called. The refcount is upped, same internal > instance returned to named and* nothing is logged.* > 2) dlz_configure() is called. > 3) dlz_destroy() is called. The refcount is decreased (from 2 to 1), > nothing is destroyed, *but it incorrectly logs that it is shutting > down!* > > Clearly, bind expects to start a new instance of its dlz, initialize > it, and then destroy the old instance. > Still not sure where the prob...

....org> wrote: > Well, I had a cursory glance dlz_bind9.c and also the bind9 source code I > could find ( > http://users.isc.org/~each/doxygen/bind9/dlz__dlopen__driver > _8c-source.html) > and didn´t see any provision for 'reload' in there. > bind is clearly calling the dlz_destroy() function and not dlz_create(), as > one would expect, for a reload. > So yes, it appears to be a shortcoming of bind. > 1) I suggest that the wiki for AD DC be updated to point out this fact. > logrotate scripts may use 'reload' which may be broken. a 'restart' is &gt...

...ther, samba_dlz, maintains a reference counted singleton of its > > state. What happens during reload is: > > 1) dlz_create is called. The refcount is upped, same internal > > instance returned to named and* nothing is logged.* > > 2) dlz_configure() is called. > > 3) dlz_destroy() is called. The refcount is decreased (from 2 to 1), > > nothing is destroyed, *but it incorrectly logs that it is shutting > > down!* > > > > Clearly, bind expects to start a new instance of its dlz, initialize > > it, and then destroy the old instance. > > &g...

Hai, Check the content of : /etc/logrotate.d/named If you see postrotate /etc/init.d/smbd reload > /dev/null endscript Change that to postrotate if [ -d /run/systemd/system ]; then; systemctl -q is-active named && systemctl reload named; else; /etc/init.d/named reload ; fi'; endscript Its something like that, so who pointing.. That does not matter, because this is OS

...17 11:34:35.317 general: managed-keys-zone: next key refresh: 12-Jan-2017 12:12:03.317 12-Jan-2017 11:34:35.317 general: zone_settimer: managed-keys-zone : enter 12-Jan-2017 11:34:35.317 general: automatic empty zone: 10.IN-ADDR.ARPA This is the destroy function used by bind9_dlz: _PUBLIC_ void dlz_destroy(void *dbdata) { struct dlz_bind9_data *state = talloc_get_type_abort(dbdata, struct dlz_bind9_data); state->log(ISC_LOG_INFO, "samba_dlz: shutting down"); dlz_bind9_state_ref_count--; if (dlz_bind9_state_ref_count == 0) { talloc_unlink(s...

...s-zone: next key refresh: > 12-Jan-2017 12:12:03.317 > 12-Jan-2017 11:34:35.317 general: zone_settimer: managed-keys-zone : enter > 12-Jan-2017 11:34:35.317 general: automatic empty zone: 10.IN-ADDR.ARPA > > This is the destroy function used by bind9_dlz: > > > _PUBLIC_ void dlz_destroy(void *dbdata) > { > struct dlz_bind9_data *state = talloc_get_type_abort(dbdata, > struct dlz_bind9_data); > state->log(ISC_LOG_INFO, "samba_dlz: shutting down"); > > dlz_bind9_state_ref_count--; > if (dlz_bind9_state_ref_count == 0)...

...t; 12-Jan-2017 12:12:03.317 >> 12-Jan-2017 11:34:35.317 general: zone_settimer: managed-keys-zone : enter >> 12-Jan-2017 11:34:35.317 general: automatic empty zone: 10.IN-ADDR.ARPA >> >> This is the destroy function used by bind9_dlz: >> >> >> _PUBLIC_ void dlz_destroy(void *dbdata) >> { >> struct dlz_bind9_data *state = talloc_get_type_abort(dbdata, >> struct dlz_bind9_data); >> state->log(ISC_LOG_INFO, "samba_dlz: shutting down"); >> >> dlz_bind9_state_ref_count--; >> if...

Mathias, Thanks for your reply. Please, try to start your bind with some debug level and run commando "rndc reload" and see the end of the log. I saw samba source code and found the destroy dns function in dlz_bind9.c and called by turture blz_bind9.c. When dlz_bind9.c is shutting down, I get this error when I try to update dns. update failed: NOTAUTH Failed nsupdate: 2