Guys i found the problem and don't know how to solve it..
DN's which have ACLs on them (administrativerole, accesscontrolsubentry)
don't replicate attributes even when I grant everything for everyone.
When i remove ACLs, everything works.
I tested this on both master and slave clear servers, just
Le 5/11/12 11:12 AM, houmles a écrit :
Guys i found the problem and don't know how to solve it..
DN's which have ACLs on them (administrativerole, accesscontrolsubentry)
don't replicate attributes even when I grant everything for everyone.
When i remove ACLs, everything works.
I tested this on
I already have ads-replattributes: *
but even when i explicitly add those 2 attributes it doesnt work.
On 05/11/2012 12:03 PM, Emmanuel Lécharny wrote:
Le 5/11/12 11:12 AM, houmles a écrit :
Guys i found the problem and don't know how to solve it..
DN's which have ACLs on them
Found something more..
I have ou object and description in it. I can modify that description
and replicate it as long as administrativeRole is not present.
When I add administrativeRole, I got this error when I try to modify or
add any attribute:
jvm 1| [15:21:29] ERROR
ups, forgot to mention 2.0.0-M6
On 05/10/2012 10:00 AM, Emmanuel Lécharny wrote:
Le 5/10/12 9:48 AM, houmles a écrit :
Hi,
Hi,
I have fully working one ADS and want to replicate it to another. I
followed some tutorial and managed to replicate it but only just DN's. I
can't get to sync
can you provide the complete entry data with DN
ads-replConsumerId=whatever-id-you-have-here,ou=replConsumers,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config
(remove the seerver IP and user credentials if they are sensitive)
On Thu, May 10, 2012 at 1:38 PM, houmles
this looks valid, do you have any error logs?
On Thu, May 10, 2012 at 2:09 PM, houmles houm...@gmail.com wrote:
here it is:
dn: ads-replconsumerid=1,ou=replConsumers,ads-serverId=ldapServer,ou=servers
,ads-directoryServiceId=default,ou=config
objectclass: top
objectclass: ads-base
this error is not related to replication, it is a password policy related error
some user is trying to change the password but is giving a value that he has
used earlier as password.
On Thu, May 10, 2012 at 3:53 PM, houmles houm...@gmail.com wrote:
This error shows on slave server. I happens
i have only 2 test users on that ldap, i am in testing phase before
deploying to live so definitely no one changing password.
this error popups in the same time as i changed the value and slave
tried to sync.
On 05/10/2012 12:26 PM, Kiran Ayyagari wrote:
this error is not related to replication,
did you, by any chance, modify the password of the user in slave to the same
value that is being replicated later?
On Thu, May 10, 2012 at 4:01 PM, houmles houm...@gmail.com wrote:
i have only 2 test users on that ldap, i am in testing phase before
deploying to live so definitely no one
maybe, but i really don't remember, i did lot of experiments to get full
replication working
On 05/10/2012 12:46 PM, Kiran Ayyagari wrote:
did you, by any chance, modify the password of the user in slave to the same
value that is being replicated later?
On Thu, May 10, 2012 at 4:01 PM,
try with a clean slave and see if you get the same error (it shouldn't
happen, report here otherwise will take a look)
On Thu, May 10, 2012 at 4:28 PM, houmles houm...@gmail.com wrote:
maybe, but i really don't remember, i did lot of experiments to get full
replication working
On 05/10/2012
12 matches
Mail list logo