similar to: AD-DC samba_gpoupdate failing

Well, I had a look at the python bindings and the error handling was in shambles. I fixed libgpo/pygpo.c and I now get: gpos = ads.get_gpo_list(creds.get_username()) SystemError: Failed to get machine token for 'DC01$' (CN=DC01,OU=Domain Controllers,DC=rvx,DC=is) (the failing call is status = gp_get_machine_token(self->ads_ptr, frame, dn,

Ok, I've analyzed this and found that the cause is a call to getpwuid(uid) with the uid being that of the domain controller. "wbinfo --uid-info=3000074" works and returns information, but this library function fails. This is then propagated upwards as a memory error, because it is being called from getpwuid_alloc() which is a talloc variant. the api doesn't allow us to

On Tue, 26 Feb 2019 13:34:32 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Ok, I've analyzed this and found that the cause is a call to > getpwuid(uid) with the uid being that of the domain controller. > "wbinfo --uid-info=3000074" works and returns information, but this > library function fails. > This is then propagated upwards as a memory error,

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

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

Hello there. I´ve been having problems with dynamic dns update by dhcp on my samba ADDC running on CentOS 7 on an RPI2. After a while, the dhccp_dyndns.sh stops stops being able to authenticate with named. for the longest time I was stumped with this, exploring all kinds of kerberos issues, but found out that *restartint* named did resolve the issue. I have finally traced this problem down to a

Just a wild guess, but I and others have been having problems with samba_dlz, because of named "reload." Try to see if systemctl reload named and systemctl restart named break and fix the server respectively. (if your're not using systemd, try "serivice named reload", "service named restart instead") If you have a /etc/logrotate.d/named file containing

On Wed, 2 Jan 2019 09:54:24 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 Jan 2019 09:45:56 +0000 > Kristján Valur Jónsson <kristjan at rvx.is> wrote: > > > Any thoughts? Have code, will debug. The error itself is > > meaningless to me and I am deeply and utterly unfamiliar with samba > > code, but if you have any thought or

No, I'm reading the dlz_bind9.c code. I've found and fixed the problem. It turns out that using a reference counted singleton is a bad idea. The singleton is defunct after reload. If we simply create a new state object and destroy the old one as bind is trying to let us do, things work out fine. This works, at least, for bind9.9. I cant test with the older (9.8), so it is possible that

so the DC with FSMO is not done first?     Van: Kristján Valur Jónsson [mailto:kristjan at rvx.is] Verzonden: vrijdag 28 december 2018 17:08 Aan: L.P.H. van Belle Onderwerp: Re: [Samba] replication failing for 4.9.4 dc01 is still running 4.7.7.  No need to restart it.  There is also still a DC03 running 4.7.7.  the only one I've upgraded is DC02.  resolv.conf on DC02 is configured with

Well, I created a bug report for this issue. Seems that none of the developers has picked up on it. https://bugzilla.samba.org/show_bug.cgi?id=13214 On 16 January 2018 at 19:47, Mark Nienberg <mnlists at tippingstructural.com> wrote: > > On Tue, Jan 9, 2018 at 7:34 AM, Kristján Valur Jónsson via samba < > samba at lists.samba.org> wrote: > >> >> I have

Hello there. I have a setup with Samba AD and a Named backend. Everything has been working fine, until a few days ago, I cannot start the DNS snap-in from windows. I get a dialog box saying "Access was denied. Would you like to add it anyway?" If I enable level 3 debugging in the samba.conf, I get the following: [2017/05/11 07:25:30.413481, 3]

Right, that is the _workaround_. It'd be great to see that documented in the Wiki. However, samba_dlz is supposed to support reload, and there has been work on that file to fix slow reload previously. 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,

On 18 December 2017 at 16:20, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > Even this looks wrong, I would expect something like this: > > Dec 18 07:43:59 dc3 dhcpd: DHCPREQUEST for 192.168.0.111 from > cc:4e:ec:e9:c8:d3 via eth0 > Dec 18 07:43:59 dc3 dhcpd: DHCPACK on 192.168.0.111 to cc:4e:ec:e9:c8:d3 > via eth0 > Dec 18 07:47:33 dc3 dhcpd:

On Fri, 11 May 2018 14:14:39 +0000 Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > I"m seeing this as well, after I updated my CentOS 7 hosts to the > latest release. > Something seems to have broken! > Do you have a 'include' line in krb5.conf ? If you do, remove it. Rowland

On 17 January 2018 at 16:00, Kristján Valur Jónsson via samba < samba at lists.samba.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()

Hello there. So, I have a Samba AD setup, with DHCP and samba_dlz setup as described in the wiki. However, I find that after a while, dynamic DHCPD updates stop working. The fix is for me to restart the named server. When in this state, I get log messages like: DHCPREQUEST for 192.168.52.232 (192.168.60.2) from 8c:be:be:0d:cf:3c (RedmiNote4-Gj?gur) via 192.168.52.253 Dec 18 15:39:44 dc02

Fyi, I've been trying to get the devs to take notice of this problem. People keep pointing fingers. Samba says its Named/bind, bind says its the OS vendors.... See: https://bugzilla.samba.org/show_bug.cgi?id=13214 https://bugzilla.samba.org/show_bug.cgi?id=13230 Maybe I'll be forced to hack on the code myself to figure out what's really happening when a "reload" happens.

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

Hi there. I'm running an AD DC in a KVM VM, a centos7 server. named is showing a very hight cpu usage, close to 100%. I just increased the number of CPUs to 2 to cope. This is a small company, with perhaps 20 workstations and another 20 linux servers. There shouldn't be that much happening. top - 17:27:48 up 2:29, 1 user, load average: 1.08, 1.13, 1.09 Tasks: 139 total, 1 running,