[Samba] Re: Winbindd Takes 100% CPU.
linuxaddict7 at gmail.com
Fri Mar 20 18:39:40 GMT 2009
On Fri, Mar 20, 2009 at 1:47 PM, Miguel Jinez <miguel.jinez at gmail.com>wrote:
> 2009/3/20 Linux Addict <linuxaddict7 at gmail.com>
> On Fri, Mar 20, 2009 at 10:46 AM, Linux Addict <linuxaddict7 at gmail.com
>> > Environment:
>> > RHEL4 U6
>> > Samba 3.2.8
>> > After the installation, Winbind is taking 100% CPU. A restart seems to
>> > most of the times, but cant figure out the reason winbind takes all CPU.
>> > there any bugs worked already. If not, please someone help me resolve
>> > Let me know what kind of logs you may need.
>> > ~LA
>> And also, When I stop winbindd(/etc/init.d/winbind stop), the command
>> complete successfully, but still the winbindd processes keep running. I
>> to run stop them multiple times to in order stop the winbind. Once the
>> winbind stopped, the cpu usage returns to normal
>> We have a problem like this, we found problems in nsswitch.conf (ERASE
> winbind in passwd, group and shadow if you have that)
> And the problem was detected too in smb.conf with the line:
> ldapsam:trusted = Yes
> Now we don't have this problem
Its somewhat inconsistent. I have log level 20 still dont see any errrors. I
recently added passdb backend = tdbsam and that seems to be causing issues
on few servers, but rest of the hosts seems to doing Ok.
I tried strace on winbindd, but dont see anything.
Is there way we can find out what winbindd spent so much time on CPU. Are
there any tools available?
More information about the samba