[Samba] Re: WINBIND idmap and tdbfiles while upgrading to 3.0.20a

Joshua Weage joshua.weage at gmail.com
Thu Oct 13 15:06:06 GMT 2005


---------- Forwarded message ----------
From: Joshua Weage <joshua.weage at gmail.com>
Date: Oct 11, 2005 8:30 AM
Subject: Re: [Samba] WINBIND idmap and tdbfiles while upgrading to 3.0.20a
To: "Dirk.Laurenz at fujitsu-siemens.com" <Dirk.Laurenz at fujitsu-siemens.com>

On 10/11/05, Dirk.Laurenz at fujitsu-siemens.com <
Dirk.Laurenz at fujitsu-siemens.com > wrote:
>
> Hello everybody,
>
> had anyone of you problems with winbind and tdbfiles, when
> upgrading from 3.0.14a to 3.0.20a?
>
> The Symptom was:
> After upgrading to 3.0.20a the idmapping was corrupt.
> Although 3.0.20a runs fine, none of the idmaping was
> resolved correctly. Downgrading to 3.0.14a "restored"
> the idmaps. tdbdump showed me the same idmappings,
> therefor i think winbind wasn't able to read them?
>
> Has anyone an idea why this happened? Has anyone had this
> problem too? There're no entries in the log concering this.
>
> The idmap is in a lock idmap tdb file


Yes. Same problem here. I sent a post to the list last week and didn't see
any responses. With Samba 3.0.20a, Samba doesn't add any entries into
winbind_idmap.tdb. 3.0.14a works correctly.

I've tried various options on the idmap backend option and can't get it to
work as it did in 3.0.14a.


Josh


More information about the samba mailing list