Winbindd using 100% of CPU. Any solution?

[Richard Sharpe]

On Wed, Dec 4, 2013 at 12:06 PM, Richard Sharpe
<realrichardsharpe at gmail.com> wrote:
>
> The build I got onto the customer system did not have the damn patch
> to dump core when we hit that problem.
>
> Trying again with a new build.

We got a hit or two:

[2013/12/16 13:28:21.454633,  0]
winbindd/winbindd_cache.c:3148(initialize_winbindd_cach
e)
  initialize_winbindd_cache: clearing cache and re-creating with
version number 2
[2013/12/16 13:28:21.933631,  0]
winbindd/winbindd_util.c:330(trustdom_list_done)
  Got invalid trustdom response:OIAA. Cannot get the SID for (NULL SID).
[2013/12/16 13:33:21.467075,  0]
winbindd/winbindd_util.c:330(trustdom_list_done)
  Got invalid trustdom response:OIAA. Cannot get the SID for (NULL SID).
[2013/12/16 13:33:21.469075,  0]
winbindd/winbindd_dual.c:1404(fork_domain_child)
  adding 0x8033730a0 to list at 0xeac360
[2013/12/16 13:33:21.473075,  0] lib/util.c:1117(smb_panic)
  PANIC (pid 3190): duplicate!
[2013/12/16 13:33:21.481075,  0] lib/util.c:1221(log_stack_trace)
  BACKTRACE: 10 stack frames:
   #0 0x5a51cc <smb_panic+108> at /usr/local/sbin/winbindd
   #1 0x4bcf48 <wb_child_domain+1224> at /usr/local/sbin/winbindd
   #2 0x4b92c3 <wb_child_request_send+291> at /usr/local/sbin/winbindd
   #3 0x5bdb09 <_tevent_queue_create+361> at /usr/local/sbin/winbindd
   #4 0x5bbef8 <tevent_common_loop_immediate+488> at /usr/local/sbin/winbindd
   #5 0x5b8a42 <run_events_poll+82> at /usr/local/sbin/winbindd
   #6 0x5b929b <get_timed_events_timeout+395> at /usr/local/sbin/winbindd
   #7 0x5ba50f <_tevent_loop_once+223> at /usr/local/sbin/winbindd
   #8 0x48a5d5 <main+2613> at /usr/local/sbin/winbindd
   #9 0x48702e <_start+142> at /usr/local/sbin/winbindd
[2013/12/16 13:33:21.481075,  0] lib/fault.c:372(dump_core)
  dumping core in /core

We are getting this consistently now.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)