samba - Nov 2008 - Samba 3.2.3 + Ubuntu 8.10 smbd panic

If this is the wrong list, apologies and redirect happily accepted :-)

Following an upgrade of my AD joined Ubuntu 8.04LTS / Samba 3.0.28  
server to Ubuntu 8.10 / Samba 3.2.3 smbd crashes on all connection  
attempts from clients. Domain controller is Windows 2008 Enterprise,  
winbindd appears to be functioning, wbinfo is good, getent is good,  
although there are several messages referring to not being able to get  
the network address for the KDC for the realm. After trying to prune  
smb.conf back to something minimal, I'm stuck.

Below is the panic trace at debug level 5 from the log for one of the  
clients that triggers the crash:

[2008/11/15 11:53:45,  0] lib/fault.c:fault_report(41)
   INTERNAL ERROR: Signal 6 in pid 13964 (3.2.3)
   Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/11/15 11:53:45,  0] lib/fault.c:fault_report(43)

   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/11/15 11:53:45,  0] lib/fault.c:fault_report(44)
   ==============================================================[2008/11/15
11:53:45,  0] lib/util.c:smb_panic(1663)
   PANIC (pid 13964): internal error
[2008/11/15 11:53:45,  0] lib/util.c:log_stack_trace(1767)
   BACKTRACE: 22 stack frames:
    #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0xb7cba3cc]
    #1 /usr/sbin/smbd(smb_panic+0x80) [0xb7cba529]
    #2 /usr/sbin/smbd [0xb7ca4fc3]
    #3 [0xb7aeb400]
    #4 /lib/tls/i686/cmov/libc.so.6(abort+0x188) [0xb76a1248]
    #5 /usr/lib/libtalloc.so.1(_talloc_steal+0x175) [0xb77ddb95]
    #6 /usr/sbin/smbd [0xb7cf5fad]
    #7 /usr/sbin/smbd(pdb_default_getgrnam+0x90) [0xb7cf2677]
    #8 /usr/sbin/smbd(pdb_getgrnam+0x26) [0xb7c6b0eb]
    #9 /usr/sbin/smbd(lookup_global_sam_name+0x1ee) [0xb7f6666d]
    #10 /usr/sbin/smbd(lookup_name+0x2a5) [0xb7c70178]
    #11 /usr/sbin/smbd(lookup_name_smbconf+0xfb) [0xb7c70c42]
    #12 /usr/sbin/smbd(token_contains_name_in_list+0x4a2) [0xb7ecf452]
    #13 /usr/sbin/smbd(change_to_user+0x3a6) [0xb7b75466]
    #14 /usr/sbin/smbd [0xb7b96d6a]
    #15 /usr/sbin/smbd(make_connection+0x796) [0xb7b97c2f]
    #16 /usr/sbin/smbd(reply_tcon_and_X+0x404) [0xb7eeb973]
    #17 /usr/sbin/smbd [0xb7b9129e]
    #18 /usr/sbin/smbd(smbd_process+0x435) [0xb7b934b1]
    #19 /usr/sbin/smbd(main+0xfa6) [0xb7b5aadf]
    #20 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)  
[0xb768a685]
    #21 /usr/sbin/smbd [0xb7b57af1]
[2008/11/15 11:53:45,  0] lib/fault.c:dump_core(201)
   dumping core in /var/log/samba/cores/smbd


Any advice that anyone can offer for determining the root cause of, or  
fixing, the panic will be much appreciated!

Is samba 4 still under development?
It seems that the last release was in 2006.

Samba4 is currently in Alpha state and under active development.

The most recent Alpha was alpha5, release about 4 months ago. The
current source is in the main samba Git repository in the source4
directory. As is noted all over the place, the software is alpha
quality and should not be used in testing.

On Sat, Nov 15, 2008 at 6:38 PM, Ansar Mohammed <ansarm@gmail.com>
wrote:
> Is samba 4 still under development?
> It seems that the last release was in 2006.
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>