Project

General

Profile

Bug #35122

winbind does not always properly fail-over to next DC

Added by Andrew Walker about 1 year ago. Updated 6 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Andrew Walker
Category:
Services
Target version:
Seen in:
Severity:
Medium
Reason for Closing:
Not Applicable
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Setup ====
1) Join FreeNAS to domain with multiple DCs.
2) Use wbinfo --dc-info=<DOMAIN> to identify the DC winbind is communicating with.
3) Pause this DC's vm (or pull network cable)
4) Perform wbinfo -ping-dc until response happens, then use wbinfo --dc-info to verify that we're speaking to a new DC.

Step (4) sometimes will reveal that winbind isn't moving on to the next DC.


Related issues

Related to FreeNAS - Bug #32814: Active Directory fails is first DC/DNS goes downClosed
Related to FreeNAS - Feature #67728: Update to Samba 4.9.4Done

History

#1 Updated by Dru Lavigne about 1 year ago

  • Assignee changed from Release Council to Alexander Motin

#2 Updated by Alexander Motin about 1 year ago

  • Assignee changed from Alexander Motin to Timur Bakeyev

#3 Updated by Timur Bakeyev about 1 year ago

  • Status changed from Unscreened to Screened
  • Severity changed from New to Medium

Ok, this is one of the document 'em tickets.

It would be nice to find the real cause of such a sticky behavior, I've rencently found one bug in DNS querying code in Samba, was Linux specific, so I guess there are more like this.

Need more thorough debugging and test environment - waiting for the VMWare server delivery for better debugging purposes.

Meanwhile, AFAIK, Andrew implemented workaround in the AD monitor for such a situation.

#4 Updated by Andrew Walker 12 months ago

[2018/08/01 18:15:43.541403,  1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
  tdb(/var/lock/mutex.tdb): tdb_lock failed on list 103 ltype=3 (Interrupted system call)
[2018/08/01 18:15:43.541522,  0] ../source3/lib/util_tdb.c:497(tdb_chainlock_with_timeout_internal)
  tdb_chainlock_with_timeout_internal: alarm (40) timed out for key DC01.BALEBDREW.FUN in tdb /var/lock/mutex.tdb
[2018/08/01 18:15:43.541644,  1] ../source3/lib/server_mutex.c:97(grab_named_mutex)
  Could not get the lock for DC01.BALEBDREW.FUN
[2018/08/01 18:15:43.541809,  0] ../source3/winbindd/winbindd_cm.c:1028(cm_prepare_connection)
  cm_prepare_connection: mutex grab failed for DC01.BALEBDREW.FUN
[2018/08/01 18:15:43.541848,  1] ../source3/winbindd/winbindd_cm.c:1258(cm_prepare_connection)
  Failed to prepare SMB connection to DC01.BALEBDREW.FUN: NT_STATUS_POSSIBLE_DEADLOCK
[2018/08/01 18:16:29.651477,  1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
  tdb(/var/lock/mutex.tdb): tdb_lock failed on list 103 ltype=3 (Interrupted system call)
[2018/08/01 18:16:29.651702,  0] ../source3/lib/util_tdb.c:497(tdb_chainlock_with_timeout_internal)
  tdb_chainlock_with_timeout_internal: alarm (40) timed out for key DC01.BALEBDREW.FUN in tdb /var/lock/mutex.tdb
[2018/08/01 18:16:29.651741,  1] ../source3/lib/server_mutex.c:97(grab_named_mutex)
  Could not get the lock for DC01.BALEBDREW.FUN
[2018/08/01 18:16:29.651933,  0] ../source3/winbindd/winbindd_cm.c:1028(cm_prepare_connection)
  cm_prepare_connection: mutex grab failed for DC01.BALEBDREW.FUN
[2018/08/01 18:16:29.652073,  1] ../source3/winbindd/winbindd_cm.c:1258(cm_prepare_connection)
  Failed to prepare SMB connection to DC01.BALEBDREW.FUN: NT_STATUS_POSSIBLE_DEADLOCK
[2018/08/01 18:16:45.551454,  1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
  tdb(/var/lock/mutex.tdb): tdb_lock failed on list 103 ltype=3 (Interrupted system call)
[2018/08/01 18:16:45.551576,  0] ../source3/lib/util_tdb.c:497(tdb_chainlock_with_timeout_internal)
  tdb_chainlock_with_timeout_internal: alarm (40) timed out for key DC01.BALEBDREW.FUN in tdb /var/lock/mutex.tdb
[2018/08/01 18:16:45.551804,  1] ../source3/lib/server_mutex.c:97(grab_named_mutex)
  Could not get the lock for DC01.BALEBDREW.FUN
[2018/08/01 18:16:45.552109,  0] ../source3/winbindd/winbindd_cm.c:1028(cm_prepare_connection)
  cm_prepare_connection: mutex grab failed for DC01.BALEBDREW.FUN
[2018/08/01 18:16:45.552158,  1] ../source3/winbindd/winbindd_cm.c:1258(cm_prepare_connection)
  Failed to prepare SMB connection to DC01.BALEBDREW.FUN: NT_STATUS_POSSIBLE_DEADLOCK

#5 Updated by Timur Bakeyev 11 months ago

  • Related to Bug #32814: Active Directory fails is first DC/DNS goes down added

#6 Updated by Timur Bakeyev 11 months ago

  • Category changed from OS to Services

#7 Updated by Dru Lavigne 11 months ago

  • Assignee changed from Timur Bakeyev to John Hixson

#8 Updated by Dru Lavigne 9 months ago

  • Assignee changed from John Hixson to William Grzybowski

#9 Updated by William Grzybowski 9 months ago

  • Assignee changed from William Grzybowski to Andrew Walker

#12 Updated by Bug Clerk 7 months ago

  • Status changed from Screened to In Progress

#13 Updated by Andrew Walker 6 months ago

  • Status changed from In Progress to Ready for Testing
  • Target version changed from Backlog to 11.2-U2
  • Needs Merging changed from Yes to No

#15 Updated by Dru Lavigne 6 months ago

#16 Updated by Dru Lavigne 6 months ago

  • Status changed from Ready for Testing to Closed
  • Target version changed from 11.2-U2 to N/A
  • Reason for Closing set to Not Applicable

Also available in: Atom PDF