XAD crashes in spengo

The xadsd process can crash with only a few workstations accessing the domain or remaining authenticated for long periods of time.
Adding a samba server as a member server to DSFW can bring about a similar crash.

Here is a section from the /var/log/messages:
Oct 13 10:06:42 dswserver smbd[32288]: [2009/10/13 10:06:42, 0]
lib/util.c:log_stack_trace(1737)
Oct 13 10:06:42 dswserver smbd[32288]:   BACKTRACE: 13 stack frames:
Oct 13 10:06:42 dswserver smbd[32288]:    #0
/usr/sbin/smbd(log_stack_trace+0x2d) [0x8023834d]
Oct 13 10:06:42 dswserver smbd[32288]:    #1 /usr/sbin/smbd [0x8030f2fc]
Oct 13 10:06:42 dswserver smbd[32288]:    #2 /usr/sbin/smbd [0x8030f4e3]
Oct 13 10:06:42 dswserver smbd[32288]:    #3
/usr/sbin/smbd(ncalrpc_write_to_funnel+0xfa) [0x80178eea]
Oct 13 10:06:42 dswserver smbd[32288]:    #4 /usr/sbin/smbd(write_to_pipe+0x6e)
[0x80175b3e]
Oct 13 10:06:42 dswserver smbd[32288]:    #5 /usr/sbin/smbd [0x80067c21]
Oct 13 10:06:42 dswserver smbd[32288]:    #6 /usr/sbin/smbd [0x80068156]
Oct 13 10:06:42 dswserver smbd[32288]:    #7 /usr/sbin/smbd(reply_trans+0x6c3)
[0x80068f73]
Oct 13 10:06:42 dswserver smbd[32288]:    #8 /usr/sbin/smbd [0x800c22a0]
Oct 13 10:06:42 dswserver smbd[32288]:    #9 /usr/sbin/smbd(smbd_process+0x836)
[0x800c3316]
Oct 13 10:06:42 dswserver smbd[32288]:    #10 /usr/sbin/smbd(main+0xbdd)
[0x8031133d]
Oct 13 10:06:42 dswserver smbd[32288]:    #11
/lib/libc.so.6(__libc_start_main+0xdc) [0xb7b3d89c]
Oct 13 10:06:42 dswserver smbd[32288]:    #12 /usr/sbin/smbd [0x8004a461]
Oct 13 10:06:42 dswserver smbd[32288]: [2009/10/13 10:06:42, 0]
smbd/server.c:exit_server_common(757)
Oct 13 10:06:42 dswserver smbd[32288]:   Last message was SMBtrans
Oct 13 10:06:42 dswserver smbd[32288]: [2009/10/13 10:06:42, 0]
lib/fault.c:dump_core(181)
Oct 13 10:06:42 dswserver smbd[32288]:   dumping core in
/var/log/samba/cores/smbd
Oct 13 10:06:42 dswserver smbd[32288]:


Taking a core shows the following stack:
#0  0xb0abf6b9 in ?? () from
/home/xadsd/opt/novell/xad/lib/gss/mech_spnego.so
#1  0xb7b4cfa1 in gss_accept_sec_context () from
/home/xadsd/opt/novell/xad/lib/libgssapi.so.1
#2  0xb7433b02 in rpc__gssauth_accept_sec_context () from
/home/xadsd/opt/novell/xad/lib/libauth_gss.so
#3  0xb7433ee7 in rpc__gssauth_cn_fmt_srvr_resp () from
/home/xadsd/opt/novell/xad/lib/libauth_gss.so
#4  0xb6bec27d in ?? () from
/home/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#5  0xb6bec71d in ?? () from
/home/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#6  0xb6bec9c4 in ?? () from
/home/rravi/Desktop/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#7  0xb6bee733 in rpc__cn_sm_eval_event () from
/home/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#8  0xb6be97ad in ?? () from
/home/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#9  0xb6be9f37 in rpc__cn_network_receiver () from
/home/xadsd/opt/novell/xad/lib/libprot_ncacn.so
#10 0xb79162ab in start_thread () from
/home/xadsd/lib/libpthread.so.0
#11 0xb7887e0e in clone () from /home/xadsd/lib/libc.so.6

The xadsd crash happens in the mech_spnego library.
A defect has been filed and a patch will be released in the channel containing this fix some time in November 2009.  Until then please contact Novell Technical Support to received the updated mech_spnego.so libraries to resolve this issue.