I looked in my logs and found this error when I try to sync when replication
is not working:
Jul 14 09:08:28 provider slapd[30730]: <= bdb_equality_candidates: (memberUid)
not indexed
Jul 14 09:08:28 provider slapd[30730]: <= bdb_equality_candidates:
(uniqueMember) not indexed
Jul 14 09:08:28 p
--On Wednesday, July 08, 2009 4:39 PM -0400 Arnout Boelens
wrote:
Thanks for the replies. However, I added "Retry "60 +"" and removed the
attrs option, but replication still stops working. Any more ideas about
what could cause this?
Given the ancient release you are using, and the numerous
Thanks for the replies. However, I added "Retry "60 +"" and removed the attrs
option, but replication still stops working. Any more ideas about what could
cause this?
Thanks,
Arnout
smime.p7s
Description: S/MIME cryptographic signature
--On Tuesday, July 07, 2009 10:52 AM -0600 Matt Kassawara
wrote:
Oops... I was under the impression that refreshAndPersist was for
MMR/MirrorMode instead of master-slave propagation.
Nope, completely unrelated. refreshAndPersist has been around since at
least 2.3, and even possibly 2.2,
Oops... I was under the impression that refreshAndPersist was for
MMR/MirrorMode instead of master-slave propagation.
On Tue, Jul 7, 2009 at 10:43 AM, Quanah Gibson-Mount wrote:
> --On Tuesday, July 07, 2009 8:58 AM -0600 Matt Kassawara <
> batt...@writeme.com> wrote:
>
> Try changing your syncr
--On Tuesday, July 07, 2009 8:58 AM -0600 Matt Kassawara
wrote:
Try changing your syncrepl mode to refreshOnly.
The "attrs" field in the configuration is clearly incorrect. The
suggestion to use refreshOnly should be ignored. refreshAndPersist is
generally more what people want anyhow, s
6 matches
Mail list logo
