search for: dlz_creat

...usly. I"m currently doing experiments to figure out what is going wrong. One thing is clear, the messages from samba_dlz is confusing, since 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 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) I'll report this defect...

...experiments to figure out what is going wrong. > > One thing is clear, the messages from samba_dlz is confusing, since > 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!...

...ad 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...

...at is going wrong. > > > > One thing is clear, the messages from samba_dlz is confusing, since > > 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...

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

...08:53:06 dc2 named[561]: samba_dlz: Failed to connect to Failed to > connect to */var/lib/samba/private/dns/sam.ldb*: Unable to open tdb > '/var/lib/samba/private/dns/sam.ldb': No such file or directory: Operations > error > > Oct 12 08:53:06 dc2 named[561]: samba_dlz: FAILED dlz_create call > result=25 #refs=0 > > Oct 12 08:53:06 dc2 named[561]: dlz_dlopen of 'AD DNS Zone' failed > > Oct 12 08:53:06 dc2 named[561]: SDLZ driver failed to load. > > Oct 12 08:53:06 dc2 named[561]: DLZ driver failed to load. > > Oct 12 08:53:06 dc2 named[561]: load...