[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slurpd error: creatorsName: no user modification allowed



Bruno Negrão wrote:

Hi all,
I'm trying to put slurpd to update a slave ldap server, but it's failing. In the slave ldap server, i found these error messages in it logs:
send_ldap_result: conn=0 op=1 p=3
send_ldap_result: 19::creatorsName: no user modification allowed
send_ldap_response: msgid=2 tag=105 err=19
ber_flush: 56 bytes to sd 7
0000: 30 36 02 01 02 69 31 0a 01 13 04 00 04 2a 63 72 06...i1......*cr 0010: 65 61 74 6f 72 73 4e 61 6d 65 3a 20 6e 6f 20 75 eatorsName: no u 0020: 73 65 72 20 6d 6f 64 69 66 69 63 61 74 69 6f 6e ser modification 0030: 20 61 6c 6c 6f 77 65 64 allowed ldap_write: want=56, written=56
0000: 30 36 02 01 02 69 31 0a 01 13 04 00 04 2a 63 72 06...i1......*cr 0010: 65 61 74 6f 72 73 4e 61 6d 65 3a 20 6e 6f 20 75 eatorsName: no u 0020: 73 65 72 20 6d 6f 64 69 66 69 63 61 74 69 6f 6e ser modification 0030: 20 61 6c 6c 6f 77 65 64 allowed conn=0 op=1 RESULT tag=105 err=19 text=creatorsName: no user modification allowed
When the master ldap tries to update the slave's directoy, it gonna add the *creatorsName*, *createTimestamp*, *modifiersName* and *modifyTimestamp* attributes of each entry.

This occurs by design.

It seems the slave's directory is not accepting the modification of these attributes, specifically, the creatorsName attribute.

how to make the slave server to accept modification on these attributes?

Configure it to act as a slave. Apparently, what you consider the "slave" is not configured to behave as such. I suggest you read the admin guide about setting up replication (http://www.openldap.org/doc/admin22/replication.html ) and follow instructions step by step to check out where your replica is misconfigured.


p.




SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497