Hi Richard, On Fri, Apr 01, 2005 at 04:24:53PM -0800, Richard A Nelson wrote: > Package: slapd > Version: 2.2.23-1 > Severity: grave > Justification: renders package unusable
Come on...
> 1) use of ldapi:/// fails:
> ldap_url_parse_ext(ldapi:///????x-mod=0777)
> daemon: bind(10) failed errno=2 (No such file or directory)
> slap_open_listener: failed on ldapi:///????x-mod=0777
>
> The cause seems to be that the ./configure script had bad settings -
> the binary expects /var/run/run/ldapi instead of the proper
> /var/run/ldapi
Very interesting. I got reports by a tester that this is the case and
some workaround but forgot about it.
> 2) error in parsing the saved ldif file:
> Setting up slapd (2.2.23-1) ...
> Enabling LDAPv2 support... already enabled.
> Updating config access directives... done.
> Moving old database directories to /var/backups:
> Loading from /var/backups/slapd-2.1.30-3:
> - directory dc=cavein,dc=org... slapadd: could not parse entry
> (line=316) failed.
That's quite known an issue. If you consider this grave, we can't put
slapd 2.2 in Debian as 2.2 fails on a lot of 2.1 and even more of 2.0
directories. I am working on a README type upgrade document which tells
the user.
> Well, that was a helpful message (I know, not your fault) :)
I think it is - at least you got the line number...
> The issue seems to be that slapcat created the root entry like this:
> uidNumber: 0000
> gidNumber: 0000
>
> but slapadd barfs on that, saying it is an invalid number! Changing
> the 0000 to 0 for the user and group settings worked fine
... and another incompatibility.
Greetings
Torsten
signature.asc
Description: Digital signature
