You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the olcServerID attribute on cn=config to help with setting up replication and ensuring that the entryCSN is set with the correct sid on all entries
What is the feature you are proposing to solve the problem?
add an environment variable that can be used on startup to set the value of olcServerID on cn=config
What alternatives have you considered?
I currently just set the olcServerID value when I startup a new server. The only problem is that the dc=example,dc=com entry has an entryCSN value with a sid of 000 when I do this. As a result the accesslog database has an extra minCSN value as well.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Name and Version
bitnami/openldap:2.6
What is the problem this feature will solve?
Setting the olcServerID attribute on cn=config to help with setting up replication and ensuring that the entryCSN is set with the correct sid on all entries
What is the feature you are proposing to solve the problem?
add an environment variable that can be used on startup to set the value of olcServerID on cn=config
What alternatives have you considered?
I currently just set the olcServerID value when I startup a new server. The only problem is that the dc=example,dc=com entry has an entryCSN value with a sid of 000 when I do this. As a result the accesslog database has an extra minCSN value as well.
The text was updated successfully, but these errors were encountered: