Zombie Ryushu
2022-Jun-05 19:42 UTC
[Samba] Bind creates a situation where SSSD Crashes du to samba_dnsupdate
On 6/4/22 23:11, Zombie Ryushu via samba wrote:> ?We WERE able to get Kerberized Bind Zone Updates working for the very > first time. > > ?(GSS-TSIG) > > What this means is that samba_dnsupdate -actually works- just with > straight Bind. > > ?That's had a bad secondary effect. Samba injects a record that looks > like: > > ?pukey IN A 192.168.0.4 into Bind. > > This crashes SSSD with an Assertion failure. How do I remove this a > DNS entry from Samba? > >The SSSD Daemon will crash with an Assertion failure if a DNS Entry exists in Bind where in an Internal Domain in the 192.168.0.x subnet points to a specific Domain. Such as: pukey IN A 192.168.0.4. Jun 05 15:23:15 olympia sssd[15008]: sssd_be: io.c:224: ber_flush2: Assertion `SOCKBUF_VALID( sb )' failed. Jun 05 15:23:15 olympia be[15184]: Starting up Jun 05 15:23:25 olympia sssd[15184]: sssd_be: io.c:224: ber_flush2: Assertion `SOCKBUF_VALID( sb )' failed. Jun 05 15:23:27 olympia be[15194]: Starting up Jun 05 15:23:37 olympia sssd[15194]: sssd_be: io.c:224: ber_flush2: Assertion `SOCKBUF_VALID( sb )' failed. Jun 05 15:23:41 olympia be[15219]: Starting up This is the error produced. sssd will cease functioning until the DNS Entry is removed. Active: failed (Result: exit-code) since Sun 2022-06-05 15:23:52 EDT; 33s ago ??? Process: 14997 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=1/FAILURE) ?? Main PID: 14997 (code=exited, status=1/FAILURE) samba_dnsupdate will cause this to happen.
Rowland Penny
2022-Jun-05 20:01 UTC
[Samba] Bind creates a situation where SSSD Crashes du to samba_dnsupdate
On Sun, 2022-06-05 at 15:42 -0400, Zombie Ryushu via samba wrote:> > > > > > The SSSD Daemon will crash with an Assertion failure if a DNS Entry > exists in Bind where in an Internal Domain in the 192.168.0.x subnet > points to a specific Domain. Such as: > > pukey IN A 192.168.0.4.There aren't supposed to be any dns entries in bind9 when using Samba AD, they are supposed to be in AD.> > Jun 05 15:23:15 olympia sssd[15008]: sssd_be: io.c:224: ber_flush2: > Assertion `SOCKBUF_VALID( sb )' failed. > Jun 05 15:23:15 olympia be[15184]: Starting up > Jun 05 15:23:25 olympia sssd[15184]: sssd_be: io.c:224: ber_flush2: > Assertion `SOCKBUF_VALID( sb )' failed. > Jun 05 15:23:27 olympia be[15194]: Starting up > Jun 05 15:23:37 olympia sssd[15194]: sssd_be: io.c:224: ber_flush2: > Assertion `SOCKBUF_VALID( sb )' failed. > Jun 05 15:23:41 olympia be[15219]: Starting up > > This is the error produced. sssd will cease functioning until the > DNS > Entry is removed. > > Active: failed (Result: exit-code) since Sun 2022-06-05 15:23:52 > EDT; > 33s ago > Process: 14997 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} > (code=exited, status=1/FAILURE) > Main PID: 14997 (code=exited, status=1/FAILURE)I am sorry, but sssd is not part of Samba, I suggest you report this to the sssd-users mailing list.> > samba_dnsupdate will cause this to happen.It is supposed to. Rowland