> Description of problem: Winbindd creates excessive debug output > Version-Release number of selected component (if applicable): samba3x-winbind-3.5.4-0.83.el5_7.2 > How reproducible: Always. > Steps to Reproduce: 1. Configure a Samba server as member of an Active Directory. 2. Configure one or more shares. 3. Browse a share from another machine. > Actual results: The following entries are logged with debug level 0: Sep 2 08:30:57 samba01 winbindd[3822]: [2011/09/02 08:30:57.282848, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) Sep 2 08:30:57 samba01 winbindd[3822]: idmap_alloc module ldap already registered! Sep 2 08:30:57 samba01 winbindd[3822]: [2011/09/02 08:30:57.283017, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) Sep 2 08:30:57 samba01 winbindd[3822]: idmap_alloc module tdb already registered! Sep 2 08:30:57 samba01 winbindd[3822]: [2011/09/02 08:30:57.283049, 0] winbindd/idmap.c:149(smb_register_idmap) Sep 2 08:30:57 samba01 winbindd[3822]: Idmap module passdb already registered! Sep 2 08:30:57 samba01 winbindd[3822]: [2011/09/02 08:30:57.283081, 0] winbindd/idmap.c:149(smb_register_idmap) Sep 2 08:30:57 samba01 winbindd[3822]: Idmap module nss already registered! Since debug level is 0, these messages can not be filtered lowering the "log level" parameter at smb.conf. > Expected results: These messages should have a higher debug level so they could be filtered by the smb.conf "log level" parameter. > Additional info: These messages are harmless and expected due to the lazy initialization for idmap modules. http://samba.2283325.n4.nabble.com/Module-already-registered-td3002095.html Duplicate shares (the same directory being accessible through more than one share) are known to cause this too. This is not the case there though.
Created attachment 522367 [details] Raising debug level to avoid high verbosity. Attaching a proposed patch. Using debug level 5 as this is the one used when the registration is successful.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0156.html