s3:pdb_tdb and winbind_idmap.tdb
abenaguev at gmail.com
Tue Dec 16 15:24:24 GMT 2008
Stefan (metze) Metzmacher wrote:
> I noticed pdb_tdb still uses winbind_idmap.tdb to store the "RID_COUNTER".
> That's very bad by design and also breaks cluster installations
> as winbind_idmap.tdb isn't syncronized between nodes, while
> passdb.tdb is.
I have a lot of problems with winbind in clustered 3.3.0rc2. Like
inability to join all nodes in domain simultaneously or winbind's
inability to enumerate all users (getent shows only 11 from 23) with
cool messages in logs:
idmap_sid_to_uid: sid =
[S-1-5-21-2361374977-3643918947-1229681082-1129], domain = 'PROFINVEST'
Returning expired cache entry: key =
IDMAP/SID2UID/S-1-5-21-2361374977-3643918947-1229681082-1129, value =
-1, timeout = Tue Dec 16 17:57:20 2008
UID = -1 it's very strange (for me). may be Metze's found is the cause?
or winbind windows-domain-member functionality is totally broken in
3.3.0? please, ask me for any logs or configs.
More information about the samba-technical