12:05 p.m.
Hello list members,
I am trying to setup ldap 2.4.23 on new FreeBSD 8.2 "consumer" server to replace
a current system that is quite old. I have copied over the slapd.conf file and associated
certs, etc from the production system and I'm able to get the server working using the
sample slapd.conf and examples in the quick setup guide. When I run slaptest -f
slapd.conf.artemis on the configuration file I copied over I get the error:
slapd.conf.artemis: line 86: index attribute "reqStart" undefined
slaptest: bad configuration file!
Running the same test on the production server's slapd.conf produces no error at all.
I've googled, RTFM and read man pages trying to get a clue as to what might be causing
this, but I'm unable to unearth any leads that have helped so far. What I have tried
is to copy the production *.bdb files over to the new server thinking that was the
problem, I didn't try re-indexing those files (just read about slapindex late last
night, so haven't tried that yet) I was also thinking that I might need to run slapcat
on the production db's and then import the ldif file using slapadd (which I'm
setting up to test shortly).
Clearly I'm missing something, I'm hoping that someone here who is much more adept
at LDAP can suggest some additional things to try. Below is what I think are the relevant
portions of the slapd.conf file, which shows the section the slaptest complains about, the
second section is our replication area which I believe is directly related to the
replication process.
database bdb
suffix cn=accesslog
directory /usr/local/var/db/openldap-accesslog
rootdn cn=accesslog
index default eq
index entryCSN,objectClass,reqStart,reqResult,reqEnd
overlay accesslog
logdb cn=accesslog
logops writes
logsuccess TRUE
logpurge 07+00:00 01+00:00
I'm trying to bootstrap my Sys Admin skills (after a 12 year absence) due to the
sudden loss of my long time admin, with mixed results! Time will tell, appreciate any
suggestions you might have to get me past this particular issue.
Mike Greene
Rock Island Technology Solutions, Inc.
San Juan Islands, WA. 360-378-5884 x201
10:15 a.m.
--On Tuesday, June 28, 2011 7:05 PM +0000 Mike Greene
<mikeg(a)rockisland.com> wrote:
Hello list members,
I am trying to setup ldap 2.4.23 on new FreeBSD 8.2 "consumer" server to
replace a current system that is quite old. I have copied over the
slapd.conf file and associated certs, etc from the production system and
I'm able to get the server working using the sample slapd.conf and
examples in the quick setup guide. When I run slaptest -f
slapd.conf.artemis on the configuration file I copied over I get the
error:
slapd.conf.artemis: line 86: index attribute "reqStart" undefined
slaptest: bad configuration file!
Running the same test on the production server's slapd.conf produces no
error at all.
I've googled, RTFM and read man pages trying to get a clue as to what
might be causing this, but I'm unable to unearth any leads that have
helped so far. What I have tried is to copy the production *.bdb files
over to the new server thinking that was the problem, I didn't try
re-indexing those files (just read about slapindex late last night, so
haven't tried that yet) I was also thinking that I might need to run
slapcat on the production db's and then import the ldif file using
slapadd (which I'm setting up to test shortly).
Clearly I'm missing something, I'm hoping that someone here who is much
more adept at LDAP can suggest some additional things to try. Below is
what I think are the relevant portions of the slapd.conf file, which
shows the section the slaptest complains about, the second section is our
replication area which I believe is directly related to the replication
process.
If this is the config on a consumer, you don't need the accesslog database
at all... Only the master requires it. Did you moduleload the accesslog
overlay?
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
10:50 a.m.
First, sorry for top-posting. Need to fix this mail client to do proper quoting...
Since I sent that message I was able to resolve my problem (my post hadn't made it to
the list yet). I did not realize that during the package install the overlay(s) needed to
be included in the build, that was problem #1, once I realized that, I had some other
issues with the build I was using so I upgraded the package to 2.4.25 and everything
started working.
Since I'm just getting up to speed on ldap I'm just following what was laid out
before me, so there are a number of things I'll likely be finding that need
addressing.
Will add accesslog to my reading list.
Thank you for responding to my inquiry, much appreciated.
Mike Greene
Rock Island Technology Solutions, Inc.
San Juan Islands, WA. 360-378-5884 x201
-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@zimbra.com]
Sent: Thursday, June 30, 2011 10:16 AM
To: Mike Greene; openldap-technical(a)openldap.org
Subject: Re: slaptest returns "index attribute "reqStart" undefined
--On Tuesday, June 28, 2011 7:05 PM +0000 Mike Greene
<mikeg(a)rockisland.com> wrote:
> Hello list members,
>
> I am trying to setup ldap 2.4.23 on new FreeBSD 8.2 "consumer" server
to
> replace a current system that is quite old. I have copied over the
> slapd.conf file and associated certs, etc from the production system
and
> I'm able to get the server working using the sample slapd.conf and
> examples in the quick setup guide. When I run slaptest -f
> slapd.conf.artemis on the configuration file I copied over I get the
> error:
>
> slapd.conf.artemis: line 86: index attribute "reqStart" undefined
> slaptest: bad configuration file!
>
> Running the same test on the production server's slapd.conf produces
no
> error at all.
>
> I've googled, RTFM and read man pages trying to get a clue as to what
> might be causing this, but I'm unable to unearth any leads that have
> helped so far. What I have tried is to copy the production *.bdb
files
> over to the new server thinking that was the problem, I didn't try
> re-indexing those files (just read about slapindex late last night,
so
> haven't tried that yet) I was also thinking that I might need to run
> slapcat on the production db's and then import the ldif file using
> slapadd (which I'm setting up to test shortly).
>
> Clearly I'm missing something, I'm hoping that someone here who is
much
> more adept at LDAP can suggest some additional things to try. Below
is
> what I think are the relevant portions of the slapd.conf file, which
> shows the section the slaptest complains about, the second section is
our
> replication area which I believe is directly related to the
replication
> process.
If this is the config on a consumer, you don't need the accesslog
database
at all... Only the master requires it. Did you moduleload the
accesslog
overlay?
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
4358
days inactive
4360
days old
openldap-technical@openldap.org
2 comments
2 participants
participants (2)
-
Mike Greene -
Quanah Gibson-Mount