You mean we can resize db any time? Wouldn't it be nice to have no max
limit and grow db dynamically?
On Oct 3, 2017 4:05 PM, "Quanah Gibson-Mount" <quanah(a)symas.com> wrote:
--On Tuesday, October 03, 2017 5:04 PM -0700 rammohan ganapavarapu <
rammohanganap(a)gmail.com> wrote:
> Ok, i am just testing it, i will follow those recommendations, but this
> is what i did as work around:
>
>
> So i have updated the olcDbMaxSize to below value and now i am able to do
> ldapadd, but i was in the impression that once u set the maxsize at the
> time of ldap initialization you can't update that, right?
>
Incorrect.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Tuesday, October 03, 2017 5:12 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> You mean we can resize db any time? Wouldn't it be nice to have no max
> limit and grow db dynamically?
MDB needs a max size at startup, so you have to define one. Generally,
it's recommended to set a large value. I wrote a script once to resize MDB
upwards as it got close (20%) to its maxsize.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Tuesday, October 03, 2017 5:04 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Ok, i am just testing it, i will follow those recommendations, but this
> is what i did as work around:
>
>
> So i have updated the olcDbMaxSize to below value and now i am able to do
> ldapadd, but i was in the impression that once u set the maxsize at the
> time of ldap initialization you can't update that, right?Â
Incorrect.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Ok, i am just testing it, i will follow those recommendations, but this is
what i did as work around:
So i have updated the olcDbMaxSize to below value and now i am able to do
ldapadd, but i was in the impression that once u set the maxsize at the
time of ldap initialization you can't update that, right?
echo "dn: olcDatabase={1}mdb,cn=config
changetype: modify
replace: olcDbMaxSize
olcDbMaxSize: 21474836480" |ldapmodify -x -D "cn=config" -H
ldap://localhost:10389 -w
So the above operation will resize the db?
Thanks,
Ram
On Tue, Oct 3, 2017 at 4:01 PM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 4:53 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Ok, this is what i see in ldap logs, this could be because of
>> maxsize? olcDbMaxSize: 102400
>>
>>
>> mdb_idl_insert_keys: c_put id failed: MDB_MAP_FULL: Environment mapsize
>> limit reached (-30792)
>>
>
> Yes. Again, as I said before, you need to set a *large* maxsize. Like
> the one I recommended previously.
>
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Tuesday, October 03, 2017 4:53 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Ok, this is what i see in ldap logs, this could be because of
> maxsize? olcDbMaxSize: 102400
>
>
> mdb_idl_insert_keys: c_put id failed: MDB_MAP_FULL: Environment mapsize
> limit reached (-30792)
Yes. Again, as I said before, you need to set a *large* maxsize. Like the
one I recommended previously.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
There are two mdb files {data,lock}.mdb both owned by processes user.
On Tue, Oct 3, 2017 at 3:41 PM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 3:53 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
> and now i am trying to add below and getting index generation failed
>> error, db dir and slapd.d owned by slapd processes user.
>>
>
> What about the *.mdb files themselves?
>
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Tuesday, October 03, 2017 3:53 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
> and now i am trying to add below  and getting index generation failed
> error, db dir and slapd.d owned by slapd processes user.
What about the *.mdb files themselves?
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Quanah,
I am not converting hdb to mdb, i am setting up fresh install with mdb, i
have generated cn=config using slapd.conf and i was able to start the
slapd, now i am trying to create my org structure.
ldapsearch -x -D "cn=manager,dc=example,dc=com" -H ldap://localhost:10389
-LLL -w <> -b "dc=example,dc=com"
dn: dc=example,dc=com
objectClass: dcObject
objectClass: organization
dc: example
o: Example
description: Example
dn: ou=global,dc=example,dc=com
objectClass: organizationalUnit
objectClass: top
ou: global
dn: ou=users,ou=global,dc=example,dc=com
objectClass: organizationalUnit
objectClass: top
ou: users
description: All global users in system
and now i am trying to add below and getting index generation failed
error, db dir and slapd.d owned by slapd processes user.
dn: ou=userroles,ou=global,dc=example,dc=com
objectClass: organizationalUnit
objectClass: top
ou: userroles
Thanks,
Ram
On Tue, Oct 3, 2017 at 2:18 PM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 3:07 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Quanah,
>>
>>
>> Any thing changed int index with mdb? i am getting this error when i try
>> to add my top level entry.
>>
>
> Why are you using ldapadd? Did you not read the process Michael and I
> both described?
>
> It sounds like your mdb database is owned by root while your slapd process
> runs as a different user?
>
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Tuesday, October 03, 2017 3:07 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Quanah,
>
>
> Any thing changed int index with mdb? i am getting this error when i try
> to add my top level entry.
Why are you using ldapadd? Did you not read the process Michael and I both
described?
It sounds like your mdb database is owned by root while your slapd process
runs as a different user?
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Quanah,
Any thing changed int index with mdb? i am getting this error when i try to
add my top level entry.
cat add.ldif
dn: ou=userroles,ou=global,dc=example,dc=com
objectClass: organizationalUnit
objectClass: top
ou: userroles
adding new entry "ou=userroles,ou=global,dc=example,dc=com"
ldap_add: Other (e.g., implementation specific) error (80)
additional info: index generation failed
Thanks,
Ram
On Tue, Oct 3, 2017 at 11:36 AM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 12:29 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Thank you, one more question on mdb side, may be last question :)
>>
>>
>> How can i migrate/convert from hdb/bdb to mdb?
>>
>
> Generally, you slapcat your existing HDB database to an LDIF file, update
> your configuration for slapd to use MDB instead, and then use slapadd to
> import the LDIF file.
>
>
> --Quanah
>
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>