Hi Quanah
Please ignore the previous email. The location I gave you was the directory I have created for the accesslog database.I am new to ldap so bare with my primitive questions. Please find my response to your questions
It looks like at least some of the modules in your system are compiled statically, which is likely why you currently do not have a module{0} section for loading modules.
[Rahul] How do I verify this if modules are compiled statically?
You'll also have to verify where on disk the accesslog overlay exists so that the moduleload statement pulls from the right directory.
[Rahul] How do I find out where an accesslog overlay exists on the disk? based on findings What changes I need to make in below lines for moduleload to work dn: cn=module{0},cn=config changetype: modify add: olcModuleLoad olcModuleLoad: syncprov olcModuleLoad: accesslog
Thanks Rahul
On Wed, Jul 1, 2020 at 3:14 PM kumar rahul rahul2002mit@gmail.com wrote:
Hi Quanah
accesslog overlay file exists at following location /var/lib/ldap/accesslog
What changes I need to make in below lines for moduleload to work dn: cn=module{0},cn=config changetype: modify add: olcModuleLoad olcModuleLoad: syncprov olcModuleLoad: accesslog
Thanks Rahul
On Wed, Jul 1, 2020 at 1:38 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Wednesday, July 1, 2020 11:09 AM -0400 kumar rahul rahul2002mit@gmail.com wrote:
I am seeing following ERROR
I have no idea how your slapd was built, etc. But essentially the accesslog overlay must be loaded into slapd to be of use. It looks like at least some of the modules in your system are compiled statically, which is likely why you currently do not have a module{0} section for loading modules. You'll also have to verify where on disk the accesslog overlay exists so that the moduleload statement pulls from the right directory.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com