[Samba] Samba panic when accessing DNS domain entry with RSAT DNS tool

Andreas Oster aoster at novanetwork.de
Tue Nov 13 11:29:49 UTC 2018


Hello Daniel,

I have setup a virtual Windows 7 machine, installed the RSAT tools and 
are now able to access the DNS settings without any problem.
Thank you very much for the advice.

best regards
Andreas

Am 09.11.2018 um 12:05 schrieb Mueller:
> I do not know. But after I did it one time from a windos 10 machine with RSAT my whole dns was broken.
> The only thing could cure that was to open RSAT on my windows 7 admin PC and delete the entries I added on Windows 10 and save the changes.
>
>
>
>
> Daniel Müller
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Oster [mailto:aoster at novanetwork.de]
> Gesendet: Freitag, 9. November 2018 11:52
> An: mueller at tropenklinik.de; samba at lists.samba.org
> Betreff: Re: [Samba] Samba panic when accessing DNS domain entry with RSAT DNS tool
>
> Hello Daniel,
>
> thank you for the fast reply.
>
> I am also using Windows 10. I'll setup a temporary Win7 VM to test if this will make any difference.
>
> Do you know if this a known issue with RSAT on Windows 10 ?
>
> Best regards
> Andreas
>
> Am 09.11.2018 um 11:23 schrieb Mueller:
>> I had this error when I did it from Windows 10.
>> I usede a Windows 7 PC and everything was fine again.
>>
>>
>> Daniel Müller
>>
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Andreas Oster via samba [mailto:samba at lists.samba.org]
>> Gesendet: Freitag, 9. November 2018 11:16
>> An: samba at lists.samba.org
>> Betreff: [Samba] Samba panic when accessing DNS domain entry with RSAT
>> DNS tool
>>
>> Hi everybody,
>>
>> for some time now I have an issue with our samba/bind9-DLZ setup which became worse lately.
>> I use the RSAT DNS tool to configure DNS records. In the past it sometimes happened, that DNS died when accessing the domain zone. This condition could only be resolved by restarting samba on the affected DC.
>> Unfortunately the situation got worse and configuration/modification of entries in the domain zone is nearly impossible.
>>
>> Connecting to the DNS is working but when I do select the domain zone I get the following in the log.samba log file:
>>
>> <--
>>
>> [2018/11/09 11:08:18.452913,  0]
>> ../source4/rpc_server/dnsserver/dcerpc_dnsserver.c:1089(dnsserver_query_zone)
>>      dnsserver: Invalid zone operation IsSigneddnsserver: Invalid zone operation IsSigneddnsserver: Invalid zone operation IsSigneddnsserver:
>> Invalid zone operation IsSigneddnsserver: Invalid zone operation
>> IsSigneddnsserver: Invalid zone operation IsSigneddnsserver: Invalid
>> zone operation
>> IsSigned==============================================================
>> =
>> [2018/11/09 11:08:23.956220,  0] ../lib/util/fault.c:80(fault_report)
>>      INTERNAL ERROR: Signal 11 in pid 3901 (4.9.3-GIT-424d4d2b408)
>>      Please read the Trouble-Shooting section of the Samba HOWTO
>> [2018/11/09 11:08:23.956548,  0] ../lib/util/fault.c:82(fault_report)
>>      ===============================================================
>> [2018/11/09 11:08:23.956634,  0] ../lib/util/fault.c:128(smb_panic_default)
>>      smb_panic_default: PANIC (pid 3901): internal error
>> [2018/11/09 11:08:23.957585,  0] ../lib/util/fault.c:261(log_stack_trace)
>>      BACKTRACE: 49 stack frames:
>>       #0 /usr/local/samba/lib/libsamba-util.so.0(log_stack_trace+0x2e)
>> [0x7f2472c76562]
>>       #1 /usr/local/samba/lib/libsamba-util.so.0(+0x202e2) [0x7f2472c762e2]
>>       #2 /usr/local/samba/lib/libsamba-util.so.0(log_stack_trace+0)
>> [0x7f2472c76534]
>>       #3 /usr/local/samba/lib/libsamba-util.so.0(+0x201e2) [0x7f2472c761e2]
>>       #4 /usr/local/samba/lib/libsamba-util.so.0(+0x201f7) [0x7f2472c761f7]
>>       #5 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f2472eea890]
>>       #6
>> /usr/local/samba/lib/private/libldb.so.1(ldb_msg_find_element+0x5e)
>> [0x7f2472a2ac88]
>>       #7
>> /usr/local/samba/lib/private/libldb.so.1(ldb_msg_find_ldb_val+0x23)
>> [0x7f2472a2bd6a]
>>       #8
>> /usr/local/samba/lib/private/libldb.so.1(ldb_msg_find_attr_as_string+0
>> x27)
>> [0x7f2472a2c41c]
>>       #9
>> /usr/local/samba/lib/libdcerpc-server.so.0(dns_name_compare+0x4e)
>> [0x7f245b39eae2]
>>       #10 /usr/local/samba/lib/private/libldb.so.1(ldb_qsort+0x723)
>> [0x7f2472a3ba6d]
>>       #11 /usr/local/samba/lib/libdcerpc-server.so.0(+0x65483)
>> [0x7f245b398483]
>>       #12 /usr/local/samba/lib/libdcerpc-server.so.0(+0x66844)
>> [0x7f245b399844]
>>       #13 /usr/local/samba/lib/libdcerpc-server.so.0(+0x6722c)
>> [0x7f245b39a22c]
>>       #14 /usr/local/samba/lib/libdcerpc-server.so.0(+0x2c371)
>> [0x7f245b35f371]
>>       #15 /usr/local/samba/lib/libdcerpc-server.so.0(+0x2cdea)
>> [0x7f245b35fdea]
>>       #16 /usr/local/samba/lib/libdcerpc-server.so.0(+0x2e808)
>> [0x7f245b361808]
>>       #17
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callbac
>> k+0x6a)
>> [0x7f24723d46a2]
>>       #18 /usr/local/samba/lib/private/libtevent.so.0(+0x8803)
>> [0x7f24723d4803]
>>       #19
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done+0x25)
>> [0x7f24723d4830]
>>       #20 /usr/local/samba/lib/libdcerpc-binding.so.0(+0x1e1f6)
>> [0x7f246d20c1f6]
>>       #21
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callbac
>> k+0x6a)
>> [0x7f24723d46a2]
>>       #22 /usr/local/samba/lib/private/libtevent.so.0(+0x8803)
>> [0x7f24723d4803]
>>       #23
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done+0x25)
>> [0x7f24723d4830]
>>       #24
>> /usr/local/samba/lib/private/libsamba-sockets-samba4.so(+0xd962)
>> [0x7f246d425962]
>>       #25
>> /usr/local/samba/lib/private/libsamba-sockets-samba4.so(+0xdb9c)
>> [0x7f246d425b9c]
>>       #26
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callbac
>> k+0x6a)
>> [0x7f24723d46a2]
>>       #27 /usr/local/samba/lib/private/libtevent.so.0(+0x8803)
>> [0x7f24723d4803]
>>       #28
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_done+0x25)
>> [0x7f24723d4830]
>>       #29
>> /usr/local/samba/lib/private/libsamba-sockets-samba4.so(+0xcda2)
>> [0x7f246d424da2]
>>       #30
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_req_notify_callbac
>> k+0x6a)
>> [0x7f24723d46a2]
>>       #31 /usr/local/samba/lib/private/libtevent.so.0(+0x8803)
>> [0x7f24723d4803]
>>       #32 /usr/local/samba/lib/private/libtevent.so.0(+0x8930)
>> [0x7f24723d4930]
>>       #33
>> /usr/local/samba/lib/private/libtevent.so.0(tevent_common_invoke_immed
>> iate_handler+0x184)
>> [0x7f24723d35a5]
>>       #34
>> /usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_immedia
>> te+0x37)
>> [0x7f24723d36ab]
>>       #35 /usr/local/samba/lib/private/libtevent.so.0(+0x11d33)
>> [0x7f24723ddd33]
>>       #36 /usr/local/samba/lib/private/libtevent.so.0(+0xe5d9)
>> [0x7f24723da5d9]
>>       #37
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_once+0x11e)
>> [0x7f24723d204f]
>>       #38
>> /usr/local/samba/lib/private/libtevent.so.0(tevent_common_loop_wait+0x
>> 25)
>> [0x7f24723d23a1]
>>       #39 /usr/local/samba/lib/private/libtevent.so.0(+0xe67b)
>> [0x7f24723da67b]
>>       #40
>> /usr/local/samba/lib/private/libtevent.so.0(_tevent_loop_wait+0x2b)
>> [0x7f24723d2444]
>>       #41 /usr/local/samba/lib/process_model/standard.so(+0x27e9)
>> [0x7f2464bfd7e9]
>>       #42
>> /usr/local/samba/lib/private/libservice-samba4.so(task_server_startup+
>> 0x9b)
>> [0x7f2471fafaf5]
>>       #43 /usr/local/samba/lib/private/libservice-samba4.so(+0x2afe)
>> [0x7f2471fadafe]
>>       #44
>> /usr/local/samba/lib/private/libservice-samba4.so(server_service_start
>> up+0x166)
>> [0x7f2471fadc83]
>>       #45 samba: task[dcesrv](+0x5ca6) [0x557afdceaca6]
>>       #46 samba: task[dcesrv](main+0x3f) [0x557afdceadb8]
>>       #47 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)
>> [0x7f246fec9b97]
>>       #48 samba: task[dcesrv](_start+0x2a) [0x557afdce88ca]
>> [2018/11/09 11:08:24.463400,  0]
>> ../source4/smbd/process_standard.c:158(standard_child_pipe_handler)
>>      standard_child_pipe_handler: Child 3901 (rpc) terminated with
>> signal 6
>> -->
>>
>> Afterwards DNS is not working and samba needs to be restarted.
>> I have configured some additional zones which do not result in the same error when being accessed via the RSAT DNS tool.
>>
>> Does anyone have an idea what could be the cause of the problem and how it could be resolved ?
>>
>> Thank you very much for your kind support.
>>
>> Best regards
>> Andreas
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>
>> ---
>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
>> https://www.avast.com/antivirus
>>
>




More information about the samba mailing list