Samba4 - random crash

[Taylor, Jonn]

I updated to the latest master (Version 4.0.0alpha15-GIT-4ccb7e5) the
other day and the crash seems to have stopped, but now I get an error in
the log like these and then you can not access any of the shares.

Replicated 0 objects (0 linked attributes) for DC=taylortelephone,DC=com
[Thu Feb 10 07:56:36 2011 CST, 2
../source4/dsdb/repl/replicated_objects.c:581:dsdb_replicated_objects_commit()]
Replicated 0 objects (0 linked attributes) for DC=taylortelephone,DC=com
[Thu Feb 10 07:56:39 2011 CST, 2
../source4/smbd/process_standard.c:208:standard_terminate()]
standard_terminate: reason[NT_STATUS_END_OF_FILE]

[Thu Feb 10 07:56:45 2011 CST, 2
../source4/dsdb/repl/replicated_objects.c:581:dsdb_replicated_objects_commit()]
Replicated 0 objects (0 linked attributes) for DC=taylortelephone,DC=com
[Thu Feb 10 07:56:45 2011 CST, 2
../source4/dsdb/repl/replicated_objects.c:581:dsdb_replicated_objects_commit()]
Replicated 0 objects (0 linked attributes) for DC=taylortelephone,DC=com
[Thu Feb 10 07:56:48 2011 CST, 2
../source4/smbd/process_standard.c:208:standard_terminate()]
standard_terminate: reason[socket_get_remote_addr() failed]

After a restart everything is ok.

Jonn


On 01/31/2011 10:18 AM, Matthieu Patou wrote:
> On 31/01/2011 18:24, Taylor, Jonn wrote:
>>
>> On 01/31/2011 01:46 AM, Matthieu Patou wrote:
>>> On 31/01/2011 04:27, Taylor, Jonn wrote:
>>>> About once a week samba4 alpha 14 is randomly crashing.
>>>>
>>>> CentOS 5.5 x86_64
>>>> Samba4 alpha14 tar ball
>>>>
>>>> [Sat Jan 29 22:00:02 2011 CST, 0
>>>> ../librpc/rpc/dcerpc_smb.c:311:smb_write_callback()]
>>>> dcerpc_smb: write callback error
>>>> [Sat Jan 29 22:00:02 2011 CST, 0
>>>> ../../lib/util/debug.c:185:talloc_log_fn()]
>>>> talloc: double free error - first free may be at
>>>> ../librpc/rpc/dcerpc_smb.c:390
>>>> [Sat Jan 29 22:00:02 2011 CST, 0
>>>> ../../lib/util/debug.c:185:talloc_log_fn()]
>>>> Bad talloc magic value - double free
>>>> [Sat Jan 29 22:00:02 2011 CST, 0
>>>> ../../lib/util/fault.c:143:smb_panic()]
>>>> PANIC: Bad talloc magic value - double free
>>>> [Sat Jan 29 22:00:02 2011 CST, 0
>>>> ../../lib/util/fault.c:62:call_backtrace()]
>>>> BACKTRACE: 20 stack frames:
>>>>    #0 /usr/local/samba/lib/libsamba-util.so.0(call_backtrace+0x1c)
>>>> [0x2ac0181a1f4c]
>>>>    #1 /usr/local/samba/lib/libsamba-util.so.0(smb_panic+0x1f1)
>>>> [0x2ac0181a21eb]
>>>>    #2 /usr/local/samba/lib/samba/libtalloc-samba4.so.2
>>>> [0x2ac0189f8c5a]
>>>>    #3 /usr/local/samba/lib/samba/libtalloc-samba4.so.2
>>>> [0x2ac0189f8cd9]
>>>>    #4 /usr/local/samba/lib/samba/libtalloc-samba4.so.2
>>>> [0x2ac0189f8def]
>>>>    #5
>>>> /usr/local/samba/lib/samba/libtalloc-samba4.so.2(talloc_get_name+0x15)
>>>> [0x2ac0189fa3c0]
>>>>    #6
>>>> /usr/local/samba/lib/samba/libtalloc-samba4.so.2(talloc_check_name+0x33)
>>>>
>>>> [0x2ac0189fa450]
>>>>    #7 /usr/local/samba/lib/libdcerpc.so.0 [0x2ac0194e5bc6]
>>>>    #8 /usr/local/samba/lib/libdcerpc.so.0 [0x2ac01952add3]
>>>>    #9
>>>> /usr/local/samba/lib/samba/libauthkrb5-samba4.so(packet_recv+0x8f7)
>>>> [0x2ac01afbd840]
>>>>    #10 /usr/local/samba/lib/libdcerpc.so.0 [0x2ac019529b0f]
>>>>    #11 /usr/local/samba/lib/samba/libtevent-samba4.so.0
>>>> [0x2ac0187f1faa]
>>>>    #12 /usr/local/samba/lib/samba/libtevent-samba4.so.0
>>>> [0x2ac0187f2688]
>>>>    #13
>>>> /usr/local/samba/lib/samba/libtevent-samba4.so.0(_tevent_loop_once+0xdf)
>>>>
>>>> [0x2ac0187ee5bb]
>>>>    #14
>>>> /usr/local/samba/lib/samba/libtevent-samba4.so.0(tevent_common_loop_wait+0x1f)
>>>>
>>>>
>>>> [0x2ac0187ee7e0]
>>>>    #15
>>>> /usr/local/samba/lib/samba/libtevent-samba4.so.0(_tevent_loop_wait+0x25)
>>>>
>>>> [0x2ac0187ee89c]
>>>>    #16 /usr/local/samba/sbin/samba [0x40a4bb]
>>>>    #17 /usr/local/samba/sbin/samba [0x40a509]
>>>>    #18 /lib64/libc.so.6(__libc_start_main+0xf4) [0x35c761d994]
>>>>    #19 /usr/local/samba/sbin/samba [0x404429]
>>> Can you put your server under network trace so that we can understand
>>> which kind of request generate this pb ?
>>>
>>> Matthieu.
>>>
>>>
>>>
>> Yes, What kind of trace to you need?
> network trace: tcpdump -i any host ip_of_domain_controler -s 0 -w file -v
> This command has to be started on the DC.
>
>
> Matthieu.
>
> -- 
>
> Matthieu Patou
> Samba Team        http://samba.org
> Private repo      http://git.samba.org/?p=mat/samba.git;a=summary
>
>