Hi,
I am trying to import the following ldif file into openldap and get the error
message manager: value #0 invalid per syntax.
test.ldif:
dn: cn=test,o=users,dc=example,dc=com
objectClass: top
objectClass: person
cn: test
manager: 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
Console output:
Hi all,
I would like a hint on how to syncreplicate only a group of subtrees from a
master DIT.
In example, if I have a BaseDN called ou=root,dc=my_domain with 4
subtrees at the first nesting level (ou=subtree1, ou=subtree2, and so
on..), how can I configure a slave to syncrepl only subtree1 and
On 05/23/2013 10:19 AM, Soulier, Marcel wrote:
Hi,
I am trying to import the following ldif file into openldap and get the
error message “manager: value #0 invalid per syntax”.
test.ldif:
dn: cn=test,o=users,dc=example,dc=com
objectClass: top
objectClass: person
cn: test
manager:
Soulier, Marcel wrote:
manager: 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
[..]
Console output:
adding new entry cn=test,o=users,dc=example,dc=com
ldap_add: Invalid syntax (21)
additional info: manager: value #0 invalid per syntax
It seems that the RDN in your example
Hello, Howard.
Many thanks for you quick reply.
I have tried version 4.8.30 and POSIX mutex option for BDB. Unfortunately,
this doesn't helps.
Debugging results of slapd process is here: http://pastebin.com/FYjp4h61
One more thing I have noticed (may be it can give some clue): while slapd
is
Hi all,
I think I already know the answer, but I would like to be absolutely sure
about it.
Could I generate a {SSHA1} hash of a password (to be used for the rootdn
account) with the help of slappasswd utility on a system and reuse that
salted hash for the very same purpose but on a different
Hi,
I think your answer does not fully explain my problem. I changed my example to
use the dn 1.2.840.113549.1.9.1=#04024869, O=Test, C=GB where
1.2.840.113549.1.9.1 should be defined as the email Attribute in core.schema.
But I still get the same exception.
Marcel
-Ursprüngliche
On 05/23/2013 01:38 PM, Soulier, Marcel wrote:
Hi,
I think your answer does not fully explain my problem. I changed my example to
use the dn 1.2.840.113549.1.9.1=#04024869, O=Test, C=GB where
1.2.840.113549.1.9.1 should be defined as the email Attribute in core.schema.
But I still get the
Hi all,
I have an openldap directory with about 7 million DNs, running openldap 2.4.31
with a BDB backend (4.6.21), running on CentOS 6.3.
The structure of the directory is like this, with suffix dc=x,dc=y
dc=x,dc=y
account=a,dc=x,dc=y
mail=m,account=a,dc=x,dc=y // Users
--On Thursday, May 23, 2013 4:40 PM + Chris Card ctc...@hotmail.com
wrote:
Hi all,
I have an openldap directory with about 7 million DNs, running openldap
2.4.31 with a BDB backend (4.6.21), running on CentOS 6.3.
The structure of the directory is like this, with suffix dc=x,dc=y
--On Thursday, May 23, 2013 11:23 AM +0200 Marco Pizzoli
marco.pizz...@gmail.com wrote:
Hi all,
I think I already know the answer, but I would like to be absolutely sure
about it.
Could I generate a {SSHA1} hash of a password (to be used for the rootdn
account) with the help of slappasswd
Marco Pizzoli wrote:
I think I already know the answer, but I would like to be absolutely sure
about it.
Could I generate a {SSHA1} hash of a password (to be used for the rootdn
account) with the help of slappasswd utility on a system and reuse that salted
hash for the very same purpose but
I'm using the gomdb interface so I'll do my best to translate this to the C
calls. I'm performing an mdb_txn_put(), committing the transaction and then
later I'm opening a new read-only transaction where I do an mdb_txn_get() and I
receive a MDB_BAD_RSLOT: Invalid reuse of reader locktable slot
I posted this to openldap-bugs but I didn't see it actually posted to the
archive so I'll try in openldap-technical. I have LMDB integrated and it's
working smoothly except for this issue.
Original Message
I'm an author of an open source database called Sky (http://skydb.io/) and I'm
Ben Johnson writes:
{Rearranging a bit}
Am I doing something wrong with how I'm creating read-only
transactions?
Maybe this, from Caveats:
* - A thread can only use one transaction at a time, plus any child
* transactions. Each transaction belongs to one thread. See below.
*
Ben Johnson wrote:
I posted this to openldap-bugs but I didn't see it actually posted to the
archive so I'll try in openldap-technical. I have LMDB integrated and it's
working smoothly except for this issue.
Original Message
I'm an author of an open source database called Sky
Running mdb_stat testdb gives me the same Resource Busy error.
It looks like mdb.c:2941 is checking if the return address from mmap() is the
same as the hint passed in. Is there a problem with just using the mmap()
return address? It looks like the mmap() is successful but just allocating to a
Ben Johnson wrote:
Running mdb_stat testdb gives me the same Resource Busy error.
It looks like mdb.c:2941 is checking if the return address from mmap() is the
same as the hint passed in. Is there a problem with just using the mmap()
return address? It looks like the mmap() is successful but
Howard-
The meta.mm_address is getting set to env-me_map only if it's a new
environment and FIXEDMAP is used. If I open up an existing database then newenv
would be 0 and the FIXEDMAP would be ignored, right?
Ben Johnson
b...@skylandlabs.com
On May 23, 2013, at 5:04 PM, Howard Chu
19 matches
Mail list logo
