openldap-bugs

openldap-bugs@openldap.org

1 participants
20961 discussions

(ITS#8711) haproxy
by marceloandril＠yahoo.com.br 16 Aug '17

16 Aug '17

Full_Name: marcelo Version: 2.4.44 OS: centos 7.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (177.69.83.5) Good morning, I'm having a problem using syncrepl by haproxy. The server can not re-create the database. I am using mdb. Log: slapd[22501]: dn_callback : entries have identical CSN slapd[22501]: syncrepl_entry: rid=001 entry unchanged, ignored slapd[22501]: do_syncrep2: rid=001 (-1) Can't contact LDAP server slapd[22501]: do_syncrepl: rid=001 rc -1 retrying

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by fumiyas＠osstech.co.jp 13 Aug '17

13 Aug '17

On Sat, 12 Aug 2017 02:58:20 +0900, Ryan Tandy wrote: > > I've added slapd.service file. Please check. > > Looks good to me. Thanks again for working on this! :) > > Just minor comments: > > > - $(srcdir)/slapd.conf > slapd.conf.tmp ; \ > > + $(srcdir)/slapd.conf > slapd.conf.tmp || exit $$?; \ > > > - $(srcdir)/slapd.ldif > slapd.ldif.tmp ; \ > > + $(srcdir)/slapd.ldif > slapd.ldif.tmp || exit $$? > > Is there any difference between this and using && instead of ;? (Not asking for any change, I just want to make sure I understand.) In Makefile, /bin/sh is invoked without -e option. > > + if test -n "$(systemdsystemunitdir)"; then \ > > This is echoed while the rest aren't; maybe it could be either appended to the above command, or change to @if. Fixed. Thanks! -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

1 0

Re: (ITS#8710) mdb_copy wait for writer to complete
by hyc＠symas.com 12 Aug '17

12 Aug '17

muthukumardce(a)gmail.com wrote: > Full_Name: Muthukumar > Version: LMDB 0.82 > OS: OSX > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (49.207.184.177) > > > # Writer > > ``` > import lmdb > > db_path = "test.db" > DB_MAX_SIZE = 40 * 1000 * 1000 * 1000 > env = lmdb.Environment(db_path, DB_MAX_SIZE, sync=True) > txn = env.begin(write=True, buffers=True) > for i in xrange(5000000): > value = "*" * 100 > txn.put("i="+str(i), value) > txn.commit() > ``` > > I ran the above python program in my machine which took almost 8 secs to > complete. Simultaneously i try to copy the database using mdb_copy, but it > started copying only after the write program completes its execution. > > Please note: First i run the writer program then the mdb_copy, if i start > mdb_copy first it runs smoothly. > > Please help. The ITS is for bug reports, not help requests. Use the openldap-technical mailing list for assistance. The mdb_copy program needs to acquire the DB write mutex before executing, to ensure it gets a consistent snapshot. It obviously can't do that until any other active writer finishes. Closing this ITS. -- -- 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

(ITS#8710) mdb_copy wait for writer to complete
by muthukumardce＠gmail.com 11 Aug '17

11 Aug '17

Full_Name: Muthukumar Version: LMDB 0.82 OS: OSX URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (49.207.184.177) # Writer ``` import lmdb db_path = "test.db" DB_MAX_SIZE = 40 * 1000 * 1000 * 1000 env = lmdb.Environment(db_path, DB_MAX_SIZE, sync=True) txn = env.begin(write=True, buffers=True) for i in xrange(5000000): value = "*" * 100 txn.put("i="+str(i), value) txn.commit() ``` I ran the above python program in my machine which took almost 8 secs to complete. Simultaneously i try to copy the database using mdb_copy, but it started copying only after the write program completes its execution. Please note: First i run the writer program then the mdb_copy, if i start mdb_copy first it runs smoothly. Please help.

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by ryan＠nardis.ca 11 Aug '17

11 Aug '17

On Fri, Aug 11, 2017 at 08:10:09PM +0900, SATOH Fumiyasu wrote: >I've added slapd.service file. Please check. Looks good to me. Thanks again for working on this! :) Just minor comments: >- $(srcdir)/slapd.conf > slapd.conf.tmp ; \ >+ $(srcdir)/slapd.conf > slapd.conf.tmp || exit $$?; \ >- $(srcdir)/slapd.ldif > slapd.ldif.tmp ; \ >+ $(srcdir)/slapd.ldif > slapd.ldif.tmp || exit $$? Is there any difference between this and using && instead of ;? (Not asking for any change, I just want to make sure I understand.) >+ if test -n "$(systemdsystemunitdir)"; then \ This is echoed while the rest aren't; maybe it could be either appended to the above command, or change to @if.

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by fumiyas＠osstech.co.jp 11 Aug '17

11 Aug '17

Hi, I've added slapd.service file. Please check. * https://github.com/osstech-jp/openldap/pull/4 * https://patch-diff.githubusercontent.com/raw/osstech-jp/openldap/pull/4.pat… On Thu, 10 Aug 2017 19:26:48 +0900, fumiyas wrote: > > > I've revised the patch for master to check if the listener initialization > > > suceeds or not. With this patch, `slapd -d0` can return non-zero exit code > > > if the listener initialization fails, thus systemd can detect slapd.service > > > startup failure. > > > > Nice catch! That change looks correct to me, but I hope Howard will check it too. Actually it's probably relevant for any init system; possibly worth splitting out as its own commit? > > This patch does NOT affect SysV-init system because an init script > for slapd normally does NOT use the -d option. > > > Just checking, do you plan to add the service file and its installation (conditional on enabled systemd support) in this branch as well, or should I work on that myself if I want it? > > Yes, I'll do that later. -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by fumiyas＠osstech.co.jp 10 Aug '17

10 Aug '17

On Thu, 10 Aug 2017 02:16:56 +0900, Ryan Tandy wrote: > > I've revised the patch for master to check if the listener initialization > > suceeds or not. With this patch, `slapd -d0` can return non-zero exit code > > if the listener initialization fails, thus systemd can detect slapd.service > > startup failure. > > Nice catch! That change looks correct to me, but I hope Howard will check it too. Actually it's probably relevant for any init system; possibly worth splitting out as its own commit? This patch does NOT affect SysV-init system because an init script for slapd normally does NOT use the -d option. > Just checking, do you plan to add the service file and its installation (conditional on enabled systemd support) in this branch as well, or should I work on that myself if I want it? Yes, I'll do that later. Thank you. -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

1 0

(ITS#8709) pw-totp: OpenSSL 1.1 compatibility
by fumiyas＠osstech.co.jp 10 Aug '17

10 Aug '17

Full_Name: SATOH Fumiyasu Version: master OS: URL: Submission from: (NULL) (118.240.43.13) Current contrib/slapd-modules/passwd/totp is not compatible with OpenSSL 1.1+. I've created a patch to fix that. Please see the following patch I post: * https://patch-diff.githubusercontent.com/raw/osstech-jp/openldap/pull/5.pat… * https://github.com/osstech-jp/openldap/pull/5

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by ryan＠nardis.ca 09 Aug '17

09 Aug '17

On Wed, Aug 09, 2017 at 05:13:44PM +0900, SATOH Fumiyasu wrote: >I've revised the patch for master to check if the listener initialization >suceeds or not. With this patch, `slapd -d0` can return non-zero exit code >if the listener initialization fails, thus systemd can detect slapd.service >startup failure. Nice catch! That change looks correct to me, but I hope Howard will check it too. Actually it's probably relevant for any init system; possibly worth splitting out as its own commit? Just checking, do you plan to add the service file and its installation (conditional on enabled systemd support) in this branch as well, or should I work on that myself if I want it? Thanks!

1 0

Re: (ITS#8707) slapd: Add systemd service notification support
by fumiyas＠osstech.co.jp 09 Aug '17

09 Aug '17

On Tue, 08 Aug 2017 04:23:27 +0900, Ryan Tandy wrote: > > + rc = sd_notifyf( 1, > > + "READY=1\n" > > + "STATUS=slapd: ready to serve connections...\n" > > + "MAINPID=%lu", > > + (unsigned long) getpid() ); > I see you've placed this call later than the parent's exit point. Any comments about the timing of this relative to the parent's exit, and to the listener startup and so on? Are the listeners more likely to be ready to serve connections at this point? I seem to recall that in the past there was opposition to moving the parent's exit later, but I can't remember why. (and I still wish we could do that, and dispense with the ldapsearch-loop hacks...) I've revised the patch for master to check if the listener initialization suceeds or not. With this patch, `slapd -d0` can return non-zero exit code if the listener initialization fails, thus systemd can detect slapd.service startup failure. * https://github.com/osstech-jp/openldap/pull/4 * https://patch-diff.githubusercontent.com/raw/osstech-jp/openldap/pull/4.pat… -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

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