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>
>
>
Thank you, one more question on mdb side, may be last question :)
How can i migrate/convert from hdb/bdb to mdb?
Ram
On Tue, Oct 3, 2017 at 11:09 AM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 11:47 AM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Ok, but are there any casses where DB size can grow bigger then RAM and
>> what will happen in that case?
>>
>
> Same thing that happens in any such case.. it'll start swapping.
>
>
> --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 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>
--On Tuesday, October 03, 2017 11:47 AM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Ok, but are there any casses where DB size can grow bigger then RAM and
> what will happen in that case?
Same thing that happens in any such case.. it'll start swapping.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Ok, but are there any casses where DB size can grow bigger then RAM and
what will happen in that case?
On Oct 3, 2017 10:18 AM, "Quanah Gibson-Mount" <quanah(a)symas.com> wrote:
> --On Tuesday, October 03, 2017 11:03 AM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Quanah,
>>
>>
>> Quick question regarding "maxsize" in mdb, slapd-mdb man page says we
>> have to preallocate the db size based on future growth of your data, that
>> means will it create a data.mdb of maxsize? what i read from docs is, mdb
>> loads whole database into memory, is it right? if my db size is grater
>> then my RAM how does mdb handles? do we have any configuration options to
>> set RAM allocation for mdb as i may have other applications sharing the
>> same RAM?
>>
>
> It uses RAM in accordance to the size of the database, not the maxsize.
> Generally, you set the maxsize value to something really large and forget
> about it. I would note you already have a fairly large database. However,
> MDB should use significantly *less* RAM than your old back-hdb database
> overall, because your old back-hdb DB had to use multiple caches in RAM as
> a part of the slapd process (cachesize, idlcachesize, dncachesize) in
> addition to the BDB cache (set_cachesize in DB_CONFIG).
>
> --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 11:03 AM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Quanah,
>
>
> Quick question regarding "maxsize" in mdb, slapd-mdb man page says we
> have to preallocate the db size based on future growth of your data, that
> means will it create a data.mdb of maxsize? what i read from docs is, mdb
> loads whole database into memory, is it right? if my db size is grater
> then my RAM how does mdb handles? do we have any configuration options to
> set RAM allocation for mdb as i may have other applications sharing the
> same RAM?
It uses RAM in accordance to the size of the database, not the maxsize.
Generally, you set the maxsize value to something really large and forget
about it. I would note you already have a fairly large database. However,
MDB should use significantly *less* RAM than your old back-hdb database
overall, because your old back-hdb DB had to use multiple caches in RAM as
a part of the slapd process (cachesize, idlcachesize, dncachesize) in
addition to the BDB cache (set_cachesize in DB_CONFIG).
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>