samba - Dec 1997 - SUMMARY: netbios-ns address already in use?

My original message follows...

Well, it would seem that my problem was that nmbd was somehow running as a
daemon.  Looking at the process IDs the first nmbd had a parent process of
1, not as the ID of inetd.  I don't know HOW that happened, the only place
nmbd is referenced is inetd.conf.  I killed the main nmbd process, sent a
HUP signal to inetd, nmbd started again and I haven't had a problem in
over 5 hours (where I was getting the message every 10 minutes before).
So, I guess everything is now OK.  Strange...

---------------------------------------------------------------------
|  Tim Winders, CNE              |  Email:  twinders@spc.cc.tx.us   |
|  Network Administrator         |  Phone:  806-894-9611 x 2369     |
|  South Plains College          |  Fax:    806-897-4711            |
---------------------------------------------------------------------

*************** Original message ****************
>
>I was just browsing through my logs and noticed this many times:
>
>Dec  2 14:00:37 barney inetd[3021]: netbios-ns/udp: bind: Address already
>in use
>
>netbios-ns should run on port 137/udp right?  This is the samba nmbd
>server, right?  When I do a ps -fe |grep nmbd I see this:
>
>root       708     1  0.0   Nov 26 ??           3:52.39 nmbd -n Alpha_1000
>root       709   708  0.0   Nov 26 ??           0:00.01 nmbd -n Alpha_1000
>
>So, nmbd is already running... IF it is already running, why are these
>error showing up in the daemon.log file?
>
>I am running 1.9.18alpha11 on Digital Unix 4.0b
>
>Thanks!

> My original message follows...
> 
> Well, it would seem that my problem was that nmbd was somehow running as a
> daemon.  Looking at the process IDs the first nmbd had a parent process of
> 1, not as the ID of inetd.  I don't know HOW that happened, the only
place
> nmbd is referenced is inetd.conf.  I killed the main nmbd process, sent a
> HUP signal to inetd, nmbd started again and I haven't had a problem in
> over 5 hours (where I was getting the message every 10 minutes before).
> So, I guess everything is now OK.  Strange...
> 
Uhhmmm... process ID 1 is init. That's the first process run by the
kernel. My guess is that one of your rc scripts is starting nmbd.
After you killed nmbd it was restarted automatically by inetd when
there was traffic in the netbios ports. Try rebooting the machine: the
rc script will restart nmbd again and then when inetd tries to run
nmbd because of UDP traffic it'll find the port already in use, so
you'll have the same problem again.

See ya!

E.-

-- 

Eloy A. Paris
Information Technology Department
Rockwell Automation de Venezuela
Telephone: +58-2-9432311 Fax: +58-2-9431645