New To Mac-Forums?

Welcome to our community! Join the discussion today by registering your FREE account. If you have any problems with the registration process, please contact us!

Get your questions answered by community gurus Advice and insight from world-class Apple enthusiasts Exclusive access to members-only contests, giveaways and deals

Join today!

 
Start a Discussion
 

Mac-Forums Brief

Subscribe to Mac-Forums Brief to receive special offers from Mac-Forums partners and sponsors

Join the conversation RSS
OS X - Operating System General OS operation information and support

OS 10.4 - Samba-SIGTERM: going down...error


Post Reply New Thread Subscribe

 
Thread Tools
Taggard
Guest
 
Posts: n/a

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]:
[2006/09/19
01:23:28,0]/SourceCache/samba/samba-92.13/samba/source/nmbd/nmbd.c:terminate(56)
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.

Thank you.
QUOTE Thanks
cazabam

 
cazabam's Avatar
 
Member Since: Jun 06, 2006
Posts: 1,153
cazabam is a glorious beacon of lightcazabam is a glorious beacon of lightcazabam is a glorious beacon of lightcazabam is a glorious beacon of lightcazabam is a glorious beacon of lightcazabam is a glorious beacon of light
Mac Specs: MacBook 2.0GHz White, 512MB RAM, 60GB HDD

cazabam is offline
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.
QUOTE Thanks

Post Reply New Thread Subscribe


« Tell me about your first time... | Mac Noob with FS/XFree86 question »
Thread Tools

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off
Forum Jump

Similar Threads
Thread
Thread Starter
Forum
Replies
Last Post
Disk I/O error - General Hard Disk Slow Downs and Issues.. sunk976 Apple Notebooks 11 07-01-2009 02:51 AM
error message during weekly maintenance ajresovsky Schweb's Lounge 0 06-18-2006 06:11 PM
XCode (Help with error messages) First - Using the word "new" as a variable nickypaul OS X - Development and Darwin 7 02-26-2005 12:38 PM
Upgrading PERL Forum Setup, MySQL, etc. ssotti OS X - Development and Darwin 0 11-29-2003 12:16 PM
Terribly Annoying Applescript Error =-1753 CmdrGuard Running Windows (or anything else) on your Mac 3 08-17-2003 01:02 AM

All times are GMT -4. The time now is 02:26 PM.

Powered by vBulletin
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
X

Welcome to Mac-Forums.com

Create your username to jump into the discussion!

New members like you have made this community the ultimate source for your Mac since 2003!


(4 digit year)

Already a member?