Re: (ITS#5536) Always use a configured serverID in the syncrepl cookie
by rein＠OpenLDAP.org
On Thu, 29 May 2008, hyc(a)symas.com wrote:
> rein(a)OpenLDAP.org wrote:
>> On Wed, 28 May 2008, Howard Chu wrote:
>>
>>> rein(a)OpenLDAP.org wrote:
>>
>>>> Syncrepl includes the serverID in the syncCookie in multi-master mode only,
>>>> but
>>>> there are other configuration that would benefit from it as well.
>>
>> The commited fix for this bug causes test033-glue-syncrepl to fail. The
>> serverID is not set by the config, which makes syncprov_qresp() skip the
>> delete when it fins that the consumer presented a cookie with its own sid
>> value.
>
> OK then I guess you're right and we need the default to be -1.
I see you have commited an alternative version to syncrepl.c. This
version don't include the serverID in the cookie when syncrepl is used on
the glue database itself, only when used on subordinate DBs. And
unfortunately, it is when used on the glue database it is needed (at least
in my configuration).
So, I still think we have to always include it when it is configured.
Unless there exist some easy way to know that a subordinate DB is not
managed by syncrepl. The only solution I know to that is to loop through
all the subordinate DBs and compare the rootdn values.
Rein
15 years, 4 months
Re: (ITS#5532) incorrect timestamp of slapd replica log
by quanah＠zimbra.com
--On June 2, 2008 8:34:12 AM -0400 Francis Swasey <Frank.Swasey(a)uvm.edu>
wrote:
> Quanah;
>
> Thank you for that completely unbiased opinion.
>
> Sheesh... I never had such terrible problems with slurpd. The problem
> with slurpd was no one wanted to maintain it anymore. So, with major
> changes in slapd came incompatibilities that no one had interest in
> working to fix.
>
> Personally -- I like Scotties comment... the fancier they make the
> plumbing, the easier it is to stop it up.
>
> Syncrepl has some really interesting failure modes. And figuring out
> that syncrepl is what loused up your replica can take a while.
True, syncrepl has definitely had some interesting issues to sort out. But
slurpd did have a lot of problems, and could mess things up just as badly,
for very obscure reasons as well.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
15 years, 4 months
Re: (ITS#5532) incorrect timestamp of slapd replica log
by Frank.Swasey＠uvm.edu
Quanah;
Thank you for that completely unbiased opinion.
Sheesh... I never had such terrible problems with slurpd. The problem
with slurpd was no one wanted to maintain it anymore. So, with major
changes in slapd came incompatibilities that no one had interest in
working to fix.
Personally -- I like Scotties comment... the fancier they make the
plumbing, the easier it is to stop it up.
Syncrepl has some really interesting failure modes. And figuring out
that syncrepl is what loused up your replica can take a while.
F
On 5/29/08 12:02 AM, quanah(a)zimbra.com wrote:
> --On Thursday, May 29, 2008 11:16 AM +0800 Hai <hai.zhao(a)gmail.com> wrote:
>
>> Hi, Quanah:
>>
>> I'm considering upgrading from 2.3 to 2.4.x. I haven't test 2.4.x yet.
>> Does this bug exist in 2.4.x too?
>
> Since slurpd was removed because it is completely unreliable and buggy, no,
> it does not exist. Sane people use syncrepl replication.
>
> --Quanah
>
>
>
> --
>
> Quanah Gibson-Mount
> Principal Software Engineer
> Zimbra, Inc
> --------------------
> Zimbra :: the leader in open source messaging and collaboration
>
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
15 years, 4 months
RE: (ITS#5542) Bug in libldap/t61.c (for your information)
by emmanuel.duru＠atosorigin.com
I am currently working on synchronisation between OpenLDAP and X.500
directories.
> -----Message d'origine-----
> De : Howard Chu [mailto:hyc@symas.com]
> Envoyé : vendredi 30 mai 2008 17:31
> À : emmanuel.duru(a)atosorigin.com
> Cc : openldap-its(a)openldap.org
> Objet : Re: (ITS#5542) Bug in libldap/t61.c (for your information)
>
> emmanuel.duru(a)atosorigin.com wrote:
> > Full_Name: Emmanuel Duru
> > Version: 2.3.39
> > OS: Windows
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (195.68.44.148)
>
> > In t61.c/ldap_utf8s_to_t61s(), the second loop is an infinite loop,
> there misses
> > a "i += j; c += j" at the end of the loop.
>
> Congratulations, you're the first person to use this code in over 6 years.
> Out
> of curiosity, why do you need it?
>
> Thanks for the report, fixed in CVS.
>
> --
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
15 years, 4 months
Re: (ITS#5543) id2entry corrupt
by pierangelo.masarati＠sys-net.it
dyxyd_dyd(a)yahoo.com wrote:
> Full_Name: Adrian
> Version: 2.3
> OS: Win XP Prof sp2
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (89.120.23.23)
>
>
> Hello,
>
> i have a huge problem with my openldap database. Even though db_recover doesn't
> indicate nothing wrong in my id2entry.bdb file, i couldn't start slapd.
>
> This is a database from a client of mine who couldn't tell me more exactly what
> happened.
>
> All i know is that id2entry.bdb is corrupt in some way. Only this file is
> corrupt, as I tried to start slapd with all other files and an older
> "id2entry.bdb".
>
> db_recover couldnt do anything.
>
> Is there any other recovery tool I could use to resuscitate this file, maybe to
> localize the corrupt places in the file and somehow remove them or fix them?
>
> Have yoy ever had this problem?
>
> Thanks a lot
Your message does not contain enough useful information to configure as
a bug report (OpenLDAP version, Berkeley BDB version, cause of issue,
anything logged by slapd, ...). Please direct software usage questions
to the openldap-software list.
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
---------------------------------------
15 years, 4 months
(ITS#5543) id2entry corrupt
by dyxyd_dyd＠yahoo.com
Full_Name: Adrian
Version: 2.3
OS: Win XP Prof sp2
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (89.120.23.23)
Hello,
i have a huge problem with my openldap database. Even though db_recover doesn't
indicate nothing wrong in my id2entry.bdb file, i couldn't start slapd.
This is a database from a client of mine who couldn't tell me more exactly what
happened.
All i know is that id2entry.bdb is corrupt in some way. Only this file is
corrupt, as I tried to start slapd with all other files and an older
"id2entry.bdb".
db_recover couldnt do anything.
Is there any other recovery tool I could use to resuscitate this file, maybe to
localize the corrupt places in the file and somehow remove them or fix them?
Have yoy ever had this problem?
Thanks a lot.
Adrian
15 years, 4 months
