[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: still unclear on error 69

Tony Earnshaw wrote:
running v2.1.22 - and with every Openldap version I've ever run since 2.1.4 - I have the following objectclasses for each posixAccount user:


So, your problem has nothing to do with schema conflicts as such.

I don't disagree. Like I said, I think that previous post was misinformed, although I don't doubt this error came with 2.1 because it is generally less permissive than 2.0.

Error 69 is not telling you anything other than that ldapmodify (ldapmod()) can not do what you want at the moment - it just doesn't tell you why.

If the server were down, the authentication failed, the user didn't have privileges to the data, etc.... there would've been a different error code telling me so. I think the 69 error is telling me something new and more specific, and I'd like to get to the bottom of it.

Quite another thing is, that if you're making the jump to 2.1.x, this should be 2.1.22 and your database should be BDB 4.1.25. But that's another story :)

My production server is 2.1.21 with BDB 4.1.25, and I'm in the process of building a new one with all the latest. These things do take time, but I'm progressing ;)

Thanks again for responding (I always like your posts), but alas I'm still seeking an explanation on this one. Anybody else?