winbind consumes 100% CPU and unable to authenticate users

Solution Verified - Updated -

Issue

Winbind process jumps to 100% CPU usage.
Unable to query or authenticate users to the domain.
The only way we can restart Winbind and re-establish connection to the domain is killing winbind processes with a SIGKILL.
Customer experienced some network issues in their network just before they started noticing this issue.

errors seen in samba logs :

Dec  6 00:11:58 xxx winbindd[28119]:   Got invalid trustdom response
Dec  6 00:12:58 xxx winbindd[27547]: [2012/12/06 00:12:58.284851,  0] winbindd/winbindd_util.c:325(trustdom_recv)
Dec  6 00:12:58 xxx winbindd[27547]:   Got invalid trustdom response
Dec  6 00:12:59 xxx winbindd[28512]: [2012/12/06 00:12:59.214147,  0] winbindd/winbindd_util.c:325(trustdom_recv)
Dec  6 00:12:59 xxx winbindd[28512]:   Got invalid trustdom response

Environment

  • Red Hat Enterprise Linux 6.3
  • samba-3.5.10-125.el6.x86_64
  • samba-winbind-clients-3.5.10-125

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content