[Date Prev][Date Next]
Re: (ITS#5678) slurpd stops processing the replication log if consecutive blank lines are encountered
On Tue, 23 Sep 2008 15:33:47 +0200
Michael StrÃ¶der <firstname.lastname@example.org> wrote:
> Which version 2.3? It is definitely more stable than slurpd in recent
> versions of 2.3 (2.3.43 is most recent release).
2.3.30, the debian etch package - unfortunately upgrading isn't really
an option here.
I experienced segfaults on the provider server. Although I'm not
entirely sure the provider was initialised properly*, the fact that
slapd would crash seemed a sufficient indication we should bide our time
and wait till 2.4 hit debian stable.
*The 2.3 admin guide states:
The provider slapd (8) is not required to be restarted. contextCSN is
automatically generated as needed: it might be originally contained in
the LDIF file, generated by slapadd (8), generated upon changes in the
context, or generated when the first LDAP Sync search arrives at the
provider. If an LDIF file is being loaded which did not previously
contain the contextCSN, the -w option should be used with slapadd (8)
to cause it to be generated. This will allow the server to startup a
little quicker the first time it runs.
This doesn't seem very clear to me - should I re-import the database
with the -w option, or should adding the overlay and syncprov-*
directives to slapd.conf and restarting be sufficient?