openldap-bugs September 2007

openldap-bugs@openldap.org

33 participants
179 discussions

Re: (ITS#5130) "Reply" oddities
by ghenry＠suretecsystems.com 08 Sep '07

08 Sep '07

<quote who="ando(a)sys-net.it"> > ghenry(a)suretecsystems.com wrote: > >>> When hitting "reply" from the ITS, messages are not sent to the mailing >>> list, >>> even if openldap-its(a)openldap.org is added to the CC field. >>> >> >> Testing. > > I've received yours (twice, as usual), but I don't receive mine. This is a reply via a normal mail client to openldap-its only, not cc'd to you. > > p. > > > > Ing. Pierangelo Masarati > OpenLDAP Core Team > > SysNet s.r.l. > via Dossi, 8 - 27100 Pavia - ITALIA > http://www.sys-net.it > --------------------------------------- > Office: +39 02 23998309 > Mobile: +39 333 4963172 > Email: pierangelo.masarati(a)sys-net.it > --------------------------------------- > > > >

1 0

Re: (ITS#5130) "Reply" oddities
by ando＠sys-net.it 08 Sep '07

08 Sep '07

ghenry(a)suretecsystems.com wrote: >> When hitting "reply" from the ITS, messages are not sent to the mailing >> list, >> even if openldap-its(a)openldap.org is added to the CC field. >> > > Testing. I've received yours (twice, as usual), but I don't receive mine. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5130) "Reply" oddities
by ghenry＠suretecsystems.com 08 Sep '07

08 Sep '07

<quote who="ando(a)sys-net.it"> > Full_Name: Pierangelo Masarati > Version: none > OS: none > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (131.175.154.35) > Submitted by: ando > > > When hitting "reply" from the ITS, messages are not sent to the mailing > list, > even if openldap-its(a)openldap.org is added to the CC field. > Testing.

1 0

(ITS#5130) "Reply" oddities
by ando＠sys-net.it 08 Sep '07

08 Sep '07

Full_Name: Pierangelo Masarati Version: none OS: none URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (131.175.154.35) Submitted by: ando When hitting "reply" from the ITS, messages are not sent to the mailing list, even if openldap-its(a)openldap.org is added to the CC field.

1 0

Re: (ITS#5120) slapadd -q makes database logs unusable
by ando＠sys-net.it 08 Sep '07

08 Sep '07

hyc(a)symas.com wrote: > ando(a)sys-net.it wrote: >> hyc(a)symas.com wrote: >>> ando(a)sys-net.it wrote: >>>> When slapadd'ing -q, existing database log files seem to become unusable. If >>>> this is correct, as it seems to be, slapadd could refuse to start with -q if log >>>> files are present, or, for example, remove the logs if -qq. >>> I guess we could add that check. The docs already say that if an error occurs, >>> the entire database will be unusable. As such, you should only use it for >>> initially populating a database, not for adding to an existing one. >> The story is that I placed logs in a separate directory and I forgot to >> clean them up when regenerating the DB after removing the database files :) > > Ugh. I don't see how we can reliably detect this case. > > In what way do the logs become unusable? I've tried to reproduce this situation > and see no errors of any kind. > > E.g., sh run test001 > rm testrun/db.1.a/{alock,*db*} > ../servers/slapd/slapadd -q -f testrun/slapd.1.conf -l testdata/test-ordered.ldif > (the above works fine) > ../servers/slapd/slapd -f testrun/slapd.1.conf ... > (works fine) > > db_stat -h testrun/db.1.a -l > > (no complaints there either) Initially, I thought your check was not much representative, since test001 doesn't do any writes. In my original case, I forgot to mention that DB_LOG_AUTOREMOVE was set. So I tried that configuration and manually ran the load of test008, resulting in creating multiple logs, part of which were removed. Then I ran the commands you suggested above, but nothing happened, so I'm at a loss. In fact, old log files were immediately removed by slapd itself, and log files numbering correctly restarted from where it left. Probably I was chasing a red herring. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5120) slapadd -q makes database logs unusable
by hyc＠symas.com 07 Sep '07

07 Sep '07

ando(a)sys-net.it wrote: > hyc(a)symas.com wrote: >> ando(a)sys-net.it wrote: >>> When slapadd'ing -q, existing database log files seem to become unusable. If >>> this is correct, as it seems to be, slapadd could refuse to start with -q if log >>> files are present, or, for example, remove the logs if -qq. >> I guess we could add that check. The docs already say that if an error occurs, >> the entire database will be unusable. As such, you should only use it for >> initially populating a database, not for adding to an existing one. > > The story is that I placed logs in a separate directory and I forgot to > clean them up when regenerating the DB after removing the database files :) Ugh. I don't see how we can reliably detect this case. In what way do the logs become unusable? I've tried to reproduce this situation and see no errors of any kind. E.g., sh run test001 rm testrun/db.1.a/{alock,*db*} ../servers/slapd/slapadd -q -f testrun/slapd.1.conf -l testdata/test-ordered.ldif (the above works fine) ../servers/slapd/slapd -f testrun/slapd.1.conf ... (works fine) db_stat -h testrun/db.1.a -l (no complaints there either) -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5129) slapindex -q corrupts database if the DB_CONFIG file has changed
by hyc＠symas.com 07 Sep '07

07 Sep '07

quanah(a)zimbra.com wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.3.37 > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (71.202.148.128) > > > After getting repeat DB corruptions, I finally tracked down the issue to this: > > If DB_CONFIG has changed since the last time slapd was started, and slapindex -q > is run, the database ends up corrupt. Don't do that. HEAD has been fixed to exit in this situation. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5129) slapindex -q corrupts database if the DB_CONFIG file has changed
by quanah＠zimbra.com 07 Sep '07

07 Sep '07

Full_Name: Quanah Gibson-Mount Version: 2.3.37 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (71.202.148.128) After getting repeat DB corruptions, I finally tracked down the issue to this: If DB_CONFIG has changed since the last time slapd was started, and slapindex -q is run, the database ends up corrupt. For example, I did the following with a perfectly happy slapd: ldap stop Killing slapd with pid 9857 done. cd /opt/zimbra/openldap-data touch DB_CONFIG /opt/zimbra/openldap/sbin/slapindex -b '' -q -f /opt/zimbra/conf/slapd.conf bdb_db_open: DB_CONFIG for suffix has changed. Performing database recovery to activate new settings. bdb(): DB_RECOVER and DB_RECOVER_FATAL require DB_TXN_INIT in DB_ENV->open bdb(): PANIC: Invalid argument bdb_db_open: Database cannot be recovered, err -30978. Restore from backup! backend_startup_one: bi_db_open failed! (-30978) slap_startup failed One of the things this does, is break syncreplication, as it apparently clears out the glue entry. :/ --Quanah

1 0

(ITS#5128) slapd startup fails to note suffix when DB_CONFIG chagnes and suffix is ""
by quanah＠zimbra.com 07 Sep '07

07 Sep '07

Full_Name: Quanah Gibson-Mount Version: 2.3.37 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (71.202.148.128) I noticed that when using the empty suffix, and DB_CONFIG is updated, this gets logged: bdb_db_open: DB_CONFIG for suffix has changed. Note the extra space and lack of suffix.

1 0

Re: ldap_unbind unhandled SIGPIPE (ITS#5127)
by ando＠sys-net.it 07 Sep '07

07 Sep '07

ando(a)sys-net.it wrote: > I've prepared a trivial client that ldap_sasl_bind_s(), holds on while I > shut down the server, ldap_search_ext_s() with LDAP_SERVER_DOWN and > ldap_unbind_ext(). Prior to patching, I always got SIGPIPE. Let me add that the above patch does not work when using ldapi://; in that case, the SIGPIPE occurs when first flushing a request on the broken connection (in sb_stream_write()), while on regular INET sockets the flush succeeds and the SIGPIPE prior to patching was returned much later at unbind. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

← Newer
1
...
10
11
12
13
14
15
16
17
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs September 2007