Thank you Quanah. This helps a lot. Let me make the changes.
Thanks Rahul
On Mon, Jul 6, 2020 at 5:34 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Monday, July 6, 2020 6:21 PM -0400 kumar rahul rahul2002mit@gmail.com wrote:
Hi Quanah
I have some questions from update_config.ldif file
Please don't attach screenshots of text. If you have questions, use text email.
In general, however:
One database is used as the main database for the system. Lets call this database A. One database is used to store the accesslog data (the change deltas). Lets call this database B. There may be other databases on the system (such as the monitor database). Lets call this database C.
Both the syncprov and accesslog *overlays* must be configured on database A with the appropriate configuration options.
The syncprov overlay must *also* be configured on database B with the appropriate (but different) configuration options to indicate it's an accesslog DB.
In cn=config, every database has a weight that indicates the order in which it loads. So:
olcDatabase={1}... is the first DB to get loaded by slapd (Ignoring {-1} and {0} which always exist, and are the frontend and config DBs respectively).
olcDatabase={2}... would be the second DB to get loaded by slapd
olcDatabase={3}... would be the third DB to get loaded by slapd
Additionally, overlays have weights associated with them to indicate the order in which they get loaded. So:
olcOverlay={1}...,olcDatabase={2}... means that this overlay is the first one that gets loaded for database #2.
In the EXAMPLE I provided on my blog:
olcDatabase={1} is the monitoring database (database C above)
olcDatabase={2} is the ACCESSLOG database (database B above)
olcDatabase={3} is the MAIN database (database A above)
So which overlays need to apply to which databases depends ENTIRELY ON THE ORDER in which they are defined in *YOUR* configuration. You need to make adjustments accordingly.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com