[Samba] Irregular crash of samba 3.6.6 (debian wheezy)

[Bill Arlofski]

On 05/19/14 02:44, Ivan Novosad wrote:
> Hi,
> 
>  
> We are using Samba3 as PDC. Sometimes (once a month, irregularly) Samba stop serving clients and log file looks like this:
> 
> …..
> 
> [2014/05/19 08:20:51.411247,  0] lib/fault.c:47(fault_report)
> 
>   ===============================================================
> 
> [2014/05/19 08:20:51.411576,  0] lib/fault.c:48(fault_report)
> 
>   INTERNAL ERROR: Signal 11 in pid 24222 (3.6.6)
> 
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
> 
> [2014/05/19 08:20:51.412014,  0] lib/fault.c:50(fault_report)
> 
>  
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> 
> [2014/05/19 08:20:51.412345,  0] lib/fault.c:51(fault_report)
> 
>   ===============================================================
> 
> [2014/05/19 08:20:51.412567,  0] lib/util.c:1117(smb_panic)
> 
>   PANIC (pid 24222): internal error
> 
> [2014/05/19 08:20:51.423718,  0] lib/util.c:1221(log_stack_trace)
> 
>   BACKTRACE: 36 stack frames:
> 
>    #0 /usr/sbin/smbd(log_stack_trace+0x1a) [0x7f74be32c59a]
> 
>    #1 /usr/sbin/smbd(smb_panic+0x22) [0x7f74be32c672]
> 
>    #2 /usr/sbin/smbd(+0x422844) [0x7f74be31d844]
> 
>    #3 /lib/x86_64-linux-gnu/libc.so.6(+0x324f0) [0x7f74baca94f0]
> 
>    #4 /usr/sbin/smbd(tcopy_passwd+0x22) [0x7f74be305172]
> 
>    #5 /usr/sbin/smbd(pdb_copy_sam_account+0x76) [0x7f74be2ca0f6]
> 
>    #6 /usr/sbin/smbd(pdb_getsampwsid+0xa5) [0x7f74be2cd2d5]
> 
>    #7 /usr/sbin/smbd(_samr_OpenUser+0x161) [0x7f74be204691]
> 
>    #8 /usr/sbin/smbd(+0x319875) [0x7f74be214875]
> 
>    #9 /usr/sbin/smbd(+0x32a1c6) [0x7f74be2251c6]
> 
>    #10 /usr/sbin/smbd(dcerpc_binding_handle_raw_call_send+0x9e) [0x7f74be39e9ae]
> 
>    #11 /usr/sbin/smbd(dcerpc_binding_handle_call_send+0x258) [0x7f74be39f198]
> 
>    #12 /usr/sbin/smbd(dcerpc_binding_handle_call+0x77) [0x7f74be39f2c7]
> 
>    #13 /usr/sbin/smbd(dcerpc_samr_OpenUser_r+0x1d) [0x7f74be2983cd]
> 
>    #14 /usr/sbin/smbd(dcerpc_samr_OpenUser+0x1d) [0x7f74be2985fd]
> 
>    #15 /usr/sbin/smbd(+0x2bc58b) [0x7f74be1b758b]
> 
>    #16 /usr/sbin/smbd(_netr_ServerAuthenticate3+0x222) [0x7f74be1b8582]
> 
>    #17 /usr/sbin/smbd(+0x2c2a76) [0x7f74be1bda76]
> 
>    #18 /usr/sbin/smbd(+0x3260a5) [0x7f74be2210a5]
> 
>    #19 /usr/sbin/smbd(process_complete_pdu+0x89b) [0x7f74be22280b]
> 
>    #20 /usr/sbin/smbd(process_incoming_data+0x118) [0x7f74be223698]
> 
>    #21 /usr/sbin/smbd(np_write_send+0x150) [0x7f74be223d70]
> 
>    #22 /usr/sbin/smbd(reply_pipe_write_and_X+0x165) [0x7f74be0390e5]
> 
>    #23 /usr/sbin/smbd(reply_write_and_X+0x348) [0x7f74be042948]
> 
>    #24 /usr/sbin/smbd(+0x18a2dc) [0x7f74be0852dc]
> 
>    #25 /usr/sbin/smbd(+0x18a6e2) [0x7f74be0856e2]
> 
>    #26 /usr/sbin/smbd(+0x18ab21) [0x7f74be085b21]
> 
>    #27 /usr/sbin/smbd(run_events_poll+0x353) [0x7f74be33c073]
> 
>    #28 /usr/sbin/smbd(smbd_process+0x84a) [0x7f74be08728a]
> 
>    #29 /usr/sbin/smbd(+0x69f913) [0x7f74be59a913]
> 
>    #30 /usr/sbin/smbd(run_events_poll+0x353) [0x7f74be33c073]
> 
>    #31 /usr/sbin/smbd(+0x44120a) [0x7f74be33c20a]
> 
>    #32 /usr/sbin/smbd(_tevent_loop_once+0x90) [0x7f74be33cd70]
> 
>    #33 /usr/sbin/smbd(main+0xf30) [0x7f74be005890]
> 
>    #34 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f74bac95ead]
> 
>    #35 /usr/sbin/smbd(+0x10accd) [0x7f74be005ccd]
> 
> [2014/05/19 08:20:51.427991,  0] lib/fault.c:372(dump_core)
> 
>   dumping core in /data/pdc.vyroba/log/cores/smbd
> 
> [2014/05/19 08:20:51.459351,  0] rpc_server/netlogon/srv_netlog_nt.c:931(_netr_ServerAuthenticate3)
> 
>   _netr_ServerAuthenticate3: no challenge sent to client V4105-SENESI 
> 
> ….
> 
>  
> Details about instalations:
> 
> Debian wheezy (uname –a      Linux Xena 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux)
> 
> Samba is from official repository (samba 3.6.6-6-+deb7u2)
> 
>  
> Where can I find more information, where the problem is?
> 
> What can I do to solve this problem?
> 
>  
> Thanks.
> 
>  
> Ivan Novosad
> 



Ivan, I have reported this same issue at least once on this list. The problem
is the same as yours (monthly, or randomly) each smbd process spawned to
handle a domain login crashes and core dumps.  No idea what triggers this, but
once it starts no new logins work until we restart samba (make sure all  smbd
and nmbd processes are killed off and then restart)

While this is going on, anyone already connected seems to be able to go about
their business accessing the fileserver with no problems.


We have been seeing this since 3.6.? and have upgraded several times to 3.6.23
and the problem still haunts us.

Linux distro is Gentoo here.

Hope you find the answer. I'll be watching this thread along with the one I
created, and will help with any info I can.


Bill


-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything after this line --