s4 crash: talloc: double free error - first free may be at ../dsdb/common/util.c:2705
Matthieu Patou
mat at samba.org
Mon Jun 21 03:02:31 MDT 2010
On 21/06/2010 12:49, Michael Wood wrote:
> Should I report this here or rather file a bug report in bugzilla?
> (The last crash report I sent to the list was ignored.)
>
>
Yes please.
> Last week I compiled 65ca3e4, vampired from a Win2k3 machine, and left
> it running over the weekend. There have been a couple of other
> instances of Samba4 that have vampired the domain before. Nothing was
> happening on the domain over the weekend, i.e. no added/deleted users
> etc.
>
> This morning there's a zombie samba process and its parent is:
>
> /usr/local/samba/sbin/samba -i -M single -d10
>
> In the window where I started Samba I see this:
>
> [...]
> queued DsReplicaSync for DC=xyz to
> bd0034a8-6252-4b42-ba54-1270a66630c4._msdcs.xyz (urgent=false)
> uSN=0:3244
> queued DsReplicaSync for DC=xyz to
> 4a86865e-403e-4aa1-b3b5-f8508ba9c873._msdcs.xyz (urgent=false)
> uSN=0:3244
> dreplsrv_notify_schedule(5) scheduled for: Fri Jun 18 19:18:57 2010 SAST
> Timed out smb_krb5 packet
> Received smb_krb5 packet of length 154
> talloc: double free error - first free may be at ../dsdb/common/util.c:2705
> Bad talloc magic value - double free
> PANIC: Bad talloc magic value - double free
> *** glibc detected *** /usr/local/samba/sbin/samba: corrupted
> double-linked list: 0x0000000002691e20 ***
>
> I've attached to the process with gdb and done a bt full (see
> attached). What else should I do to find out what caused this?
>
>
--
Matthieu Patou
Samba Team http://samba.org
More information about the samba-technical
mailing list