[Samba] Winbind 3.2.0rc2 Coredump [was: Re: Help needed. Samba
3.2.0rc2 - IDMAP - Windows 2008 Server - ADS Integration - Winbind]
Scott Lovenberg
scott.lovenberg at gmail.com
Sat Jun 28 09:39:19 GMT 2008
Samba-Liste wrote:
> Hi,
>
> sorry, it's me again:
>
> On Fri, 2008-06-27 at 17:35 +0200, Samba-Liste wrote:
>
>> Hi again,
>>
>> On Fri, 2008-06-27 at 13:31 +0200, Samba-Liste wrote:
>>
>>> Hi,
>>>
>>> I read at least 100 different documentations during the last week and
>>> didn't get it. So I decided to ask the list for help :)
>>>
>>>
>> - the problem is solved now. I found this in the logs on linux-side:
>>
>
> - but another problem occured now
> - the setup worked nice yesterday evening unitl ist stoppen working
> - as I tried a login this morning it didn't work anymore
> - if I try a "getnet passwd <user>" I get nothing back
> - no login via pam_winbind is possible
> - But I see a winbind core-dump in the logs:
>
> ----- snip -----
>
> [2008/06/28 09:51:02, 0] lib/fault.c:fault_report(40)
> ===============================================================
> [2008/06/28 09:51:02, 0] lib/fault.c:fault_report(41)
> INTERNAL ERROR: Signal 11 in pid 4897 (3.2.0rc2)
> Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2008/06/28 09:51:02, 0] lib/fault.c:fault_report(43)
>
> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2008/06/28 09:51:02, 0] lib/fault.c:fault_report(44)
> ===============================================================
> [2008/06/28 09:51:02, 0] lib/util.c:smb_panic(1666)
> PANIC (pid 4897): internal error
> [2008/06/28 09:51:02, 0] lib/util.c:log_stack_trace(1770)
> BACKTRACE: 19 stack frames:
> #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x815b36c]
> #1 /usr/sbin/winbindd(smb_panic+0x80) [0x815b4a8]
> #2 /usr/sbin/winbindd [0x8145fea]
> #3 [0xb7f13420]
> #4 /usr/lib/samba/nss_info/rfc2307.so [0xb787f8e9]
> #5 /usr/sbin/winbindd(nss_get_info+0x193) [0x83d30e0]
> #6 /usr/sbin/winbindd(nss_get_info_cached+0x180) [0x80a67a5]
> #7 /usr/sbin/winbindd [0x80c40d4]
> #8 /usr/sbin/winbindd [0x80a820e]
> #9 /usr/sbin/winbindd(winbindd_dual_userinfo+0x183) [0x8098372]
> #10 /usr/sbin/winbindd [0x80c89c5]
> #11 /usr/sbin/winbindd(async_request+0x1b2) [0x80c9fb3]
> #12 /usr/sbin/winbindd(init_child_connection+0x2bd) [0x809fa85]
> #13 /usr/sbin/winbindd(async_domain_request+0x139) [0x80ca23c]
> #14 /usr/sbin/winbindd [0x809fcfb]
> #15 /usr/sbin/winbindd(rescan_trusted_domains+0x49) [0x80a00f9]
> #16 /usr/sbin/winbindd(main+0xe00) [0x8095464]
> #17 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7c72ea8]
> #18 /usr/sbin/winbindd [0x8092e11]
> [2008/06/28 09:51:02, 0] lib/fault.c:dump_core(201)
> dumping core in /var/log/samba/cores/winbindd
>
> ----- snip -----
>
> - I then did a "wbinfo -u" and "wbinfo -g"
> - both worked normally
> - afterwards "getent passwd <user>" an pam-login worked again
> - but only for a few minutes then the same happend again
>
> ----- snip -----
>
> [2008/06/28 09:59:35, 0] lib/fault.c:fault_report(40)
> ===============================================================
> [2008/06/28 09:59:35, 0] lib/fault.c:fault_report(41)
> INTERNAL ERROR: Signal 11 in pid 5265 (3.2.0rc2)
> Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2008/06/28 09:59:35, 0] lib/fault.c:fault_report(43)
>
> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2008/06/28 09:59:35, 0] lib/fault.c:fault_report(44)
> ===============================================================
> [2008/06/28 09:59:35, 0] lib/util.c:smb_panic(1666)
> PANIC (pid 5265): internal error
> [2008/06/28 09:59:35, 0] lib/util.c:log_stack_trace(1770)
> BACKTRACE: 22 stack frames:
> #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x815b36c]
> #1 /usr/sbin/winbindd(smb_panic+0x80) [0x815b4a8]
> #2 /usr/sbin/winbindd [0x8145fea]
> #3 [0xb7f13420]
> #4 /usr/lib/samba/nss_info/rfc2307.so [0xb785e8e9]
> #5 /usr/sbin/winbindd(nss_get_info+0x193) [0x83d30e0]
> #6 /usr/sbin/winbindd(nss_get_info_cached+0x180) [0x80a67a5]
> #7 /usr/sbin/winbindd [0x80c40d4]
> #8 /usr/sbin/winbindd [0x80a820e]
> #9 /usr/sbin/winbindd(winbindd_dual_userinfo+0x183) [0x8098372]
> #10 /usr/sbin/winbindd [0x80c89c5]
> #11 /usr/sbin/winbindd(async_request+0x1b2) [0x80c9fb3]
> #12 /usr/sbin/winbindd(async_domain_request+0x57) [0x80ca15a]
> #13 /usr/sbin/winbindd(do_async_domain+0x14e) [0x80cbfb6]
> #14 /usr/sbin/winbindd(winbindd_lookupname_async+0x29d) [0x80ccdf7]
> #15 /usr/sbin/winbindd(winbindd_getpwnam+0x37f) [0x8098044]
> #16 /usr/sbin/winbindd [0x8093b22]
> #17 /usr/sbin/winbindd [0x8093c39]
> #18 /usr/sbin/winbindd [0x8094598]
> #19 /usr/sbin/winbindd(main+0x1035) [0x8095699]
> #20 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7c72ea8]
> #21 /usr/sbin/winbindd [0x8092e11]
> [2008/06/28 09:59:35, 0] lib/fault.c:dump_core(201)
>
> ----- snip -----
>
> - there's also this error in the logs I don't understand
> - but it seems not to be directly related to the core dump
>
> ----- snip -----
>
> [2008/06/28 09:56:11, 1] libsmb/clientgen.c:cli_rpc_pipe_close(554)
> cli_rpc_pipe_close: cli_close failed on pipe \lsarpc, fnum 0x400d to
> machine WIN-6P6G74VAOZ7.testlab.company.com. Error was SUCCESS - 0
> [2008/06/28 09:56:11, 1] libsmb/clientgen.c:cli_rpc_pipe_close(554)
> cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x400b to
> machine WIN-6P6G74VAOZ7.testlab.company.com. Error was SUCCESS - 0
> [2008/06/28 09:56:11, 1] libsmb/clikrb5.c:ads_krb5_mk_req(666)
> ads_krb5_mk_req: krb5_get_credentials failed for WIN-6P6G74VAOZ7
> $@TESTLAB (Cannot resolve network address for KDC in requested realm)
> [2008/06/28 09:56:11, 1]
> libsmb/cliconnect.c:cli_session_setup_kerberos(626)
> cli_session_setup_kerberos: spnego_gen_negTokenTarg failed: Cannot
> resolve network address for KDC in requested realm
>
> ----- snip -----
>
> - Here comes my final smb.conf
>
> ----- snip -----
>
> [global]
> workgroup = TESTLAB
> realm = TESTLAB.COMPANY.COM
> netbios name = filesrv001
> server string = Samba Storage Fileserver 001 (%v)
> security = ADS
> idmap domains = BUILTIN, TESTLAB
> idmap config TESTLAB:backend = ad
> idmap config TESTLAB:default = yes
> idmap config TESTLAB:schema_mode = rfc2307
> idmap config TESTLAB:base_rid = 10000
> idmap config TESTLAB:range = 10000-100000
> idmap config BUILTIN:backend = tdb
> idmap config BUILTIN:base_rid = 800
> idmap config BUILTIN:range = 800-999
> idmap uid = 800-100000
> idmap gid = 800-100000
> winbind nss info = rfc2307
> winbind use default domain = yes
> winbind nested groups = Yes
> winbind offline logon = yes
> password server = WIN-6P6G74VAOZ7.TESTLAB.COMPANY.COM
> wins server = WIN-6P6G74VAOZ7.TESTLAB.COMPANY.COM
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> hide unreadable = yes
> hide dot files = yes
> unix charset = LOCALE
> log level = 1
> log file = /var/log/samba/log.%m
>
> [big_data]
> comment = Very Big Share
> path = /SERV
> browseable = yes
> guest ok = no
> valid users = "@TESTLAB\entenhausen"
> create mask = 660
> directory mode = 770
> writeable = yes
> readonly = no
> force group = "TESTLAB\entenhausen"
>
> ----- snip -----
>
> - Any Ideas what I can do now?
> - should I post more information as my pam.d files?
> - Is this a config issue or should I open a bug report?
>
> best regards
>
> Daniel
>
>
Have you tried using the 'nss_ldap' with the entry 'ldap' in your
nsswitch.conf? I found that to be the best way to interface the LDAP
backend in my case. I tried the pam route, but since Slackware does not
ship with it, I found the nss_ldap module to be the path of least
resistance. It's worth a shot if you have troubles with PAM modules,
but it won't allow syncing of *nix and Windows passwords, IIRC.
nss_ldap is available from PADL.
More information about the samba
mailing list