winbing looping

[Shane Watson]

Hi Team,

I am facing winbind performance issue. This is happening when pwgrd and winbindd are running simultaniously. Here winbindd loops (looping starts after running "nsquery passwd 12345" command. Here 12345 is invalid UID) with the following debug entries:

[, 10] nsswitch/winbindd_util.c:rescan_trusted_domains(321)
  rescan_trusted_domains
[, 10] nsswitch/winbindd_util.c:rescan_trusted_domains(323)
  rescan_trusted_domains: allow trusted domains disabled
[, 10] lib/events.c:event_add_timed(130)
  Added timed event "async_request_timeout": 62b240
[, 10] nsswitch/winbindd_util.c:rescan_trusted_domains(321)
  rescan_trusted_domains
[, 10] nsswitch/winbindd_util.c:rescan_trusted_domains(323)
  rescan_trusted_domains: allow trusted domains disabled
[, 10] lib/events.c:get_timed_events_timeout(298)
  timed_events_timeout: 299/999873
[, 10] lib/events.c:timed_event_destructor(65)
  Destroying timed event 62b240 "async_request_timeout"
[, 10] nsswitch/winbindd_cache.c:cache_retrieve_response(2522)
  Retrieving response for pid 21332
[, 10] nsswitch/winbindd_user.c:getpwuid_recv(417)
  uid2sid_recv: uid 99999 has sid S-1-22-1-12345
[, 3] nsswitch/winbindd_user.c:winbindd_getpwsid(208)
  Could not find domain for sid S-1-22-1-12345

I observed looping frequency as about 1 sec. 

 
We have nsswitch.conf content as 'files winbindd'  for passwd and group.

Below is the smb.conf file content.

[global]
        workgroup = MYDOM
        realm = MYDOM.XXX.YYY.ZZZ
        server string = Samba Server
        interfaces = 10.20.11.55
        bind interfaces only = Yes
        security = ADS
        update encrypted = Yes
        map to guest = Bad Uid
        password server = 10.20.11.11, *
        log level = 10
        syslog = 0
        log file = /var/opt/samba/log.%m
        max log size = 10000
        socket options = SO_KEEPALIVE=0
        preferred master = No
        domain master = No
        idmap uid = 1000-3000
        idmap gid = 1000-3000
        winbind use default domain = Yes
        read only = No
        short preserve case = No
        strict locking = Yes
        dos filetime resolution = Yes

I encountered this on samba-3.0.36 and onwards.

Is this a bug in samba ? Please let me know what is going wrong here.

--Shane