That certainly gives me more information, but I still don't see anything in stdout related to cn=config. Thank you for the suggestion.
Prior to starting the slapd daemon on v2.6, I did the following:
root@ldap-provider:~# history | grep slaptest | grep symas 1880 /opt/symas/sbin/slaptest -f /opt/symas/etc/openldap/slapd.conf -F /var/symas/openldap-data/slapd.d/
By doing this, I thought I had created the cn=config database / converted from slapd.conf. Perhaps I'm an idiot and cn=config doesn't actually exist, and all of my config settings are being directly read from slapd.conf? But that still doesn't explain to me why I can see the ACL that I (thought I) built into cn=config. I do see in the below stdout that all of the modules, for example, are being loaded from slapd.conf. If I try to move that .conf file out of the way, slapd refuses to start. I'm sure that I'm still missing something obvious. I'll keep reading.
The following stdout is edited for brevity. When we get down to the bottom at # id=00000001, that's coming from the -n1 database.
root@ldap-provider:~# slapcat -d -1 -v slapcat init: initiated tool. slap_sasl_init: initialized! reading config file /opt/symas/etc/openldap/slapd.conf /opt/symas/etc/openldap/slapd.conf: line 18 (include /opt/symas/etc/openldap/schema/core.schema) reading config file /opt/symas/etc/openldap/schema/core.schema
{snip}
reading config file /opt/symas/etc/openldap/schema/cosine.schema
{snip}
/opt/symas/etc/openldap/slapd.conf: line 21 (modulepath /opt/symas/lib/openldap) /opt/symas/etc/openldap/slapd.conf: line 22 (moduleload back_mdb.la) loaded module back_mdb.la mdb_back_initialize: initialize MDB backend mdb_back_initialize: LMDB 0.9.29: (March 16, 2021) module back_mdb.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 23 (moduleload back_ldap.la) loaded module back_ldap.la module back_ldap.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 24 (moduleload syncprov.la) loaded module syncprov.la module syncprov.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 25 (moduleload pcache.la) loaded module pcache.la module pcache.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 26 (moduleload ppolicy.la) loaded module ppolicy.la module ppolicy.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 27 (moduleload memberof.la) loaded module memberof.la module memberof.la: null module registered /opt/symas/etc/openldap/slapd.conf: line 29 (database mdb) mdb_db_init: Initializing mdb database /opt/symas/etc/openldap/slapd.conf: line 30 (suffix "dc=example,dc=com")
{snip}
slapcat startup: initiated. backend_startup_one: starting "dc=example,dc=com" mdb_db_open: "dc=example,dc=com" mdb_db_open: database "dc=example,dc=com": dbenv_open(/var/symas/openldap-data). mdb_monitor_db_open: monitoring disabled; configure monitor database to enable => mdb_entry_decode: <= mdb_entry_decode # id=00000001
{snip}
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, January 5th, 2022 at 2:21 AM, Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
David White dmwhite823@protonmail.com schrieb am 04.01.2022 um 21:56 in
Nachricht
<M4XIZ-Tt1gRAAT3xioaiNB_MDhGxw1LmqgiO5qOQz0CC5xphpB5h8UF6r2Qv-N641tn_xtdpBYIr75s
gdjXz_qGO40G1uvowznggQOeink=@protonmail.com>:
...
root@ldap-provider:~# slapcat -b cn=config
slapcat: could not open database.
root@ldap-provider:~# slapcat -n0
slapcat: could not open database.
Did you try the -v or -d option to get more info?
...
Regards,
Ulrich