10-09-2006, 10:10 AM #1TaggardGuestSamba-SIGTERM: going down...error
We have a mac XServe server running OSX 10.4.7. It's primary use is as
a file server. Every so often (randomly), the windows XP Pro computers
on the network will stop connecting to the server. I will go to the
logs and look and I always notice in the "Windows Name Service Log"
(/var/log/samba/log.nmbd) a message that says [example below]:
Got SIGTERM: going down...
If I stop the Windows service and then start it again, the file server
works again with no problems (at least temporarily).
I am pretty sure this is the point when SAMBA has a problem, but Is
there more info that I can provide to help with troubleshooting this?
Area of Server Admin module that I am talking about: WINDOWS.
10-09-2006, 10:34 AM #2
It appears that the netbios naming daemon (nmbd) is actually being killed by something else. A SIGTERM is sent when a process it told to halt, as opposed to SIGSEGV which would occur if the software crashed with a segmentation fault, or SIGKILL if the process was forcibly brought down.
Try increasing the log level and see if anything immediately precedes the nmbd termination in any of the Samba log files. It may not be the nmbd log file itself that actually provides the clue as to what is causing this termination to happen.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By varghesema in forum OS X - Apps and GamesReplies: 0Last Post: 10-16-2009, 12:55 AM
By felixm in forum Internet, Networking, and WirelessReplies: 0Last Post: 02-15-2009, 11:21 AM
By NeoGreen in forum OS X - Apps and GamesReplies: 4Last Post: 11-29-2007, 02:58 PM
By dinkoarun in forum Internet, Networking, and WirelessReplies: 2Last Post: 05-29-2007, 10:18 PM
By euthymos in forum OS X - Operating SystemReplies: 3Last Post: 08-15-2006, 05:27 AM