Stacey,

Okay, got it.  Would you belive that portsentry caused nmbd to core dump when it
runs?

Rusty


Stacey Roberts(stacey) wrote:
> On Mon, 2002-12-30 at 02:14, Rusty Nejdl wrote:
> > I've tried the following versions of samba:
> > 
> > samba-2.2.4_1.tgz
> > samba-2.2.6.p2_1.tgz
> > samba-2.2.7a.tar.gz
> > samba-2.2.7a.tbz
> > samba-3.0a19.tgz
> > samba-3.0a20.tbz
> > 
> > All produce the same results.  I'm looking to see if there's just something I
> > changed on the way to installing my box that would cause this.  I'm not sure if
> > this the key to it or not:
> > 
> > [2002/12/29 19:30:01, 0] lib/util_sock.c:set_socket_options(165)
> >   Failed to set socket option SO_BROADCAST (Error Bad file descriptor)
> > 
> > Ideas?
> 
> Silly suggestion.
> 
> Is it possible for you to try:
> # cd /usr/ports/net/samba; make install clean
> 
> Unless you've got some other reason for not doing it like that, of
> course.
> 
> Regards,
> 
> Stacey
> 
> > 
> > Thanks!
> > Rusty Nejdl
> > 
> > Jack L. Stone(jackstone) wrote:
> > > At 01:39 AM 12.30.2002 +0000, Stacey Roberts wrote:
> > > >On Mon, 2002-12-30 at 01:32, Rusty Nejdl wrote:
> > > >> Ok, I'm completely stuck with this one.  I am trying to get Samba
> > > >> running on my FreeBSD 4.7 - Release computer.  Everytime I try to run
> > > >> any version of nmbd, it core dumps.  The config doesn't matter.  Now,
> > > >> of note is the fact that I did get Sambda running properly on this
> > > >> computer when I first installed it, but in the process of building the
> > > >> computer (installing more packages, configuring, and rebuilding a
> > > >> kernel) samba broke.
> > > >> 
> > > >> So, in knowing that, I used another computer to try to cause samba to
> > > >> break in the same way and I can't do it.  I installed all the same
> > > >> ports and rebuilt the kernel and nmbd still ran.  The only big
> > > >> difference was that I didn't get all of the processes configured and
> > > >> running.
> > > >> 
> > > >> Here's /var/log/log.nmbd using a debug level of 3:
> > > >> [2002/12/29 19:26:45, 0] nmbd/nmbd.c:main(794)
> > > >>   Netbios nameserver version 2.2.6pre2 started.
> > > >>   Copyright Andrew Tridgell and the Samba Team 1994-2002
> > > >> [2002/12/29 19:26:45, 3] param/loadparm.c:init_globals(1261)
> > > >>   Initialising global parameters
> > > >> [2002/12/29 19:26:45, 3] param/params.c:pm_process(577)
> > > >>   params.c:pm_process() - Processing configuration file
> > > >> "/usr/local/etc/smb.conf"
> > > >
> > > ><Huge snip>
> > > >
> > > >> 
> > > >> I recompiled libc.so.4 as a result of the above error and tried again.
> > > >>  No change. However, since I'm installing samba from a package, it
> > > >> shouldn't matter.  In addition, I have tried compiling from source
> > > >> different versions of samba and they all fail the same way.
> > > >> 
> > > >> I haven't found this posted anywhere else so I'm completely stumped. 
> > > >> Any ideas or help would be appreciated.
> > > >> 
> > > >> Sincerely,
> > > >> Rusty Nejdl
> > > >
> > > >Hi,
> > > >  Out of curiosity, is there a reason why you're not running the latest
> > > >version of samba? Or has 2.2.7_b already failed before this one?
> > > >
> > > >If the other box still has nmbd up and running fine, then I'd suggest
> > > >you load more and more services (that are on the failing box) until nmbd
> > > >cores.
> > > >
> > > >I'm no hacker, hence my avoidance of the core dump file :-)
> > > >
> > > >Regards,
> > > >
> > > >Stacey
> > > >> 
> > > 
> > > Some months ago, I was having frequent core dumps for nmbd and an upgrade
> > > of Samba cured it for me. Suggest the latest portupgrade....
> > > 
> > > Best regards,
> > > Jack L. Stone,
> > > Administrator
> > > 
> > > SageOne Net
> > > http://www.sage-one.net
> > > [EMAIL PROTECTED]
> -- 
> Stacey Roberts
> B.Sc (HONS) Computer Science
> 
> Web: www.vickiandstacey.com
> 
> 

-- 
Any technical problem can be overcome given enough time and money.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to