Samba problem w/netbios-ns-udp server

Samba problem w/netbios-ns-udp server

Post by Bill Voigh » Thu, 14 Oct 1999 04:00:00



Guys,

I intermittently get the following error message from my v2.04 nmbd (Sol
7 server, SS5)

Oct 13 16:29:32 solargeek inetd[15450]: netbios-ns/udp server failing
(looping), service terminated

It causes samba -which works sometimes to quit working.  Sometimes
rebooting will fix it, sometimes it runs for quite a while.  I've
looked.

When I kill the daeamon and restart, a tail of log.nmbd yields the
following:

/cdrom/cdrom0 > tail /var/opt/samba/log.nmb
[1999/10/13 16:41:33, 1] nmbd/nmbd.c:(677)
  Netbios nameserver version 2.0.4b started.
  Copyright Andrew Tridgell 1994-1998
[1999/10/13 16:41:33, 0] lib/pidfile.c:(86)
  ERROR: nmbd is already running. File /var/opt/samba/locks/nmbd.pid
exists and process id 16062 is running.
[1999/10/13 16:41:34, 1] nmbd/nmbd.c:(677)
  Netbios nameserver version 2.0.4b started.
  Copyright Andrew Tridgell 1994-1998
[1999/10/13 16:41:34, 0] lib/pidfile.c:(86)
  ERROR: nmbd is already running. File /var/opt/samba/locks/nmbd.pid
exists and process id 16062 is running.

Near as I can figure, it's restarting.  I imagine that explains the
reference to looping in the error message above.

Any ideas?

BV

 
 
 

Samba problem w/netbios-ns-udp server

Post by Bill Voigh » Thu, 14 Oct 1999 04:00:00


Oops, I forgot to include the error message smbstatus returns:

Samba version 2.0.4b
Service      uid      gid      pid     machine
----------------------------------------------

ERROR: Failed to initialise share modes!
Can't initialise shared memory - exiting

BV


> Guys,

> I intermittently get the following error message from my v2.04 nmbd (Sol
> 7 server, SS5)

> Oct 13 16:29:32 solargeek inetd[15450]: netbios-ns/udp server failing
> (looping), service terminated

> It causes samba -which works sometimes to quit working.  Sometimes
> rebooting will fix it, sometimes it runs for quite a while.  I've
> looked.

> When I kill the daeamon and restart, a tail of log.nmbd yields the
> following:

> /cdrom/cdrom0 > tail /var/opt/samba/log.nmb
> [1999/10/13 16:41:33, 1] nmbd/nmbd.c:(677)
>   Netbios nameserver version 2.0.4b started.
>   Copyright Andrew Tridgell 1994-1998
> [1999/10/13 16:41:33, 0] lib/pidfile.c:(86)
>   ERROR: nmbd is already running. File /var/opt/samba/locks/nmbd.pid
> exists and process id 16062 is running.
> [1999/10/13 16:41:34, 1] nmbd/nmbd.c:(677)
>   Netbios nameserver version 2.0.4b started.
>   Copyright Andrew Tridgell 1994-1998
> [1999/10/13 16:41:34, 0] lib/pidfile.c:(86)
>   ERROR: nmbd is already running. File /var/opt/samba/locks/nmbd.pid
> exists and process id 16062 is running.

> Near as I can figure, it's restarting.  I imagine that explains the
> reference to looping in the error message above.

> Any ideas?

> BV


 
 
 

Samba problem w/netbios-ns-udp server

Post by Jack Spr » Thu, 14 Oct 1999 04:00:00




Quote:>Guys,

>I intermittently get the following error message from my v2.04 nmbd (Sol
>7 server, SS5)

>Oct 13 16:29:32 solargeek inetd[15450]: netbios-ns/udp server failing
>(looping), service terminated

This isn't a Samba error.

It's inetd.  Inetd will only spawn off a certain number of processes
in a second before it stops with a looping error.   The solution is to
change one of the fields in the inetd.conf line (or, better, not to
run Samba out of inetd).

I've seen this a lot with POP servers.   Hunt around the web for
"inetd looping error" -- you'll find the syntax.

Sprat

 
 
 

Samba problem w/netbios-ns-udp server

Post by Andrew Gabri » Thu, 14 Oct 1999 04:00:00




Quote:>Oops, I forgot to include the error message smbstatus returns:

>Samba version 2.0.4b
>Service      uid      gid      pid     machine
>----------------------------------------------

>ERROR: Failed to initialise share modes!
>Can't initialise shared memory - exiting

From the samba-bugs FAQ...

|3) Couldn't open status file STATUS..LCK
|
|If you run smbstatus before anyone has ever connected to your new
|Samba installation then you may get the error:
|
|  Couldn't open status file /var/lock/samba/STATUS..LCK
|
|or possibly the error:
|
| ERROR smb_shm_open : open failed with code No such file or directory
| ERROR: Failed to initialize share modes!
| Can't initialize shared memory - exiting
|
|both of these errors are harmless. The appropriate files and memory
|segments get automatically created the first time you connect to
|Samba. Try connecting with smbclient and you should find that
|smbstatus is happy after your first connection.

I have recently reported a similar fault in that issueing the
smbstatus command before any samba shares are accessed causes
smbstatus to allocate a semaphore which samba then refuses to
use. This will be fixed in 2.0.6 apparently.

--
Andrew Gabriel
Consultant Software Engineer

 
 
 

Samba problem w/netbios-ns-udp server

Post by Bill Voigh » Thu, 14 Oct 1999 04:00:00


Andrew,

Thanks for the info.   I note I didn't get this message when there were
connections active.

BV




> >Oops, I forgot to include the error message smbstatus returns:

> >Samba version 2.0.4b
> >Service      uid      gid      pid     machine
> >----------------------------------------------

> >ERROR: Failed to initialise share modes!
> >Can't initialise shared memory - exiting

> From the samba-bugs FAQ...

> |3) Couldn't open status file STATUS..LCK
> |
> |If you run smbstatus before anyone has ever connected to your new
> |Samba installation then you may get the error:
> |
> |  Couldn't open status file /var/lock/samba/STATUS..LCK
> |
> |or possibly the error:
> |
> | ERROR smb_shm_open : open failed with code No such file or directory
> | ERROR: Failed to initialize share modes!
> | Can't initialize shared memory - exiting
> |
> |both of these errors are harmless. The appropriate files and memory
> |segments get automatically created the first time you connect to
> |Samba. Try connecting with smbclient and you should find that
> |smbstatus is happy after your first connection.

> I have recently reported a similar fault in that issueing the
> smbstatus command before any samba shares are accessed causes
> smbstatus to allocate a semaphore which samba then refuses to
> use. This will be fixed in 2.0.6 apparently.

> --
> Andrew Gabriel
> Consultant Software Engineer

 
 
 

Samba problem w/netbios-ns-udp server

Post by Bob Farm » Thu, 14 Oct 1999 04:00:00






>>Guys,

>>I intermittently get the following error message from my v2.04 nmbd (Sol
>>7 server, SS5)

>>Oct 13 16:29:32 solargeek inetd[15450]: netbios-ns/udp server failing
>>(looping), service terminated

>This isn't a Samba error.

>It's inetd.  Inetd will only spawn off a certain number of processes
>in a second before it stops with a looping error.   The solution is to
>change one of the fields in the inetd.conf line (or, better, not to
>run Samba out of inetd).

>I've seen this a lot with POP servers.   Hunt around the web for
>"inetd looping error" -- you'll find the syntax.

>Sprat

The syntax is to put a ".x" after the "nowait" parameter, ie:

pop-3   stream  tcp     nowait.50000  root    /usr/sbin/tcpd    ipop3d

--

Computer Services, Sam Houston State University; Huntsville, TX

 
 
 

1. netbios-ns/udp server failing (Samba)??

Hello,

I installed Samba from the ports and uncommented the two lines
required to start the program from inetd. I receive that error
message... Any suggestion as to what I might overlooked?

In the mean time, I just started the Oreily book... But if anyone has
an answer...

Thanks, sincerely,

Gil G.

2. FS: PC equipment

3. netbios-ns/udp server failing (looping)

4. ps problem

5. samba, netbios-ns problem

6. print postscript, comes out as text

7. Failures in nmbd and netbios-ns/udp

8. Int 10h ?

9. inetd[291]: netbios-ns/udp: bind: Address already in use

10. SAMBA: netbios-ns errors

11. NETBIOS-DD-SERVER and NETBIOS-SCOPE dhcpd.conf ????

12. Bind resolve netbios names to samba wins server!