Bug 3572 - winbind crash version 3.0.9-1.3E.5
winbind crash version 3.0.9-1.3E.5
Status: RESOLVED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: winbind
3.0.9
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-02 09:08 UTC by valter
Modified: 2006-03-02 09:18 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description valter 2006-03-02 09:08:52 UTC
smbd version 3.0.9-1.3E.5
winbindd version 3.0.9-1.3E.5
Linux TDFSERVER 2.4.21-37.ELsmp #1 SMP Wed Sep 7 13:28:55 EDT 2005 i686 i686 i386 GNU/Linux

winbind crash about once a week with the following messages:

[2006/03/02 05:01:00, 3] libads/ldap.c:ads_do_paged_search(479)
ldap_search_ext_s((objectclass=*)) -> Can't contact LDAP server
[2006/03/02 05:01:00, 3] libads/ldap_utils.c:ads_do_search_retry(66)
  Reopening ads connection to realm 'THINK3.COM' after error Can't contact LDAP server
[2006/03/02 05:01:00, 3] libads/ldap.c:ads_connect(247)
  Connected to LDAP server 192.168.3.6
[2006/03/02 05:01:01, 3] libads/ldap.c:ads_server_info(2432)
  got ldap server name pddc2@THINK3.COM, using bind path: dc=THINK3,dc=COM
[2006/03/02 05:01:01, 3] libads/sasl.c:ads_sasl_spnego_bind(204)
  ads_sasl_spnego_bind: got OID=1 3 6 1 4 1 311 2 2 10
[2006/03/02 05:01:
01, 3] libads/sasl.c:ads_sasl_spnego_bind(211)
  ads_sasl_spnego_bind: got server principal name =pddc2$@THINK3.COM
[2006/03/02 05:01:01, 3] libsmb/clikrb5.c:ads_cleanup_expired_creds(319)
  Ticket in ccache[MEMORY:winbind_ccache] expiration Thu, 02 Mar 2006 05:01:01 GMT
[2006/03/02 05:01:01, 0] lib/fault.c:fault_report(36)
  ===============================================================
[2006/03/02 05:01:01, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 6 in pid 5428 (3.0.9-1.3E.5)
  Please read the appendix Bugs of the Samba HOWTO collection
[2006/03/02 05:01:01, 0] lib/fault.c:fault_report(39)
  ===============================================================

If the crash may be related to the message 'Can't contact LDAP server', how can I force the usage of a different LDAP server?

thanks for your support,
Valter
Comment 1 Gerald (Jerry) Carter 2006-03-02 09:18:52 UTC
Please try to reproduce again 3.0.21c and reopen if the bug 
still exists.  If you need a patch for 3.0.9, you'll need 
to contact RedHat.