[Samba] winbindd stays at 100% CPU having joined a domain

[Volker Lendecke]

On Tue, May 05, 2009 at 09:43:36AM +0100, Thomas Adam wrote:
> [ Please would anyone replying to this maintain the Cc list here as my
> dear colleague is not subscribed to this mailing list. ]
> 
> Hello all,
> 
> I am trying to track down an oddity with winbindd.  We're using samba only
> to join a given domain -- so the config file is very minimal, as per:
> 
>  [global]
>  workgroup = TEDDYBEARS
>  netbios name = SMOOTHWALL
>  realm = TEDDYBEARS.LOCAL
>  security = ads
>  password server = ad.teddybears.local
>  winbind separator = /
>  winbind enum users = yes
>  winbind enum groups = yes
> 
> Shortly after joining a domain though, winbindd will suddenly start using
> 100% CPU and sit there.
> 
> Attaching strace to this process shows nothing -- literally, it's making
> no system calls whatsoever.  Attaching gdb to this running process and
> using "next" reveals that it's doing the following:
> 
> memcpy() -> tdb_read() -> tdb_find()

Very likely that is a corrupted tdb file, probably the
netsamlogon_cache.tdb. What kind of file system do you run
this on?

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba/attachments/20090505/12987544/attachment.bin