Re: lloadd and cn=config

[Stefan Kania]

Am 07.12.23 um 17:40 schrieb Quanah Gibson-Mount:

My question was more, once you add the database config block, if you ldapsearch the cn=config database it generates, does it match what you get from slatpest conversion.

Now I understand :-). so that's what I did now

adding
----------
database config
rootdn "cn=admin,cn=config"
rootpw config
----------

to slapd.conf and start slapd with slapd.conf then I did:

ldapsearch -x -D cn=admin,cn=config -w geheim -b cn=config -H ldap://loadbalancer01.example.net -LLL > slapd-conf.ldif

Then:

rm -rf /opt/symas/etc/openldap/slapd.d/*
slapadd -n0 -F /opt/symas/etc/openldap/slapd.d/ -l slapd-conf.ldif
chown -R openldap: /opt/symas/etc/openldap/slapd.d/

switch to start slapd via cn=config

then:
systemctl restart symas-openldap-server.service


-----------
ldapsearch -x -D uid=repl-user,ou=users,dc=example,dc=net -w geheim
ldap_bind: Server is unavailable (52)
        additional info: no connections available
-----------

Stefan

Slapd has started. But the behavior is the same. Same error message as before.

smime.p7s
Description: Kryptografische S/MIME-Signatur