[Samba] ClassicUpgrade => EpicFail

[Andrew Bartlett]

On Mon, 2013-04-08 at 13:21 -0500, Jon Detert wrote:
> ----- Original Message -----
> > From: "Andrew Bartlett" <abartlet at samba.org>
> > To: "Jon Detert" <jdetert at infinityhealthcare.com>
> > Cc: samba at lists.samba.org
> > Sent: Sunday, April 7, 2013 4:16:30 AM
> > Subject: Re: [Samba] ClassicUpgrade => EpicFail
> > 
> > On Fri, 2013-04-05 at 14:47 -0500, Jon Detert wrote:
> > > ClassicUpgrade of my samba3 data to samba4 fails, with this error:
> > > 
> > >        ERROR(<class 'passdb.error'>): uncaught exception - Unable
> > >        to get id for sid
> > > 
> > > Full log of the classicupgrade is at the end of this email.
> > > 
> > > Project member on this list, Andrew Barlett, wrote that the issue
> > > is probably that my Samba 3 passdb was passable in an NT 4 DC
> > > mode, but is actually 'invalid' :
> > 
> > I should have been clearer:  I make no statement as to that validity
> > of
> > your database, but note that this tool has much stricter requirements
> > than we enforced on passdb databases in the past.
> 
> Understood.  I think you were clear.  My problem is that I have no idea how
> to proceed.
> 
> -- snip --
> 
> 
> > In any case, from here the next debugging step would be to run with
> > git
> > master or v4-0-test, as I included some idmap patches there that
> > didn't
> > make 4.0.4.
> 
> 
> I already tried the git master (as of March 18th) as well as the v4-0-test
> (as of March 4th).  Are you saying I should try a more recent snapshot of those
> git projects?

Probably not, but if you have nothing else to loose, please try current
master. 

> > Eventually, we will either to improve the import of the DB for your
> > particular issue, either to accept it (possibly fixing it along the
> > way)
> > or more clearly rejecting it with a proper explanation.
> 
> That would be great.  In the mean-time, is there nothing for me to do but
> wait?  Can someone give a list of common data problems to look for and fix?
> I.e. I've already resolved user/group name overlaps.  You listed 2 other
> common probs (duplicate SIDs; accounts flagged as both user and machine
> accounts).  Any tips on how to detect those problems?
> In other words, it might be faster for me to resolve my data problems than
> to wait for updated code.

If those problems were present, then it would have failed much earlier
than this. 

At this stage we need to work out which SID is failing to convert, and
then look at the uidNumber or gidNumber records on that record. 

Inserting some print statements into the python scripts would be the
best place to start, if you are comfortable with that. 

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org