Bug 10108 - Winbind takes way too long to fail to cached logins if all AD servers down
Winbind takes way too long to fail to cached logins if all AD servers down
Status: NEW
Product: Samba 4.0
Classification: Unclassified
Component: Winbind
4.0.7
All Linux
: P5 normal
: ---
Assigned To: Samba QA Contact
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
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

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?