nmbd shuts down

Question

nmbd shuts down

Can anyone help me?

For some time now the nmbd part of samba is getting a sigterm (56) command from somwhere.

I can't seem to find any log files that help me understand why it is shutting down. Just changing the loging details and re saving the config in server admin is enough to start it again.

Most recently it would appear to be happening at almost exactly the same time everyday.

I have trawled through the internet and seen various references to the sig term (56) but so far no article has helped.

Thanks in advance......

G5 dual 2GHz, Mac OS X (10.4.10), server

Posted on Oct 12, 2007 5:21 AM

Reply

Answer 1

davidh

Level 4

1,896 points

Oct 12, 2007 8:38 AM in response to binaryburford

Please post a sample of the log entries raher than asking us to guess : )

Some signal info is here:
http://www.dartmouth.edu/~rc/classes/soft_dev/signal.html

Or you can run

cat /usr/include/sys/signal.h

However, I think "56" is specific to samba and nmbd.

It's not clear what "56" is referring to, but you can have a look at the following to understand that that message may be generated by nmbd itself:

http://www.opensource.apple.com/darwinsource/10.4.8.ppc/samba-100.4/samba/source /nmbd/nmbd.c

Reply

Answer 2

Oct 18, 2007 9:18 AM in response to davidh

Thanks for the reply, here is some log from a typical day...

[2007/10/10 13:10:06, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd synclists.c:sync_browselists(169)
Initiating browse sync for MAIN to WHOPPER(192.168.100.90)
[2007/10/10 13:10:06, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd synclists.c:sync_browselists(169)
Initiating browse sync for MSHOME to FATTY1(0.0.0.0)
[2007/10/10 13:10:06, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd synclists.c:completesync(283)
sync with WHOPPER(192.168.100.90) for workgroup MAIN completed (4 records)
[2007/10/10 13:10:06, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd synclists.c:completesync(283)
sync with FATTY1(0.0.0.0) for workgroup MSHOME completed (4 records)
[2007/10/10 13:10:22, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd browsesync.c:announce_local_master_browser_to_domain_masterbrowser(110)
announce local_master_browser_to_domain_masterbrowser:
We are both a domain and a local master browser for workgroup XLVIDEOUK. Do not announce to ourselves.
[2007/10/10 13:10:22, 2] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd browsesync.c:sync_withdmb(154)
sync withdmb:
Initiating sync with domain master browser BIGMAC2<20> at IP 192.168.100.17 for workgroup XLVIDEOUK
[2007/10/10 13:10:56, 0] /SourceCache/samba/samba-100.7/samba/source/nmbd/nmbd.c:terminate(56)
Got SIGTERM: going down...

This seems to happen almost exactly the same time every day..... I notice also that I get an nmbd shutdown if I start the VPN service on the same box.

Thanks again

Richard.

Reply

Answer 3

davidh

Level 4

1,896 points

Oct 18, 2007 12:13 PM in response to binaryburford

You'll probably need to make changes to your PCs to stop Master Browser arbitration problems.
Can happen just with a bunch of PCs on the same network.

Google for it (registry changes to be made on the PCs in order to not try to be a master browser).

On the Server, shut down Windows file-services, and edit
/etc/smb.conf (use nano/vi in the Terminal)
and change
os level = 8
to
os level = 255

then restart Windows file-services.

Reply

Answer 4

Nov 8, 2007 3:14 AM in response to davidh

I changed the os level to 255 as suggested, but to no avail.

After about 2 weeks of nmbd working, it has now starting shutting down every few minutes.

Thanks again

Richard

Reply

Answer 5

Nov 8, 2007 3:25 PM in response to binaryburford

I am getting this as well.
nmbd.c:terminate(56)
Got SIGTERM: going down...
At the same time every day.

Reply

Answer 6

Nov 9, 2007 11:56 PM in response to Doug Ellsley

Two days ago after nmbd shutdown, I restarted it from the command line. It has been up ever since.....

Maybe its server manager causing it to terminate...

strange!.....

Richard.

Reply

Answer 7

Nov 17, 2007 6:14 AM in response to binaryburford

more info...

nmbd stayed up until I changed some acl permissions to a share. NMBD shutdown immediately with the 56 code.

Again I restarted it with the command line and its stayed up ever since......

Reply