http://bugzilla.opensuse.org/show_bug.cgi?id=1206996 Bug ID: 1206996 Summary: Named with samba-dlz: core dump when windows 10 PC starts or wakes up; Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Samba Assignee: samba-maintainers@SuSE.de Reporter: conde.philippe@skynet.be QA Contact: samba-maintainers@SuSE.de Found By: --- Blocker: --- Created attachment 863974 --> http://bugzilla.opensuse.org/attachment.cgi?id=863974&action=edit named. conf I have samba-ad-dc installed and running on a raspberry pi400 with named on the same system managing only the samba domain (samdom.pce23.net) I connected two windows10 pro pc to this samba domain and now when a Windows PC starts or wake up there is a core dump of named. The windows PCs of course loss internet access and I need to start named via systemctl. Here the core Jan 10 09:35:53 rasp.samdom.pce23.net named[1035]: client @0xffff91070168 192.168.2.100#61871: update 'samdom.pce23.net/IN' denied Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: client @0xffff8fa71d68 192.168.2.100#52614: update '2.168.192.in-addr.arpa/IN' denied Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: name.c:664: REQUIRE(((name1) != ((void *)0) && ((const isc__magic_t *)(name1))->magic == ((('D') << 24 | ('N') << 16 | ('S') << 8 | ('n'))))) failed, back trace Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /usr/sbin/named(+0x1faa4) [0xaaaae6d1faa4] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(isc_assertion_failed+0x18) [0xffffb017a7fc] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libdns-9.18.10.so(dns_name_equal+0x19c) [0xffffaffa231c] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /usr/lib64/samba/bind9/dlz_bind9_18.so(dlz_subrdataset+0x1b8) [0xffffaeea6b9c] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /usr/sbin/named(+0x1df64) [0xaaaae6d1df64] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libdns-9.18.10.so(+0x184108) [0xffffb0094108] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libdns-9.18.10.so(+0x53a40) [0xffffaff63a40] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libns-9.18.10.so(+0x27384) [0xffffafec7384] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libns-9.18.10.so(+0x27db4) [0xffffafec7db4] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libns-9.18.10.so(+0x27a6c) [0xffffafec7a6c] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libns-9.18.10.so(+0x27bdc) [0xffffafec7bdc] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libns-9.18.10.so(+0x317a8) [0xffffafed17a8] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(isc_task_run+0x110) [0xffffb01a4bc0] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(+0x2d4f0) [0xffffb016d4f0] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(+0x2d940) [0xffffb016d940] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(+0x2db64) [0xffffb016db64] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libuv.so.1(+0xa374) [0xffffafa6a374] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libuv.so.1(+0x25ac4) [0xffffafa85ac4] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libuv.so.1(uv_run+0x57c) [0xffffafa6fefc] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(+0x2e02c) [0xffffb016e02c] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libisc-9.18.10.so(isc__trampoline_run+0x20) [0xffffb01a8ae0] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libc.so.6(+0x84ee8) [0xffffaf6c4ee8] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: /lib64/libc.so.6(+0xf0bdc) [0xffffaf730bdc] Jan 10 09:35:54 rasp.samdom.pce23.net named[1035]: exiting (due to assertion failure) Jan 10 09:35:54 rasp.samdom.pce23.net systemd[1]: named.service: Main process exited, code=dumped, status=6/ABRT Jan 10 09:35:54 rasp.samdom.pce23.net systemd[1]: named.service: Failed with result 'core-dump'. After restart of named the Windows PC can use named without problem to access internet until a restart or wake upp of these PCs. Here the query for the samba domain zone rasp:~ # samba-tool dns query 192.168.4.91 samdom.pce23.net @ ALL -U Administrator Password for [SAMDOM\Administrator]: Name=, Records=3, Children=0 SOA: serial=9, refresh=900, retry=600, expire=86400, minttl=3600, ns=rasp.samdom.pce23.net., email=hostmaster.samdom.pce23.net. (flags=600000f0, serial=9, ttl=3600) NS: rasp.samdom.pce23.net. (flags=600000f0, serial=7, ttl=900) A: 192.168.4.91 (flags=600000f0, serial=7, ttl=900) Name=_msdcs, Records=0, Children=0 Name=_sites, Records=0, Children=1 Name=_tcp, Records=0, Children=4 Name=_udp, Records=0, Children=2 Name=DESKTOP-GAU, Records=1, Children=0 A: 192.168.2.100 (flags=f0, serial=9, ttl=1200) Name=DESKTOP-RC7R9GG, Records=1, Children=0 A: 192.168.3.100 (flags=f0, serial=9, ttl=1200) Name=DomainDnsZones, Records=0, Children=2 Name=ForestDnsZones, Records=0, Children=2 Name=rasp, Records=1, Children=0 A: 192.168.4.91 (flags=f0, serial=1, ttl=900) Name=vm, Records=1, Children=0 A: 192.168.4.92 (flags=f0, serial=3, ttl=900) To solve a problem with samba_dnsupdate I added this line in sysconfig echo 'KRB5RCACHETYPE="none"' >> /etc/sysconfig/named I'll atrtach my named.conf stripped from all comments Let me known if you need more information Regards Philippe -- You are receiving this mail because: You are on the CC list for the bug.