There is warning at lastest CE install
See original GitHub issue11:41:59 12/23/16 585d0d87 mdb_db_open: database "cn=accesslog" cannot be opened: No such file or directory (2). Restore from backup!
585d0d87 backend_startup_one (type=mdb, suffix="cn=accesslog"): bi_db_open failed! (2)
slap_startup failed (test would succeed using the -u switch)
After install CE works fine and config according to this is good too:
/opt/symas/bin/slaptest -f /opt/symas/etc/openldap/slapd.conf -F /opt/symas/etc/openldap/slapd.d
config file testing succeeded
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Deinstall and install of docker ce fails on ubuntu 18.04 #41792
After successful docker-ce installation I uninstalled it. The second installation fails. Steps to reproduce the issue: I used vagrant to ...
Read more >PS4 Error Code CE-37732-2 – Help & Support - PlayStation
The downloaded file was not installed in the system properly. It is likely that the data has been corrupted during the download process....
Read more >WARNING: latest docker-ce (20.10.0) not compatible with ...
If you are installing home assistant under docker, ... WARNING: latest docker-ce (20.10.0) not compatible with Home Assistant supervised.
Read more >Resolving Common Errors During Installation of Carbonio ...
When installing and using Carbonio CE, administrators may encounter unexpected problems that may affect the correct operation and usability ...
Read more >Cannot install docker in a RHEL server - Stack Overflow
yum -y install slirp4netns fuse-overlayfs container-selinux. was successful. ... sudo yum install docker-ce docker-ce-cli containerd.io.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, enabling cn=config lead to confusion… we were updating slapd.conf, but the changes were not taking effect. I think disabling it by default is better, so anyone who enables it needs to really understand what they’re doing.
There is no this error message in latest setup. Thanks!