[Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)

[Doug Sampson]

> -----Original Message-----
> From: Jeremy Allison [mailto:jra at samba.org]
> Sent: Thursday, September 10, 2009 05:47 PM
> To: Doug Sampson
> Cc: 'Jeremy Allison'; 'samba at lists.samba.org'
> Subject: Re: [Samba] Samba Panic when attempting to connect using OS X
> cli ent (3.3.7)
> 
> 
> On Thu, Sep 10, 2009 at 05:14:33PM -0700, Doug Sampson wrote:
> > > > >   
> ===============================================================
> > > > > [2009/09/04 12:26:19,  0] lib/fault.c:fault_report(41)
> > > > >   INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7)
> > > > >   Please read the Trouble-Shooting section of the Samba3-HOWTO
> > > > > [2009/09/04 12:26:19,  0] lib/fault.c:fault_report(43)
> > > > >   
> > > > >   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> > > > > [2009/09/04 12:26:19,  0] lib/fault.c:fault_report(44)
> > > > >   
> ===============================================================
> > > > > [2009/09/04 12:26:19,  0] lib/util.c:smb_panic(1673)
> > > > >   PANIC (pid 52669): internal error
> > > > > [2009/09/04 12:26:19,  0] lib/util.c:log_stack_trace(1777)
> > > > >   BACKTRACE: 15 stack frames:
> > > > >    #0 0x2b43c5 <smb_panic+133> at /usr/local/sbin/smbd
> > > > >    #1 0x29d27a <dump_core_setup+1594> at /usr/local/sbin/smbd
> > > > >    #2 0xbfbfffb4
> > > > >    #3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at
> > > > > /usr/local/lib/nss_wins.so.1
> > > > >    #4 0x207d28d4 <nsdispatch+452> at /lib/libc.so.7
> > > > >    #5 0x207d2230 <gethostbyaddr_r+240> at /lib/libc.so.7
> > > > >    #6 0x207d235f <gethostbyaddr+95> at /lib/libc.so.7
> > > > >    #7 0x207b51f6 <getipnodebyaddr+150> at /lib/libc.so.7
> > > > >    #8 0x207b3647 <getnameinfo+1191> at /lib/libc.so.7
> > > > >    #9 0x29f992 <sys_getnameinfo+98> at /usr/local/sbin/smbd
> > > > >    #10 0x2b92c9 <get_peer_name+345> at /usr/local/sbin/smbd
> > > > >    #11 0x2a4c76 <check_access+358> at /usr/local/sbin/smbd
> > > > >    #12 0xdde58 <smbd_process+72> at /usr/local/sbin/smbd
> > > > >    #13 0x4feb94 <main+8692> at /usr/local/sbin/smbd
> > > > >    #14 0x64949 <_start+137> at /usr/local/sbin/smbd
> > > 
> > > This looks like a problem with the interface
> > > between the nss wins plugin library on FreeBSD.
> > > 
> > > Remove "wins" from the "hosts:" line in your
> > > nsswitch.conf.
> > > 
> > > Jeremy.
> > > 
> > 
> > That did it. Removing 'wins' from the host: line allowed OS 
> X clients to
> > connect.
> > 
> > Is this unique to FreeBSD or to Samba in general? Or even 
> OS X clients?
> > 
> > What am I going to do for browsing while we operate in NT 
> domain model until
> > we upgrade to AD?
> 
> That doesn't have anything to do with browsing (smbd doesn't browse
> anyway). The 3.3.x code doesn't have the symbol 
> _nss_wins_freebsd_gethostbyname_r
> in it at all, so this doesn't look like our code.
> 
> Can you find out what package installed the libnss_wins.so library ?
> 
> Looks like it might have come from here:
> 
> http://www.nabble.com/-PATCH---FreeBSD-1--nss_wins-support-for
> -FreeBSD-td23910214.html
> 
> which is code that never made it into the main Samba tree. Is
> this part of the Samba FreeBSD ports system ?
> 
> 
> Jeremy.
> 

Not being a FreeBSD wizard, I'd hazard a guess that the nss_wins.so came
with the FreeBSD port of Samba 3.3.x. All of the other FBSD servers I'm
running here that does not have Samba installed doesn't have that file.

I'm not sure how to go about filing a bug report with Timur. Here's hoping
he reads this!

Am looking at using "name resolve order = hosts wins bcast" line in the
smb.conf file. Does it accept "dns" as well? Also, it looks like the Samba
server does check with the WINS server simply by parsing the "wins server =
x.x.x.x" line in smb.conf.

Thanks for your help, Jeremy.

~Doug