Bug 10108 - Winbind takes way too long to fail to cached logins if all AD servers down
Summary: Winbind takes way too long to fail to cached logins if all AD servers down
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.0.7
Hardware: All Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-22 15:53 UTC by shawn.starr@rogers.com
Modified: 2014-01-29 00:07 UTC (History)
0 users

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 shawn.starr@rogers.com 2013-08-22 15:53:21 UTC 
In the worst case situation, if you lose ALL of your AD servers, winbind takes a very, very long time to fail to iusing cached logins instead. 

I see of no way of forcing winbind to abort trying to contact an AD server if they're all down, that results in an unacceptable wait to log into a server.

Could we please have an option to let us set a timeout for when winbind will give up trying to see if a domain controller is available or if they're all down fail to local cached logins quicker somehow?

Thanks,
Shawn
Comment 1 Björn Jacke 2014-01-29 00:07:01 UTC 
can you provide a network sniff and a rough overview of the setup that you have in the case that you describe?