You got me wrong: the problem is not the port, it's the URI; "master.site:<anyport>" is not a valid URI"master.site:38" is not a valid referral URI.Sorry ... i write wrong message, yes certainly this was
"referral="master.site:389"
I remake replica from slurp to synrepl, it work fine from master to slave but i again have problem write changes from
slave to master
updateref ldap://ldap.dgb.local:389This is a valid URI.
Apparently, your client tries to chase referrals anonymously, and this fails as expected. I don't see any software malfunction here (on the OpenLDAP side, at least); there might be a missing or misimplemented feature in the client, though.------------------------------------------------------------------------- I try from differnt client
ldapadd return message from slave - "ldap_add: Referral (10) referrals: ldap://ldap.dgb.local/uid=bbb1,ou=user,dc=dgb,dc=local" LDAP Admin from windows return message from master
"text=modifications require authentication".
That's a completely different business. I gather from your initial message that your master is 2.3.11. As the current release is 2.3.30, and the CHANGES reports a huge number of fixes and improvements to sync replication, I suggest you upgrade before proceeding any further with syncrepl.???
P.S. I got crash master slapd when i try syncreplica with
type=refreshAndPersist.
refreshOnly - work fine.
p.