[Samba] HELP: Samba server crashing on me

Sun Sep 6 21:17:48 MDT 2009

On 09/06/2009 10:12 PM, Timothy Normand Miller wrote:
> On Sun, Sep 6, 2009 at 10:54 PM, Jobst Schmalenbach<jobst at barrett.com.au> wrote:
>>
>> This is ONLY a guess:
>>
>>  * signal 11 means invalid memory reference, so I would check your RAM
>>   and even your harddisks, it could be a page fault.
>>   (find some other ram, put them in and run it for a while).
> 
> This problem is new and 100% reproducable.  I've tried rebooting,
> which should fix any intermittent problem.  Also the RAM is from
> Crucial, and I'm not doing any overclocking of any kind.  Everything
> else is 100% stable, except for samba, which crashes.
> 
> Turns out that it doesn't crash until a client tries to connect.
> 
>>
>>  * may, just maybe your problems from earlier "Unable to connect to CUPS server"
>>   have had too many pointer allocations/references that the next one in the
>>   chain crashed the server, fix this and check again.
> 
> That's the first thing I fixed.  Didn't help.  Any other ideas?
> 
> Apparently, the crash is here:
> 
>>> #6  dns_register_smbd_reply (dns_state=0x0, lfds=0x7ffff4963ed0,
>>> timeout=0x7ffff4964060) at smbd/dnsregister.c:171
> 
> I'm going to pull the source and see what's there.

Did you by any chance update glibc before this problem started to occur?

Samba is a user-space application.  If your whole system crashed this
suggests a symptomatic problem with either the hardware (memory or
motherboard) or else corrupt binaries (either kernel or system libraries).

- John T.

>>
>> this is what I would do first.
>> Jobst
>>
>>
>>
>> On Sun, Sep 06, 2009 at 10:44:01PM -0400, Timothy Normand Miller (theosib at gmail.com) wrote:
>>> For no reason that I can discover, my smb server has started crashing
>>> on me.  I'm really hoping someone help me out with this.  This is the
>>> relevant portion of the log:
>>>
>>> [2009/09/06 22:24:44,  0] smbd/server.c:main(1274)
>>>   smbd version 3.3.7 started.
>>>   Copyright Andrew Tridgell and the Samba Team 1992-2009
>>> [2009/09/06 22:24:44,  0] printing/print_cups.c:cups_connect(103)
>>>   Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No
>>> such file or directory
>>> [2009/09/06 22:24:44,  0] printing/print_cups.c:cups_connect(103)
>>>   Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No
>>> such file or directory
>>> [2009/09/06 22:26:09,  0] smbd/server.c:main(1274)
>>>   smbd version 3.3.7 started.
>>>   Copyright Andrew Tridgell and the Samba Team 1992-2009
>>> [2009/09/06 22:26:09,  0] printing/print_cups.c:cups_connect(103)
>>>   Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No
>>> such file or directory
>>> [2009/09/06 22:26:09,  0] printing/print_cups.c:cups_connect(103)
>>>   Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No
>>> such file or directory
>>> [2009/09/06 22:26:43,  0] lib/fault.c:fault_report(40)
>>>   ===============================================================
>>> [2009/09/06 22:26:43,  0] lib/fault.c:fault_report(41)
>>>   INTERNAL ERROR: Signal 11 in pid 16066 (3.3.7)
>>>   Please read the Trouble-Shooting section of the Samba3-HOWTO
>>> [2009/09/06 22:26:43,  0] lib/fault.c:fault_report(43)
>>>
>>>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
>>> [2009/09/06 22:26:43,  0] lib/fault.c:fault_report(44)
>>>   ===============================================================
>>> [2009/09/06 22:26:43,  0] lib/util.c:smb_panic(1673)
>>>   PANIC (pid 16066): internal error
>>> [2009/09/06 22:26:43,  0] lib/util.c:log_stack_trace(1777)
>>>   BACKTRACE: 8 stack frames:
>>>    #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f4fdfff6b10]
>>>    #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f4fdfff6c1d]
>>>    #2 /usr/sbin/smbd [0x7f4fdffe3e71]
>>>    #3 /lib/libpthread.so.0 [0x7f4fde09bef0]
>>>    #4 /usr/sbin/smbd(dns_register_smbd_reply+0x1c) [0x7f4fdfe59e3b]
>>>    #5 /usr/sbin/smbd(main+0x16e8) [0x7f4fe01f05cc]
>>>    #6 /lib/libc.so.6(__libc_start_main+0xe6) [0x7f4fdca49a26]
>>>    #7 /usr/sbin/smbd [0x7f4fdfde1339]
>>> [2009/09/06 22:26:43,  0] lib/fault.c:dump_core(231)
>>>   dumping core in /var/log/samba/cores/smbd
>>>
>>> I don't get much out of gdb:
>>>
>>> #0  0x00007f4fdca5d645 in raise (sig=<value optimized out>) at
>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:64
>>> 64      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
>>>         in ../nptl/sysdeps/unix/sysv/linux/raise.c
>>> (gdb) where
>>> #0  0x00007f4fdca5d645 in raise (sig=<value optimized out>) at
>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:64
>>> #1  0x00007f4fdca5eb63 in abort () at abort.c:88
>>> #2  0x00007f4fdffe38db in dump_core () at lib/fault.c:242
>>> #3  0x00007f4fdfff6d3b in smb_panic (why=<value optimized out>) at
>>> lib/util.c:1689
>>> #4  0x00007f4fdffe3e71 in sig_fault (sig=11) at lib/fault.c:46
>>> #5  <signal handler called>
>>> #6  dns_register_smbd_reply (dns_state=0x0, lfds=0x7ffff4963ed0,
>>> timeout=0x7ffff4964060) at smbd/dnsregister.c:171
>>> #7  0x00007f4fe01f05cc in main (argc=<value optimized out>,
>>> argv=<value optimized out>) at smbd/server.c:689
>>>
>>>
>>> Other things:
>>>
>>> - I did try stopping and restarting the service
>>> - I ran testparm, and it says my config is fine
>>>
>>> --
>>> Timothy Normand Miller
>>> http://www.cse.ohio-state.edu/~millerti
>>> Open Graphics Project
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>> --
>> Do Lipton Tea employees take coffee breaks?
>>
>>  | |0| |   Jobst Schmalenbach, jobst at barrett.com.au, General Manager
>>  | | |0|   Barrett Consulting Group P/L & The Meditation Room P/L
>>  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
> 
> 
> 

-- 
John H Terpstra

"If at first you don't succeed, don't go sky-diving!"