[Pkg-openldap-devel] Bug#673038: Re: Bug#673038: Bug#673038: slapd: slapcat output truncated every now and then

[Bálint Réczey]

tags 673038 patch upstream - moreinfo
thanks

Hi,

Upstream seems to know about the problem and I provided a fix for them
with a documentation update.
Slapcat's exit code is 1 in case of missing entries thus an
unsuccessful backup attempt can be detected.
Since there is also a helper script for retrying mentioned in me
earlier email I suggest decreasing the severity of this bug removing
it from the RC list.

Cheers,
Balint

PS: Discussion with upstream starts here:
http://www.openldap.org/lists/openldap-technical/201301/msg00195.html

2013/1/19 Balint Reczey <balint at balintreczey.hu>
>
> forwarded 673038 technical at openldap.org
> thanks
>
> Hi,
>
> I have forwarded the problem to technical at openldap.org but it has not
> yet appeared in the list archive.
>
> It worth noting that there exists a script [1] in ldap-git-backup which
> can be used for backing up LDAP databases more reliably.
>
> Cheers,
> Balint
>
> [1]
> https://github.com/elmar/ldap-git-backup/blob/master/README.mdown#safe-ldif
>
> On 06/19/2012 06:27 PM, Quanah Gibson-Mount wrote:
> > --On Tuesday, June 19, 2012 2:25 PM +0200 Axel Beckert
> > <abe at debian.org> wrote:
> >
> >> Hi Steve,
> >>
> >> Steve Langasek wrote:
> >>> > According to the slapcat man page it should be "always safe to run
> >>> > slapcat with the slapd-bdb(5) ... backends" even if slapd runs. We do
> >>> > use a BDB backend.
> >>>
> >>> Note that the HDB backend is the one recommended upstream and the
> >>> Debian
> >>> default.
> >>
> >> Well, yeah, that system has been dist-upgraded from at least Etch.
> >> IIRC it started at some time when BDB was still the default.
> >>
> >> I wrote that -- according to our backups -- this happened already with
> >> Lenny's slapd. But with Lenny it seemed to have happened less often
> >> (which is why we noticed it only recently).
> >
> > Personally, I would advise you to ask a question about this on
> > openldap-technical at openldap.org.  I asked Howard about it, and he had
> > a ready answer as to why you were seeing this, but I forget what it
> > is.  In any case, this is not a debian specific openldap bug.
> >
>
>