(ITS#8290) Our system has occured "Server is unwilling to perform" from slapd when syncrepl rid was changed.

[Andrew Findlay]

Content preview: On Tue, Oct 27, 2015 at 02:55:11AM +0000, t-***@az.jp.nec.com
wrote: > Subject: (ITS#8290) Our system has occured "Server is unwilling
to perform" This does not look like a bug report, so you should direct it
to the openldap-technical mailing-list rather than the ITS. [...]

Content analysis details: (-4.2 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium
trust
[194.106.223.201 listed in list.dnswl.org]
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: skills-1st.co.uk]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]

Subject: (ITS#8290) Our system has occured "Server is unwilling to perform"

This does not look like a bug report, so you should direct it to the
openldap-technical mailing-list rather than the ITS.

Master server connect two slave nodes , A and B. And, LDAP syncronization
configure as below.
B server <---> Master server <---> A server
rid=27 rid=30 rid=32
Master server is set for LDAP syncronization in slapd.conf.

Remember that the syncrepl directive only configures a replication consumer.
Servers A and B also need syncrepl directives. All three servers also need the
syncprov overlay, and I suspect that this is missing in your case leading to
the error that you mentioned.

Andrew