I am attempting to use slapcat to create an ldif of my 2.1 database.
When I use the modern (2.3.21) slapcat on my 2.1 database, it
complains about schema conflicts. The 2.1 version, however, does not
complain. (This is also true of slapd, which is a little more
expected)
Should I work on
Hello,
I am new with Openldap and with this list, too.
My problem is as follows:
I have set up an openldap server with simple bind.
Everything works fine when using rootdn to acess my data.
There are several addressbooks in different dns.
My access controls are:
access to *
by * read
Ok, now im getting another error message.
Look at this:
linux:~ # ldapadd -x -D cn=Manager,dc=ronnenberg.de -W -f /testdump.ldif
Enter LDAP Password:
adding new entry ou=DEZI,o=Rathaus
ldap_add: Server is unwilling to perform (53)
additional info: global superior knowledge
Here is
as I see there are some changes in schemas between the two versions. Now in
2.3:
only 1 structural objetClass in an ldap entrie
also in an ldif file you must define the define the attribute used for the
DN ie.:
dn: cn=toto, ou=people, dc=myorg
cn: toto
in the ACLs in slapd.conf if you have
matthew sporleder writes:
I am attempting to use slapcat to create an ldif of my 2.1 database.
When I use the modern (2.3.21) slapcat on my 2.1 database, it
complains about schema conflicts.
Yuck. Don't do that. To access your database files, use programs from
the LDAP version (and
Hi all,
I'm running openldap-2.3.20 from FreeBSD 6.1-prerelease ports. The slapd server
is configured to run my backend shell script. But the server fails to parse
my output.
It seems the problem is in trailing whitespace in every line except the first
(the one with RESULT) which I can see in
Jan-Piet Mens wrote:
FWIW, if an entry on the provider is modified every two minutes,
the consumer doesn't stop (have been monitoring this for about
seven days). OTOH, an update every five minutes is not sufficient,
and the consumer falls asleep and doesn't sync with the provider
any longer.
Howard Chu wrote:
Jan-Piet Mens wrote:
FWIW, if an entry on the provider is modified every two minutes,
the consumer doesn't stop (have been monitoring this for about
seven days). OTOH, an update every five minutes is not sufficient,
and the consumer falls asleep and doesn't sync with the
On Thursday 13 April 2006 09:16, Guillaume Rousse wrote:
I would also note that:
2.2.23 is an ancient and known to be very buggy release. If you are
going to use 2.2, you should be using 2.2.30.
Unfortunatly, I can't do it without manually installing it, and losing
distribution
Kurt D. Zeilenga wrote:
I encourage those interested in this feature to contribute
to its completion by:
- reading the specification (draft-zeilenga-ldap-managedit)
and commenting in the appropriate forum (ldapext@ietf.org),
Already done.
- experiment with the code in HEAD (or
Quanah Gibson-Mount wrote:
--On Wednesday, April 12, 2006 4:10 PM -0400 matthew sporleder
[EMAIL PROTECTED] wrote:
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22
--On Thursday, April 13, 2006 9:45 AM -0300 Marcelo H. Terres
[EMAIL PROTECTED] wrote:
Yes. I'm using vmware to test this problem.
When I'm running openldap 2.2.30 using Debian Woody I had no problems.
But if I try to run 2.3.21 in Debian Sarge the problems occur.
I'm testing 2.2.30 in
--On Thursday, April 13, 2006 9:21 AM -0400 matthew sporleder
[EMAIL PROTECTED] wrote:
I am attempting to use slapcat to create an ldif of my 2.1 database.
When I use the modern (2.3.21) slapcat on my 2.1 database, it
complains about schema conflicts. The 2.1 version, however, does not
--On Thursday, April 13, 2006 9:16 AM +0200 Guillaume Rousse
[EMAIL PROTECTED] wrote:
Quanah Gibson-Mount wrote:
--On Wednesday, April 12, 2006 3:42 PM +0200 Guillaume Rousse
[EMAIL PROTECTED] wrote:
Hello.
I'm having troubles with replication using sync-repl.
I first configured my
Timur Izhbulatov writes:
I'm running openldap-2.3.20 from FreeBSD 6.1-prerelease ports. The
slapd server is configured to run my backend shell script. But the
server fails to parse my output.
(...)
The slapd log looks like this:
(...)
Apr 13 13:53:17 fbsd slapd[71478]: shell search reading
Ok, now im getting another error message.
Look at this:
linux:~ # ldapadd -x -D cn=Manager,dc=ronnenberg.de -W -f /testdump.ldif
Enter LDAP Password:
adding new entry ou=DEZI,o=Rathaus
ldap_add: Server is unwilling to perform (53)
additional info: global superior knowledge
I suggest you (and other newbies) start by following the
example in the Admin Guide quick start section.
http://www.openldap.org/doc/admin23/quickstart.html
I also note that common reasons for common errors, such
as this, are discussed in the FAQ.
http://www.openldap.org/faq/index.cgi?file=53
Michael Ströder [EMAIL PROTECTED] wrote:
[snip]
Just for the records: OpenLDAP often complains about alock package even
when using back-bdb or back-hdb.
Also for the record: Messages from the alock package should not be ignored
lightly (not to say that Michael implied they could be). I'll
Thank you very much in advance. Using version 2.1.30
You're unlikely to find any happy solution with 2.1.30. But if you run
2.3.21 you can do one better and modify a back-config database; the ACLs
should take effect immediately.
What I need is for my Cobalt RaQ users to be able to authenticate
against my Postfix server for SMTP, which uses a 2.3.20 server now. In
case you not aware, the Cobalt RaQ 4 is a Linux 2.2 based server
appliance by Sun. There is the openldap-1.2.9-6 package installed on the
system, but I believe I
20 matches
Mail list logo
