Bug 7208 - Very long time to connect to alternative DC
Summary: Very long time to connect to alternative DC
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.4
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 3.4.4
Hardware: x86 Linux
: P3 normal
Target Milestone: ---
Assignee: Stefan Metzmacher
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-04 04:18 UTC by remo
Modified: 2011-10-12 14:17 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description remo 2010-03-04 04:18:35 UTC 
We maintain a system that hold users repository on Win2008R2 Domain Controllers.
we use winbind to authenticate users with DC, to get groups information etc.

out Linux box is running RHEL5.3. we took off the stock samba (3.0.33) because of compatibility issues (PIPE_DISCONNECT) and installed 3.4.4.

in normal cases, all works well. but when there is a DC outage it takes winbind a very long time to regain functionality with another DC on the domain. this can take either 6 minutes, or sometime even longer.

during that time winbind is blocking.

if winbind is restarted - the alternative DC is found quickly, and all works well.
looks like there is some problems with the mechanisms that manage connections, detect dead server, and kill old connection and move to a new connection.

please advise!
Remo
Comment 1 Michael Adam 2010-03-31 16:21:21 UTC 
Thanks for your bug report!

Metze: can this be related to the winbindd reconnect bug you have recently investigated?
Comment 2 Stefan Metzmacher 2010-04-01 01:09:57 UTC 
Yes, looks very likely

Can you try the patches attached to bug 7295?
https://bugzilla.samba.org/show_bug.cgi?id=7295

Or use the current v3-5-test branch

I'm working on a backport for 3.4
Comment 3 remo 2010-04-06 06:56:48 UTC 
Will try the patch on 3.5 and see if it helps.
Comment 4 Stefan Metzmacher 2011-07-30 09:19:51 UTC 
Any results on this with 3.5.10?
Comment 5 Stefan Metzmacher 2011-07-30 09:23:10 UTC 
3.4.14 should also have the related fixes
Comment 6 Stefan Metzmacher 2011-10-12 14:17:33 UTC 
This should be in current 3.4.x, 3.5.x, 3.6.x and master