thr3ads.net - samba - [Samba] 3.0.25 Winbind high CPU usage [May 2007]

If this information is useful, please help other people find it:
Share via:

Jason Lanclos

2007-May-18 16:35 UTC

[Samba] 3.0.25 Winbind high CPU usage

I just upgraded from 3.0.23d to 3.0.25 and I'm noticing that winbind is
chewing up a lot of CPU usage.

There are always 2 winbindd processes and one uses about 80% cpu and the
other use 15% cpu.

When I run a tcpdump and look at the traffic going to/from the domain
controller winbindd is connected to, there is a constant flow of
traffic.


Here is the winbind setup from my smb.conf file:

   #idmap uid = 16777216-33554431
   #idmap gid = 16777216-33554431
   allow trusted domains = no
   #idmap backend = idmap_rid:WORKGROUP=16777216-33554431
   idmap alloc backend = tdb

   idmap domains = WORKGROUP
   idmap config WORKGROUP: default =    yes
   idmap config WORKGROUP: backend =    rid
   idmap config WORKGROUP: read_only = yes
   idmap config WORKGROUP: range = 16777216-33554431
   idmap alloc config: range = 16777216-33554431

   winbind offline logon = true
   winbind nested groups = no
   winbind enum users = yes
   winbind enum groups = yes
   winbind cache time = 900
   #winbind cache time = 300
   template shell = /bin/bash
   winbind use default domain = yes
   password server = print.ldaf.state.la.us dc2.ldaf.state.la.us
usershare.ldaf.state.la.us agchem.ldaf.state.la.us *
   realm = LDAF.STATE.LA.US
   template homedir = /data/HomeDirectories/%U




Lookin at the smbd logs I'm seeing a lot of user lookups for Shares...
DocumentImaging and OfficeDirectories are Shares..

[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user dOcUMenTimagING
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam dOcUMentIMAGing
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user docUMentImaginG
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam docUMentiMAging
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user ofFIcEdirEctoRies
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam ofFIcEdirEctorIes
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user dOCUMenTimAgiNG
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam dOCUMenTimaGINg
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user dOcuMeNtimAgIng
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam dOcuMeNtimAgiNg
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user OFFicEdirECtoriEs
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam OFFicEdirECtorieS
[2007/05/18 11:21:06, 5] nsswitch/winbindd_async.c:lookupname_recv2(801)
  lookup_name returned an error
[2007/05/18 11:21:06, 5]
nsswitch/winbindd_user.c:getpwnam_name2sid_recv(390)
  Could not lookup name for user DoCumentIMAGinG
[2007/05/18 11:21:06, 3] nsswitch/winbindd_user.c:winbindd_getpwnam(346)
  [    0]: getpwnam DoCumentIMAgINg


There are also a lot of lookups being logged in wb-BUILTIN log
==> /var/log/samba/log.wb-BUILTIN <=[2007/05/18 11:24:41, 4]
nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:41, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544
[2007/05/18 11:24:41, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:41, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-545
[2007/05/18 11:24:42, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:42, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544
[2007/05/18 11:24:42, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:42, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-545
[2007/05/18 11:24:42, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:42, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544
[2007/05/18 11:24:42, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:42, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-545
[2007/05/18 11:24:43, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:43, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-546
[2007/05/18 11:24:43, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:43, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544
[2007/05/18 11:24:43, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:43, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-545
[2007/05/18 11:24:44, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:44, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544
[2007/05/18 11:24:45, 4] nsswitch/winbindd_dual.c:fork_domain_child(989)
  child daemon request 20
[2007/05/18 11:24:45, 3]
nsswitch/winbindd_async.c:winbindd_dual_lookupsid(754)
  [29981]: lookupsid S-1-5-32-544


Any ideas of whats going on with this?


Thanks,

Jason Lanclos - RHCE
Systems Administrator
Louisiana Department of Agriculture and Forestry

Gerald (Jerry) Carter

2007-May-18 17:07 UTC

head link

[Samba] 3.0.25 Winbind high CPU usage

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Lanclos wrote:> I just upgraded from 3.0.23d to 3.0.25 and I'm noticing that winbind is
> chewing up a lot of CPU usage.
> 
> There are always 2 winbindd processes and one uses about 80% cpu and the
> other use 15% cpu.
> 
> When I run a tcpdump and look at the traffic going to/from the domain
> controller winbindd is connected to, there is a constant flow of
> traffic.
> 
> 
> Here is the winbind setup from my smb.conf file:
> 
>    #idmap uid = 16777216-33554431
>    #idmap gid = 16777216-33554431
>    allow trusted domains = no
>    #idmap backend = idmap_rid:WORKGROUP=16777216-33554431
>    idmap alloc backend = tdb
> 
>    idmap domains = WORKGROUP
>    idmap config WORKGROUP: default =    yes
>    idmap config WORKGROUP: backend =    rid
>    idmap config WORKGROUP: read_only = yes
>    idmap config WORKGROUP: range = 16777216-33554431
>    idmap alloc config: range = 16777216-33554431
> 
>    winbind offline logon = true
>    winbind nested groups = no
>    winbind enum users = yes
>    winbind enum groups = yes
>    winbind cache time = 900
First I would disable thwe winbindd enum users/group options.
Second, you might want to push the "idmap cache time" and
"idmap negative cache time" value up from their default values.

Finally, I have it on my TODO list to move the winbindd and
idmap cache managers into the main winbindd proces so we don't
have to cross process boundaries unless we actually hitting
the backend (i.e. xpired cache entries).

Can you give me a better idea of what is going on in smbd
and other applications running on the server?






cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGTd1MIR7qMdg1EfYRAoJMAJ9Nye7WhjjOOklNJsVbTfGCBSSn9ACgsCeq
KgPypRDG/SoGuhyb0J1A1BA=oc5C
-----END PGP SIGNATURE-----

Reasonably Related Threads

Search for more possibly parallel threads

samba - May 2007 - 3.0.25 Winbind high CPU usage

[Samba] 3.0.25 Winbind high CPU usage

[Samba] 3.0.25 Winbind high CPU usage

Reasonably Related Threads