[389-users] LDAP server is unwilling to perform

[mjames at guesswho.com]

Sorry, forgot to send this to the list.

From: Michael James
Sent: Tuesday, March 13, 2012 12:13 PM
To: 'Rich Megginson'
Subject: RE: [389-users] LDAP server is unwilling to perform

That’s a big *IF* there… I did turn up the logging. Attached is the error log, trimmed to around the time that I tried to create the new replication agreement. Sorry about that.

From: Rich Megginson [mailto:rmeggins at redhat.com]<mailto:[mailto:rmeggins at redhat.com]>
Sent: Tuesday, March 13, 2012 11:51 AM
To: General discussion list for the 389 Directory server project.
Cc: Michael James
Subject: Re: [389-users] LDAP server is unwilling to perform

On 03/13/2012 09:41 AM, mjames at guesswho.com<mailto:mjames at guesswho.com> wrote:
Pls see attached new console.log. Thanks.
If you follow the directions at http://port389.org/wiki/FAQ#Troubleshooting to enable the Replication log level, the extra information will be in the directory server errors log, not the console log - /var/log/dirsrv/slapd-INST/errors

Mike

From: Rich Megginson [mailto:rmeggins at redhat.com]
Sent: Monday, March 12, 2012 3:14 PM
To: General discussion list for the 389 Directory server project.
Cc: Michael James
Subject: Re: [389-users] LDAP server is unwilling to perform

On 03/12/2012 12:39 PM, mjames at guesswho.com<mailto:mjames at guesswho.com> wrote:
Pls. see attached. Thx.
Hmm - nothing to go on there - please turn on the Replication log level and reproduce the problem - then the errors log may contain more clues
http://port389.org/wiki/FAQ#Troubleshooting


Mike

From: Rich Megginson [mailto:rmeggins at redhat.com]
Sent: Monday, March 12, 2012 1:30 PM
To: General discussion list for the 389 Directory server project.
Cc: Michael James
Subject: Re: [389-users] LDAP server is unwilling to perform

On 03/12/2012 11:30 AM, mjames at guesswho.com<mailto:mjames at guesswho.com> wrote:
Thanks for your previous help. I built a new server, CentOS 6.2, added the epel-389-ds-base and epel repos, then installed 389-ds via yum. I ran setup-ds-admin.pl with the “Typical” setup option, user nobody, and registered with one of our existing configuration servers. I created the supplier bind DN on the new server per the installation docs.

At this point, I can’t establish a replication agreement. I open the 389-console on existing server and use the GUI to create a new replication agreement on userRoot. I accepted the defaults, entered the correct bind DN and password. At the end of the wizard, it fails with “LDAP server is unwilling to perform”. In the error log, I see one error. Any help is appreciated. Thanks, Mike
Can you run the console with -D 9 -f console.log, reproduce the problem, remove any sensitive information from console.log, and post console.log to this list?



[12/Mar/2012:13:26:46 -0400] NSMMReplicationPlugin - agmtlist_add_callback: Can't start agreement "cn=389 to analog-01v,cn=replica,cn=dc\3d<MY_DOMAIN>\2c dc\3dcom,cn=mapping tree,cn=config"




--

389 users mailing list

389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>

https://admin.fedoraproject.org/mailman/listinfo/389-users




--

389 users mailing list

389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>

https://admin.fedoraproject.org/mailman/listinfo/389-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20120313/844c4119/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: errors.txt
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20120313/844c4119/attachment.txt>