I'm having problems when I restart the smb server with it not coming back up. As near as I can tell it's actually NMBD that's having the issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a When I issue: #service smb restart It says that it shut down and restarted ok, but then nobody can logon to the domain, so I issue it again and it tells me that it couldn't kill nmbd, but then it starts it OK, and I can get everyone on. There's also been a few times where it just stopped accepting logons, after accepting them for most of the day, so I restart it, and it tells me then that it couldn't kill nmbd either. testparm doesn't find anything wrong with my config. Does anybody know of a way to stabalize this? Thanks, Rick
Are you sure that all of the nmbd processes are actually stopping the first time you issue the command. I had to change the killproc command to killall on one system so that nmbd would actually be completely stopped. Dan ---------- Original Message ---------------------------------- From: "D. Rick Anderson" <ruger@acsnv.com> Reply-To: ruger@acsnv.com Date: Fri, 6 Jun 2003 10:58:33 -0700 (PDT)>I'm having problems when I restart the smb server with it not coming back >up. As near as I can tell it's actually NMBD that's having the issue. I'm >running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just >upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a > >When I issue: >#service smb restart > >It says that it shut down and restarted ok, but then nobody can logon to >the domain, so I issue it again and it tells me that it couldn't kill >nmbd, but then it starts it OK, and I can get everyone on. > >There's also been a few times where it just stopped accepting logons, >after accepting them for most of the day, so I restart it, and it tells me >then that it couldn't kill nmbd either. > >testparm doesn't find anything wrong with my config. Does anybody know of >a way to stabalize this? > >Thanks, > >Rick > > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >
killproc is defined in /etc/rc.d/init.d/functions that's called by the rc scripts. In my case it was only killing one nmbd while multiples were actually running. ---------- Original Message ---------------------------------- From: "D. Rick Anderson" <ruger@acsnv.com> Reply-To: ruger@acsnv.com Date: Fri, 6 Jun 2003 13:21:32 -0700 (PDT)>killproc doesn't even exist on this machine, yet it was how the script was >'attempting' to stop nmbd. I'm sure that the version (2.2.7a) installed >with RedHat must have been using just kill. > >I changed it to killall, but I'm going to wait until all of the users >logoff and go home before I start dorkin' around with it. > >Thanks! > >Rick > > >> Are you sure that all of the nmbd processes are actually stopping the >> first time you issue the command. I had to change the killproc command >> to killall on one system so that nmbd would actually be completely >> stopped. >> >> Dan >> >> ---------- Original Message ---------------------------------- >> From: "D. Rick Anderson" <ruger@acsnv.com> >> Reply-To: ruger@acsnv.com >> Date: Fri, 6 Jun 2003 10:58:33 -0700 (PDT) >> >>>I'm having problems when I restart the smb server with it not coming >>> back up. As near as I can tell it's actually NMBD that's having the >>> issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s >>> and I just upgraded Samba to 2.2.8a-1 after having this same problem >>> with 2.2.7a >>> >>>When I issue: >>>#service smb restart >>> >>>It says that it shut down and restarted ok, but then nobody can logon >>> to the domain, so I issue it again and it tells me that it couldn't >>> kill nmbd, but then it starts it OK, and I can get everyone on. >>> >>>There's also been a few times where it just stopped accepting logons, >>> after accepting them for most of the day, so I restart it, and it tells >>> me then that it couldn't kill nmbd either. >>> >>>testparm doesn't find anything wrong with my config. Does anybody know >>> of a way to stabalize this? >>> >>>Thanks, >>> >>>Rick >>> >>> >>> >>>-- >>>To unsubscribe from this list go to the following URL and read the >>> instructions: http://lists.samba.org/mailman/listinfo/samba >>> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: http://lists.samba.org/mailman/listinfo/samba > > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >
I think you might be helped by looking at the startup scripts and see just what is hapening. You don't need fancy scripts to start and stop samba. For example, here is all I have in mind: #!/bin/bash case "$1" in start) killall smbd killall nmbd /usr/local/samba/bin/smbd -D /usr/local/samba/bin/nmbd -D ;; stop) killall smbd killall nmbd ;; reload) kill -SIGHUP `cat /usr/local/samba/var/locks/smbd.pid` kill -SIGHUP `cat /usr/local/samba/var/locks/nmbd.pid` ;; *) echo Usage: echo start stop reload ;; esac exit 0 To find where your binaries are, just run: which smbd which nmbd To find where your logs and such are, this MIGHT help: strings `which smbd` | grep samba You can modify this to take into account your own configuration. You can also run nmbd from the command line and increase debugging to see what is happening in case nmbd is crashing. You can also look in your nmbd log. Joel On Fri, Jun 06, 2003 at 10:58:33AM -0700, D. Rick Anderson wrote:> I'm having problems when I restart the smb server with it not coming back > up. As near as I can tell it's actually NMBD that's having the issue. I'm > running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just > upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a > > When I issue: > #service smb restart > > It says that it shut down and restarted ok, but then nobody can logon to > the domain, so I issue it again and it tells me that it couldn't kill > nmbd, but then it starts it OK, and I can get everyone on. > > There's also been a few times where it just stopped accepting logons, > after accepting them for most of the day, so I restart it, and it tells me > then that it couldn't kill nmbd either. > > testparm doesn't find anything wrong with my config. Does anybody know of > a way to stabalize this? > > Thanks, > > Rick > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > I'm having problems when I restart the smb server with it not coming back > up. As near as I can tell it's actually NMBD that's having the issue. I'm > running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just > upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a > > When I issue: > #service smb restart > > It says that it shut down and restarted ok, but then nobody can logon to > the domain, so I issue it again and it tells me that it couldn't kill > nmbd, but then it starts it OK, and I can get everyone on. > > There's also been a few times where it just stopped accepting logons, > after accepting them for most of the day, so I restart it, and it tells me > then that it couldn't kill nmbd either. > > testparm doesn't find anything wrong with my config. Does anybody know of > a way to stabalize this? > > Thanks, > > Rick > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba
----- Original Message ----- From: "Alex" <sysadm@omniarch-ny.com> To: <ruger@acsnv.com> Sent: Friday, June 06, 2003 4:03 PM Subject: Re: [Samba] stability> I had similar problems about a year ago with 2.2.3a-- the problem was a > stale PID. > Long story short, when the smb script is call to start|restart Samba, nmbd > fails to start because the script looks for a running process. While the > process had long died off it never cleaned up the PID number from > /usr/local/samba/var/locks/ ...nmbd.pid and smbd.pid. > > Try to start nmbd manually.../usr/local/samba/bin/nmbd -D -- (RH may have > the binaries somewhere else 'whereis' for nmbd) see if you get errorstating> process is already running. > What worked for me was "rm /usr/local/samba/var/locks/nmbd.pid " then > restarting Samba > > I don't know the cause but Good Luck to Ya. > > alex > > ----- Original Message ----- > From: "D. Rick Anderson" <ruger@acsnv.com> > To: <samba@lists.samba.org> > Sent: Friday, June 06, 2003 4:21 PM > Subject: Re: [Samba] stability > > > > killproc doesn't even exist on this machine, yet it was how the scriptwas> > 'attempting' to stop nmbd. I'm sure that the version (2.2.7a) installed > > with RedHat must have been using just kill. > > > > I changed it to killall, but I'm going to wait until all of the users > > logoff and go home before I start dorkin' around with it. > > > > Thanks! > > > > Rick > > > > > > > Are you sure that all of the nmbd processes are actually stopping the > > > first time you issue the command. I had to change the killproccommand> > > to killall on one system so that nmbd would actually be completely > > > stopped. > > > > > > Dan > > > > > > ---------- Original Message ---------------------------------- > > > From: "D. Rick Anderson" <ruger@acsnv.com> > > > Reply-To: ruger@acsnv.com > > > Date: Fri, 6 Jun 2003 10:58:33 -0700 (PDT) > > > > > >>I'm having problems when I restart the smb server with it not coming > > >> back up. As near as I can tell it's actually NMBD that's having the > > >> issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s > > >> and I just upgraded Samba to 2.2.8a-1 after having this same problem > > >> with 2.2.7a > > >> > > >>When I issue: > > >>#service smb restart > > >> > > >>It says that it shut down and restarted ok, but then nobody can logon > > >> to the domain, so I issue it again and it tells me that it couldn't > > >> kill nmbd, but then it starts it OK, and I can get everyone on. > > >> > > >>There's also been a few times where it just stopped accepting logons, > > >> after accepting them for most of the day, so I restart it, and ittells> > >> me then that it couldn't kill nmbd either. > > >> > > >>testparm doesn't find anything wrong with my config. Does anybody know > > >> of a way to stabalize this? > > >> > > >>Thanks, > > >> > > >>Rick > > >> > > >> > > >> > > >>-- > > >>To unsubscribe from this list go to the following URL and read the > > >> instructions: http://lists.samba.org/mailman/listinfo/samba > > >> > > > -- > > > To unsubscribe from this list go to the following URL and read the > > > instructions: http://lists.samba.org/mailman/listinfo/samba > > > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba > > >
I've just had this and it drove me crazy for a couple of days - started after I had been editing the smb.conf on a remote machine, and the conf file was the same on all three of my Samba servers except for a few lines - turns out I'd managed to get a capital S in one of the paths - took ages to spot such a simple error.... -----Original Message----- From: D. Rick Anderson [mailto:ruger@acsnv.com] Sent: 06 June 2003 18:59 To: samba@lists.samba.org Subject: [Samba] stability I'm having problems when I restart the smb server with it not coming back up. As near as I can tell it's actually NMBD that's having the issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a When I issue: #service smb restart It says that it shut down and restarted ok, but then nobody can logon to the domain, so I issue it again and it tells me that it couldn't kill nmbd, but then it starts it OK, and I can get everyone on. There's also been a few times where it just stopped accepting logons, after accepting them for most of the day, so I restart it, and it tells me then that it couldn't kill nmbd either. testparm doesn't find anything wrong with my config. Does anybody know of a way to stabalize this? Thanks, Rick -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba