Re: Efficient way to count number of entries in a database?

Hi Quanah, 2017-11-14 16:46 GMT+01:00 Quanah Gibson-Mount : > mdb_stat -s id2e /path/to/mdb/db | grep Entries > Entries: 3993833 > That's exactly what I needed. Thanks a lot! btw for those using debian as well, mdb_stat is in the lmdb-utils package BR Karsten

Re: Is existing documentation kind of vague?

MJ J wrote: > Client apps are not scoped to do subtree searches from the root of the > directory where the autoincrement objects live, nor do the ACLs permit > it, but you knew that already. Good to hear it's alright in your deployment. But please add this extra note next time you give general

Re: Is existing documentation kind of vague?

John Lewis wrote: > I was trying to implement uidNumber Attribute Auto-Incrementing Method > and I read http://www.rexconsulting.net/ldap-protocol-uidNumber.html This is 3rd-party documentation. Just a blog article, but not bad. => Take it with a grain of salt. > what name the called the schema.

Re: Is existing documentation kind of vague?

Client apps are not scoped to do subtree searches from the root of the directory where the autoincrement objects live, nor do the ACLs permit it, but you knew that already. Duplicate a race condition using the above code and you shouldn't be using LDAP in the first place. On Tue, Nov 14, 2017

Re: Is existing documentation kind of vague?

MJ J wrote: > You don't need a special object class or schema, you can use this: > dn: cn=user,ou=increment,dc=foo,dc=bar > objectClass: top > objectClass: account > objectClass: posixAccount Ouch! Depending on the config of your LDAP server and client systems this is a visible user account with

Re: Is existing documentation kind of vague?

Hi, You don't need a special object class or schema, you can use this: dn: cn=user,ou=increment,dc=foo,dc=bar objectClass: top objectClass: account objectClass: posixAccount cn: user gidNumber: 9 homeDirectory: /no/such/location uid: user uidNumber: 1000 description: Modify-increment user

Is existing documentation kind of vague?

Hello Everyone. I was trying to implement uidNumber Attribute Auto-Incrementing Method and I read http://www.rexconsulting.net/ldap-protocol-uidNumber.html . I specifically want to point to this line here. > Create a “uidNext” entry (objectClass: uidNext) at an specific > location in the

Re: Efficient way to count number of entries in a database?

Karsten Heymann wrote: > 2017-11-14 16:21 GMT+01:00 Michael Ströder How many entries do you have in your DB? > > Currently about 1.5Mio. Way too many for using slapo-noopsrch. So Quanah's suggestion with mdb_stat is more suitable. Ciao, Michael. smime.p7s

Re: Efficient way to count number of entries in a database?

--On Tuesday, November 14, 2017 4:35 PM +0100 Karsten Heymann wrote: Currently about 1.5Mio. If you have access to the system and have mdb_stat available, the easiest method is to simply query the database directly: mdb_stat -s id2e /path/to/mdb/db | grep

Re: Efficient way to count number of entries in a database?

Hi Michael, 2017-11-14 16:21 GMT+01:00 Michael Ströder : > > Also my monitoring script does that: > https://www.stroeder.com/pylib/slapd_checkmk.py Interesting, I will have a look, especially as we might use checkmk as well. > How many entries do you have in your DB? >

Re: Efficient way to count number of entries in a database?

Karsten Heymann wrote: > is there a more efficient way to count how many entries a ldap database > has than You could try using contrib overlay slapo-noopsrch and then use noop search request control. But if you have many entries you will run into search timeout. ldapsearch -E

Re: Re: Efficient way to count number of entries in a database?

Hi, 2017-11-14 15:37 GMT+01:00 Ulrich Windl : > I avoided mdb so far I can only recommend it. Its handling is so much simpler. BR Karsten

Re: Efficient way to count number of entries in a database?

Hi Ulrich, 2017-11-14 12:40 GMT+01:00 Ulrich Windl : > >>> Karsten Heymann schrieb: > > is there a more efficient way to count how many entries a ldap database > has > > than > > > > slapcat -b | grep ^dn: | wc -l > > Here

Re: a question about "Assertion 'NUMKEYS(mp) > 1' failed in mdb_page_search_root()"

James Anderson wrote: good afternoon; we have seen sporadic instances of the “page search root" error: dydrad[20250]: [#2224] CREATE-TRANSACTION 8f9e6986-5fd4-c54b-b073-0c134552aa4a R/O => james/test2@d3102d2e-ded8-d740-8340-4b7e5608eb78 (pid=22136 tid=31865) mdb.c:5276: Assertion

Re: your mail

Dave Horsfall wrote: On Mon, 13 Nov 2017, Suneet Shah wrote: Hi Openldap http://bit.ly/2zC6jTU Thank you Suneet Is there some reason why spam is allowed on this list? This email address was a legitimate participant on this list, you can find their posts from 2011-2015 in the archive.

a question about "Assertion 'NUMKEYS(mp) > 1' failed in mdb_page_search_root()"

good afternoon; we have seen sporadic instances of the “page search root" error: dydrad[20250]: [#2224] CREATE-TRANSACTION 8f9e6986-5fd4-c54b-b073-0c134552aa4a R/O => james/test2@d3102d2e-ded8-d740-8340-4b7e5608eb78 (pid=22136 tid=31865) mdb.c:5276: Assertion 'NUMKEYS(mp) > 1' failed in

Re: restrict wildcard searches

Geert Hendrickx wrote: > Is there a way to restrict (acl?) searches using wildcards? AFAIK no. > For compliancly reasons, I want to allow certain (actually most) users to > search on eg. known email addresses, like: mail=u...@example.org, but not > to retrieve a list of all users, like

restrict wildcard searches

Hi, Is there a way to restrict (acl?) searches using wildcards? For compliancly reasons, I want to allow certain (actually most) users to search on eg. known email addresses, like: mail=u...@example.org, but not to retrieve a list of all users, like mail=*@example.org. Sizelimit restriction is

Efficient way to count number of entries in a database?

Hi, is there a more efficient way to count how many entries a ldap database has than slapcat -b | grep ^dn: | wc -l I searched the cn=Monitor backend but it does not seem to export this number. I want to have this for graphing and reporting and as a secondary data point that replication is