Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Jonas Kellens
On 31-03-14 12:52, Hallvard Breien Furuseth wrote: On Mon, 2014-03-31 at 10:43 +0200, Jonas Kellens wrote: Well actually, this is the entire ACL : (...) defaultaccess none The defaultaccess keyword disappeared in OpenLDAP 2.1, and 2.4 won't start with it. Unless you're using a hacked

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Jonas Kellens
On 01-04-14 10:53, Terje Trane wrote: On 01.04.2014 09:58, Jonas Kellens wrote: even if I add at the beginning of slapd.conf the following : access to * by * I still get no results with the user 'cn=U101001,ou=101001,dc=mydomain' I only get result with 'cn=Manager,dc=mydomain' Remember

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Dieter Klünter
Am Tue, 01 Apr 2014 11:04:15 +0200 schrieb Jonas Kellens jonas.kell...@telenet.be: On 01-04-14 10:53, Terje Trane wrote: On 01.04.2014 09:58, Jonas Kellens wrote: even if I add at the beginning of slapd.conf the following : access to * by * I still get no results with the user

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Jonas Kellens
On 01-04-14 12:20, Dieter Klünter wrote: Am Tue, 01 Apr 2014 11:04:15 +0200 schrieb Jonas Kellens jonas.kell...@telenet.be: On 01-04-14 10:53, Terje Trane wrote: On 01.04.2014 09:58, Jonas Kellens wrote: even if I add at the beginning of slapd.conf the following : access to * by * I still

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Terje Trane
On 01.04.2014 14:25, Jonas Kellens wrote: debug level is 256. That is loglevel stats. You need to add the loglevel acl. You can find the loglevels in http://www.openldap.org/doc/admin24/slapdconfig.html#Configuration%20File%20Directives No need to use the numbers, You can use the keywords,

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Dieter Klünter
Am Tue, 01 Apr 2014 14:25:47 +0200 schrieb Jonas Kellens jonas.kell...@telenet.be: On 01-04-14 12:20, Dieter Klünter wrote: Am Tue, 01 Apr 2014 11:04:15 +0200 schrieb Jonas Kellens jonas.kell...@telenet.be: On 01-04-14 10:53, Terje Trane wrote: On 01.04.2014 09:58, Jonas Kellens

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Jonas Kellens
On 01-04-14 14:55, Terje Trane wrote: On 01.04.2014 14:25, Jonas Kellens wrote: debug level is 256. That is loglevel stats. You need to add the loglevel acl. You can find the loglevels in http://www.openldap.org/doc/admin24/slapdconfig.html#Configuration%20File%20Directives No need to

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Howard Chu
Terje Trane wrote: On 01.04.2014 14:25, Jonas Kellens wrote: debug level is 256. That is loglevel stats. This is an important point that seems to get missed a lot - debug level and log level are two completely separate things. We've stated this countless times now: For troubleshooting

dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Zeus Panchenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, I configured my isc-dhcpd servers to work with openldap, all works now when I want to find dn for some definite MAC or IP, I am unable to do that please, help to understand how can I ldapsearch by attribute dhcpStatements values? in

Re: Problem after migration openldap 2.3.43 to 2.4.23 -- 32 No Such Object

2014-04-01 Thread Hallvard Breien Furuseth
On Tue, 2014-04-01 at 09:58 +0200, Jonas Kellens wrote: On 31-03-14 12:52, Hallvard Breien Furuseth wrote: (...) Append something like this to access list: access to * by * search even if I add at the beginning of slapd.conf the following : access to * by * I still get no results

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Michael Ströder
On Tue, 01 Apr 2014 17:21:16 +0300 Zeus Panchenko z...@ibs.dn.ua wrote I use filter: ((objectClass=dhcpHost)(dhcpStatements=fixed-address 10.0.0.222)) and receive empty result ... Did you change the indexing configuration for attribute 'dhcpStatements'? Ciao, Michael.

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Zeus Panchenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Ströder mich...@stroeder.com wrote: I use filter: ((objectClass=dhcpHost)(dhcpStatements=fixed-address 10.0.0.222)) and receive empty result ... Did you change the indexing configuration for attribute 'dhcpStatements'? the only

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Michael Ströder
On Tue, 01 Apr 2014 18:54:22 +0300 Zeus Panchenko z...@ibs.dn.ua wrote Michael Ströder mich...@stroeder.com wrote: I use filter: ((objectClass=dhcpHost)(dhcpStatements=fixed-address 10.0.0.222)) and receive empty result ... Did you change the indexing configuration for attribute

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Zeus Panchenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Ströder mich...@stroeder.com wrote: I rephrase my question: Did you change the indexing configuration for attribute 'dhcpStatements' *after* adding/modifying the entries? no, I didn't If yes, then see this:

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Michael Ströder
Zeus Panchenko wrote: Michael Ströder mich...@stroeder.com wrote: I rephrase my question: Did you change the indexing configuration for attribute 'dhcpStatements' *after* adding/modifying the entries? no, I didn't If yes, then see this: http://www.openldap.org/faq/data/cache/136.html

Re: Changing cert paths may cause openldap to stop

2014-04-01 Thread Quanah Gibson-Mount
--On Thursday, March 27, 2014 1:52 PM +0200 Nick Milas n...@eurobjects.com wrote: Hi, On 2.4.39 (CentOS 5.10 x86_64), I found that if I attempt to change certificate values but there is an error in a path, openldap stops. I would expect this should be avoided. Openldap should reject the

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Zeus Panchenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Ströder mich...@stroeder.com wrote: Because there's no SUBSTR matching rule defined for 'dhcpHWAddress' so, there is no way to ldapsearch by that attribute exept `*' ? which is not needed anyway. mmm ... no need to be able to find the

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Harry Jede
Zeus Panchenko wrote: hi, I configured my isc-dhcpd servers to work with openldap, all works now when I want to find dn for some definite MAC or IP, I am unable to do that ... I use filter: ((objectClass=dhcpHost)(dhcpStatements=fixed-address 10.0.0.222)) and receive empty result ...

Re: dhcp.schema attribute dhcpStatements value in filter

2014-04-01 Thread Harry Jede
Harry Jede wrote: Zeus Panchenko wrote: hi, I configured my isc-dhcpd servers to work with openldap, all works now when I want to find dn for some definite MAC or IP, I am unable to do that ... I use filter: ((objectClass=dhcpHost)(dhcpStatements=fixed-address