Hi there, I have three S4 servers running as AD DCs. In order to keep the sysvol share in sync I'm using crontab to run the following command: /usr/bin/rsync -PavAX --delete root@<masterPDC>:/var/lib/samba/sysvol/ /var/lib/samba/sysvol/ However everytime this command is run a couple of extra smbd processes are started on the <masterPDC> (between 2 and 5 processes) which never exit and just sit there taking up resources. So, quite quickly I had a system with over 500 smbd processes and no free memory which very abruptly fell over and stopped serving genuine clients. Has anyone else come across this issue/know what is causing it? I have taken some level 10 logs of the smbd processes that get formed. However I don't have access to them from my current location. I will email them in tomorrow from work. Thanks, Alex
On May 7, 2013 4:56 PM, "Alex Matthews" <qoole.samba at lillimoth.com> wrote:> > Hi there, > > I have three S4 servers running as AD DCs. > In order to keep the sysvol share in sync I'm using crontab to run thefollowing command:> > /usr/bin/rsync -PavAX --delete root@<masterPDC>:/var/lib/samba/sysvol//var/lib/samba/sysvol/> > However everytime this command is run a couple of extra smbd processesare started on the <masterPDC> (between 2 and 5 processes) which never exit and just sit there taking up resources. So, quite quickly I had a system with over 500 smbd processes and no free memory which very abruptly fell over and stopped serving genuine clients.> > Has anyone else come across this issue/know what is causing it? > > I have taken some level 10 logs of the smbd processes that get formed.However I don't have access to them from my current location. I will email them in tomorrow from work.> > Thanks, > > Alex > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/sambaAre you sure those are separate processes, and not simply threads? (Apologies for brief response; sending from phone.)
On Tue, 2013-05-07 at 21:55 +0100, Alex Matthews wrote:> Hi there, > > I have three S4 servers running as AD DCs. > In order to keep the sysvol share in sync I'm using crontab to run the > following command: > > /usr/bin/rsync -PavAX --delete root@<masterPDC>:/var/lib/samba/sysvol/ > /var/lib/samba/sysvol/ > > However everytime this command is run a couple of extra smbd processes > are started on the <masterPDC> (between 2 and 5 processes) which never > exit and just sit there taking up resources. So, quite quickly I had a > system with over 500 smbd processes and no free memory which very > abruptly fell over and stopped serving genuine clients. > > Has anyone else come across this issue/know what is causing it? > > I have taken some level 10 logs of the smbd processes that get formed. > However I don't have access to them from my current location. I will > email them in tomorrow from work.My best guess is that the winbind part of samba's AD DC is making a connection, but never closing it. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org