Hi, We have detected this error in samba 4.4.4 # cat /usr/local/samba/var/log.winbindd-idmap [2016/06/09 12:06:53.547280, 0] ../source3/lib/util_tdb.c:494(tdb_chainlock_with_timeout_internal) tdb_chainlock_with_timeout_internal: alarm (40) timed out for key dc.domain.com in tdb /usr/local/samba/var/lock/mutex.tdb [2016/06/09 12:06:53.547469, 0] ../source3/winbindd/winbindd_cm.c:1032(cm_prepare_connection) cm_prepare_connection: mutex grab failed for dc.domain.com [2016/06/09 12:07:33.578631, 0] ../source3/lib/util_tdb.c:494(tdb_chainlock_with_timeout_internal) tdb_chainlock_with_timeout_internal: alarm (40) timed out for key dc.domain.com in tdb /usr/local/samba/var/lock/mutex.tdb [2016/06/09 12:07:33.578896, 0] ../source3/winbindd/winbindd_cm.c:1032(cm_prepare_connection) cm_prepare_connection: mutex grab failed for dc.domain.com [2016/06/09 12:09:48.079144, 0] ../source3/lib/util_tdb.c:494(tdb_chainlock_with_timeout_internal) tdb_chainlock_with_timeout_internal: alarm (40) timed out for key dc.domain.com in tdb /usr/local/samba/var/lock/mutex.tdb [2016/06/09 12:09:48.079316, 0] ../source3/winbindd/winbindd_cm.c:1032(cm_prepare_connection) cm_prepare_connection: mutex grab failed for dc.domain.com I have tried in a new domain provisioned and in this cas mutex.tdb doesn't exist Another test is during upgrade samba 3 to samba 4 AD, in this case mutex.tdb, exist with old timestamp but same error described appears in log Is this correct? Reproduced compile samba 4.4.4 from sources ./configure make make install provision new domain start domain and view logs Thanks
With a new provisiones domain (not migrated form samba3) mutex.tdb doesn't exist What is mutex.tdb?
migrated from samba 3 to samba 4 AD, without whit files, It seems that is not needed or now works without this...