nmbd internal error (PR#22576)

Jeremy Allison jra at samba.org
Thu Feb 28 18:11:02 GMT 2002

On Thu, Feb 28, 2002 at 05:41:08PM -0800, Galen Sampson wrote:
> Hello,
> I recently had a couple of issues with nmbd and was asked to share them with
> this list.  I attempted to attach a core file and send it as an attachment to
> this list but the message was too large.  As a result I will just send some
> output I have gathered with gdb and show the world my configuration files. 
> This text file was generated in unix and as such has no carraige returns.  The
> standard windows word pad seems to handel it well for people whe need to view
> it in that environment.
> If there are any questions I still have my core file and debug binary.  Please
> email me directly with any of these questions since I am not a member of the
> samba mailing lists.  Hope this helps.
> GNU gdb 4.18
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/dbxread.c line 2629 in elfstab_build_psymtabs
> Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/dbxread.c line 935 in fill_symbuf
> Core was generated by `nmbd'.
> Program terminated with signal 6, Abort trap.
> Reading symbols from /usr/local/lib/libcups.so.2...done.
> Reading symbols from /usr/lib/libpam.so.1...done.
> Reading symbols from /usr/lib/libc.so.5...done.
> Reading symbols from /usr/lib/libssl.so.2...done.
> Reading symbols from /usr/lib/libcrypto.so.2...done.
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> #0  0x28132533 in kill () from /usr/lib/libc.so.5
> #0  0x28132533 in kill () from /usr/lib/libc.so.5
> #1  0x281846c2 in abort () from /usr/lib/libc.so.5
> #2  0x808b717 in smb_panic (why=0x80ae374 "internal error") at lib/util.c:1066
> #3  0x807b436 in fault_report (sig=11) at lib/fault.c:43
> #4  0x807b48d in sig_fault (sig=11) at lib/fault.c:63
> #5  0xbfbfffb4 in ?? ()
> #6  0x8059b3b in write_browse_list (t=0, force_write=1)
> ---Type <return> to continue, or q <return> to quit---
>     at nmbd/nmbd_serverlistdb.c:372
> #7  0x804b10c in sig_hup (sig=1) at nmbd/nmbd.c:93
> #8  0xbfbfffb4 in ?? ()
> #9  0x808b01f in become_daemon () at lib/util.c:601
> #10 0x804c1e8 in main (argc=2, argv=0xbfbffdcc) at nmbd/nmbd.c:822
> #11 0x804a86d in _start ()

Looking at this it looks like something happened in the
signal handling for SIGHUP. Was some process sending SIGHUP
to nmbd at the time ?

Examining nmbd it's nowhere near as robust w.r.t. signal
handling as smbd (we had to rework that when we moved to
the signal based messaging system). I will re-do the nmbd
signal handling - but not for 2.2.4, only for HEAD (3.x)
I think.


More information about the samba-technical mailing list