Samba 3.5.5 crashing issue

[Eric Chris Garrison]

  So, to follow up this thread... the solution I had works for the test 
machine, but when I applied the RPMs created by makerpms.sh, smbd 
crashes on startup.  After much fiddling, I tried installing the 
"vanilla" RPMs for samba-3.5.5 from samba.org and got the same problem:

[2010/09/28 10:17:55.422863,  0] lib/fault.c:46(fault_report)
   ===============================================================
[2010/09/28 10:17:55.422993,  0] lib/fault.c:47(fault_report)
   INTERNAL ERROR: Signal 6 in pid 10535 (3.5.5)
   Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/09/28 10:17:55.423657,  0] lib/fault.c:49(fault_report)

   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2010/09/28 10:17:55.423715,  0] lib/fault.c:50(fault_report)
   ===============================================================
[2010/09/28 10:17:55.423755,  0] lib/util.c:1465(smb_panic)
   PANIC (pid 10535): internal error
[2010/09/28 10:17:55.437097,  0] lib/util.c:1569(log_stack_trace)
   BACKTRACE: 19 stack frames:
    #0 smbd(log_stack_trace+0x1c) [0x2ab3e844bdac]
    #1 smbd(smb_panic+0x2b) [0x2ab3e844be7b]
    #2 smbd [0x2ab3e843c11e]
    #3 /lib64/libc.so.6 [0x2ab3eb5d42d0]
    #4 /lib64/libc.so.6(gsignal+0x35) [0x2ab3eb5d4265]
    #5 /lib64/libc.so.6(abort+0x110) [0x2ab3eb5d5d10]
    #6 /usr/lib64/libtalloc.so.1 [0x2ab3ecaa89d9]
    #7 /usr/lib64/libtalloc.so.1(talloc_free+0x283) [0x2ab3ecaac913]
    #8 /usr/lib/libwbclient.so.0(wbcFreeMemory+0xe) [0x2ab3eb1851cd]
    #9 /usr/lib/libwbclient.so.0(wbcSidToGid+0xa2) [0x2ab3eb1872ce]
    #10 smbd(winbind_sid_to_gid+0x5f) [0x2ab3e8419e6f]
    #11 smbd(sid_to_gid+0x123) [0x2ab3e83f9b73]
    #12 smbd(create_local_nt_token+0x139) [0x2ab3e849e759]
    #13 smbd(get_root_nt_token+0xbe) [0x2ab3e849ec7e]
    #14 smbd(svcctl_init_keys+0x25) [0x2ab3e8365f85]
    #15 smbd(registry_init_full+0x63) [0x2ab3e870b733]
    #16 smbd(main+0x62a) [0x2ab3e8735ffa]
    #17 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2ab3eb5c1994]
    #18 smbd [0x2ab3e81da3c9]
[2010/09/28 10:17:55.440068,  0] lib/fault.c:326(dump_core)
   dumping core in /var/log/samba/cores/smbd

I've tried both with the sample smb.conf and with our local one that 
works on the test machine, with the same results.

Any hints as to what could be wrong?

Thank you,

Chris

-------- Original Message --------
Subject: 	Re: AFS token issue in samba 3.5.5? [solution]
Date: 	Tue, 21 Sep 2010 17:00:39 -0400
From: 	Eric Chris Garrison <ecgarris at iupui.edu>
To: 	Gémes Géza <geza at kzsdabas.hu>
CC: 	Volker.Lendecke at SerNet.DE, samba-technical at lists.samba.org



  I will try to create a patch and submit it as soon as I get some time,
though I'll have to figure out the proper procedure.  I'm a bit swamped
right now, so it won't be immediate, but if you follow my directions in
the fixed reply, it should work.

It's nice to know someone else out there is using this... we rather rely
on it here.

Chris

On 9/18/10 4:21 AM, Gémes Géza wrote:
>  2010-09-18 08:48 keltezéssel, Volker Lendecke írta:
>>  On Sat, Sep 18, 2010 at 08:21:47AM +0200, Gémes Géza wrote:
>>
>>>  Could you post your patch somewhere. Or give your assigned (by bugzilla)
>>>  bug number. I also plan to upgrade to 3.5.5. (and also use fake-kaserver)
>>>
>>  BTW, I'm really surprised that this is still being used. It
>>  was meant at the time as a pretty specialized hack... :-)
>>
>>  Volker
>>
>  Until there is something better IMHO it is the best fail-back solution.
>  At our site we have a samba3 (with ldap backend) domain, a heimdal
>  kerberos (with the same ldap backend) realm, and an openafs data store.
>  The windows clients authenticate to the samba3 domain, and by integrated
>  logon they get kerberos tickets and afs tokens, and then the logon
>  scripts are able to map the afs dirs at the correct drive letters. If
>  integrated logon or other afs components fail the logon scripts are
>  trying to map a share from the logon server (here comes the
>  fake-kaserver part into action). Btw. the netlogon share is also in afs
>  (replication is a non-issue ;-) ). So I think keeping fake-kaserver and
>  vfs-afsacl functional is crucial for sites where there is a
>  samba-openafs mixed infrastructure. The only better aproach I could
>  think about would be to "convince" windows machines to do proxiable
>  kerberos authentication to samba even in NT4 domain mode. However I'm
>  afraid that is way harder to implement than to keep fake-kaserver alive.
>
>  Geza