openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

Re: (ITS#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

Hi, thank you for your reply I simply took the slapd.conf file adapted to PostgreSQL in the source (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) In that file, we have : olcSqlInsEntryStmt: insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?) it works with static configuration (slapd.conf) : I successfully managed to insert some data into the postgresql tables But after having converted it to cn=config (slaptest -f slapd.conf -F slapd.d) slapd doesn't start anymore : 0ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, <cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft after <SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> *extra cruft after <SQL expression>* 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. I believe it's a bug, no ? thanks BT Le 24/01/2013 00:39, quanah(a)zimbra.com a écrit : > --On Wednesday, January 23, 2013 10:58 PM +0000 benintechnologies(a)yahoo.fr > wrote: > >> I just noticed I forgot some infos, so here is the problem again : >> >> If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the >> line starting with olcSqlInsEntryStmt, then slapd starts fine. >> >> So what's the right syntax for olcSqlInsEntryStmt ??? > > From the man page: > > > insentry_stmt<SQL expression> > The statement that is used to insert a new entry in table > ldap_entries; see "METAINFORMATION USED" for details. The > default is "INSERT INTO ldap_entries (dn, oc_map_id, parent, > keyval) VALUES (?, ?, ?, ?)". > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > >

1 0

Re: (ITS#7499)
by quanah＠zimbra.com 23 Jan '13

23 Jan '13

--On Wednesday, January 23, 2013 10:58 PM +0000 benintechnologies(a)yahoo.fr wrote: > I just noticed I forgot some infos, so here is the problem again : > > If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the > line starting with olcSqlInsEntryStmt, then slapd starts fine. > > So what's the right syntax for olcSqlInsEntryStmt ??? >From the man page: insentry_stmt <SQL expression> The statement that is used to insert a new entry in table ldap_entries; see "METAINFORMATION USED" for details. The default is "INSERT INTO ldap_entries (dn, oc_map_id, parent, keyval) VALUES (?, ?, ?, ?)". --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

I just noticed I forgot some infos, so here is the problem again : Hi, Has anyone out there managed to successfully convert slapd.conf into cn=config with back-sql enabled ? I'm on Debian 6 / OpenLDAP 2.4.33 with back-sql support (./configure --enable-sql) According tohttp://www.openldap.org/software/release/changes.html, back-sql supports dynamic config as of version 2.4.27. So I converted slapd.conf to slapd.d, conversion went well. However, when I start slapd, I get the following message : # /usr/local/libexec/slapd -u openldap -g openldap -d -1 ....... 50ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>,<cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft after<SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> extra cruft after<SQL expression> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. The error message seems to be "extra cruft after<SQL expression>" If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the line starting with olcSqlInsEntryStmt, then slapd starts fine. So what's the right syntax for olcSqlInsEntryStmt ??? Thanks Ben

1 0

(ITS#7499) bug on dynamic configuration with back-sql
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

Full_Name: Ben Tech Version: 2.4.33 OS: Debian 6.0.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (41.85.161.126) Hi, I'm on Debian 6 / OpenLDAP 2.4.33 with back-sql. According to http://www.openldap.org/software/release/changes.html, back-sql supports dynamic config as of version 2.4.27. So I converted slapd.conf to slapd.d, conversion went well. However, when I start slapd, I get the following message : # /usr/local/libexec/slapd -u openldap -g openldap -d -1 ....... 50ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, <cn=root,dc=example,dc=com> 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft after <SQL expression>. 50ff3f0a config error processing olcDatabase={1}sql,cn=config: <olcSqlInsEntryStmt> extra cruft after <SQL expression> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 50ff3f0a send_ldap_result: err=19 matched="" text="" 50ff3f0a slapd destroy: freeing system resources. 50ff3f0a slapd stopped. 50ff3f0a connections_destroy: nothing to destroy. If I comment that line, the server starts fine # olcSqlInsEntryStmt: insert into ldap_entries (id,dn,oc_map_id,parent,keyval) v alues ((select max(id)+1 from ldap_entries),?,?,?,?)

1 0

Re: (ITS#7495) access filter not correctly validated if assertion attribute not requested
by michael＠stroeder.com 23 Jan '13

23 Jan '13

Using extra_attrs would be a possible work-around (tested). Unfortunately it seems to trigger a seg fault in slapo-rwm in my setup which is hard to track down to a certain cause. slapd starts ok but quite soon a seg fault message is written to syslog. Just before the seg fault I see the usual search requests of sssd in the logs... Ciao, Michael.

1 0

Re: (ITS#7498) Openldap syncrepl issue
by quanah＠zimbra.com 23 Jan '13

23 Jan '13

--On Wednesday, January 23, 2013 11:59 AM +0000 arunkumar_1123(a)yahoo.com wrote: > Full_Name: Arunkumar shanmugam > Version: 2.4.33 > OS: rhel5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (203.83.248.32) > > > Hi, > > I've been having issues with syncrepl in openldap. This is plain > syncrepl. I'm not using delta-syncrepl as I run with mirror mode on. MMR has supported delta-syncrepl since 2.4.27. You should use it. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7498) Openldap syncrepl issue
by arunkumar_1123＠yahoo.com 23 Jan '13

23 Jan '13

Full_Name: Arunkumar shanmugam Version: 2.4.33 OS: rhel5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (203.83.248.32) Hi, I've been having issues with syncrepl in openldap. This is plain syncrepl. I'm not using delta-syncrepl as I run with mirror mode on. I've noticed that when there are a large number of writes on the writemaster (Typically around 10 per second) the data on the readslave goes out of sync with the master, typically having entries which have been deleted on the master. The contextCSNs on both the readslaves and writemaster match eventually, but the data doesn't. I'm running the readslave in refreshOnly mode with an interval of 1 minute. I'm using a reasonably large DB of size ~ 2 GB. I turned on the sync logs and found lots of entries with "nonpresent_callback" and "syncrepl_del_nonpresent". Tested this and found it occurring in both 2.4.29 and 2.4.33 (Latest as of this time), and with BDB 4.2.36 as the backend. I was wondering if anyone has faced similar issues before, and if there exists a solution to this problem. I will send any relevant configuration and log snippets as needed. Thanks

1 0

(ITS#7497) ldif_read_record line number overflow
by hyc＠OpenLDAP.org 22 Jan '13

22 Jan '13

Full_Name: Howard Chu Version: RE24/master OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (78.155.233.73) Submitted by: hyc While trying to load a 150 million entry LDIF file using slapadd, it would finish with no errors but only ~107 million entries were loaded. This turns out to be because at 20 lines per record, the LDIF file contained 3 billion lines, and the line number counter is a signed int. And in slapadd, we have the "jumpline" option to skip some number of input lines, when resuming an interrupted load. The jumpline defaults to 0, if the input line number is less than the jumpline the record is silently skipped. After reading the 2147483647th line of the file, it discards all of the rest until hitting EOF. Will fix this by changing the parameter to unsigned long. This is unfortunately going to require a libldap version bump.

1 0

Re: (ITS#7475) documenting that dynamic lists/groups overlays are mutually exclusive with the memberof overlay
by tedcheng＠symas.com 22 Jan '13

22 Jan '13

On Jan 22, 2013, at 4:40 AM, Howard Chu wrote: > tedcheng(a)symas.com wrote: >> Full_Name: Ted C. Cheng >> Version: trunk >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (76.174.253.197) >> >> >> Document enhancement request: >> >> Dynamic lists/groups do not involve group entry modification. As a result, they >> cannot be used with the memberof overlay. Would the above text, in one single paragraph, be good enough for the documentation? >> >> It would be great to document explicitly, man pages and admin guide, that >> dynamic lists/groups overlays and memberof overlay are mutually exclusive. > > If you have suggested text, please submit the patch here. > Ted C. Cheng Symas Corporation

1 0

Re: (ITS#7475) documenting that dynamic lists/groups overlays are mutually exclusive with the memberof overlay
by hyc＠symas.com 22 Jan '13

22 Jan '13

tedcheng(a)symas.com wrote: > Full_Name: Ted C. Cheng > Version: trunk > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (76.174.253.197) > > > Document enhancement request: > > Dynamic lists/groups do not involve group entry modification. As a result, they > cannot be used with the memberof overlay. > > It would be great to document explicitly, man pages and admin guide, that > dynamic lists/groups overlays and memberof overlay are mutually exclusive. If you have suggested text, please submit the patch here. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs