Kyle Tucker, dnia 2006-11-25 02:39 napisal:
> dn: cn=Replication Manager, cn=config
> changetype: add
> cn: Replication Manager
> sn: replication
> objectClass: top
> objectClass: person
> userPassword: xxxxx
'userPassword' field should be clear text. So considering that you
entered 'xxxxx' in this example, in the wizard you should provide
'xxxxx' as a password. Easiest way to do it: stop your replica, edit
dse.ldif (can be found in ./slapd-hostname/config/) and type password in
there in the userPassword. Start replica and run replication agreement
wizard on the master. Initialization should go on without any problems.
I put xxxxx in this just as an example. Oddly, on my working test
servers (1.0.3 on FC5), I used a {SSHA} password in my LDIF and it
worked without a hitch all 3 times I've set replication there. I
did put in clear text in the non-working production sets. If it's
of any help, here's the entries in the access logs, although I'd
guess there's nothing revelational here.
[24/Nov/2006:17:26:56 -0800] conn=23 fd=64 slot=64 connection from 10.1.100.186 to
10.1.109.203
[24/Nov/2006:17:26:56 -0800] conn=23 op=0 BIND dn="cn=Replication
Manager,cn=config" method=128 version=3
[24/Nov/2006:17:26:56 -0800] conn=23 op=0 RESULT err=49 tag=97 nentries=0 etime=0
[24/Nov/2006:17:26:56 -0800] conn=23 op=1 UNBIND
[24/Nov/2006:17:26:56 -0800] conn=23 op=1 fd=64 closed - U1
--
- Kyle
---------------------------------------------
kylet(a)panix.com
http://www.panix.com/~kylet
---------------------------------------------