[Date Prev][Date Next]
Re: Help needed with replication and ldapadd on version 2.2
Thanks for the reply.
I am creating a new server (slave) with a script and need to populate it with all the masters data. Since this is part of an install of a software on remote machine, I wish not to copy files, but rather use ldap commands to populate the salve. This is why ldapadd is used.
In version 2.0.x this was made available (well it simply worked) and now, I guess the 2.2 version is more strict.
The need is quite complex, I notify the master about the new slave and only then should the salve be populated with current master's
Is there a way to make this work with different configuration or different commands?
On 5/30/07, Buchan Milne <firstname.lastname@example.org> wrote:
On Wednesday, 30 May 2007, Jonathan Halevy wrote:
> I have a slave server that I try to run ldapadd from remote and it fails.
Why are you running ldapadd against a slave ?
> I get the following error:
> ldap_add: Internal (implementation specific) error (80)
> additional info: no structuralObjectClass operational attribute
> If I remove the updatedn line from slapd.coinf / restart the ldap, the
> command works. Yet, now* replication does not.*
This is understandable.
> Please tell me what am I doing wrong.
> Is it related the the schema?
> Is it related to access control?
Slaves should not be written to except via the replication mechanism. For
slurpd-based replication, this means by:
1)slurpd, whether running as a daemon or in oneshot mode
2)ldapmodify, if you bind as the updatedn (to manually process failed
Essentially, when operating as a slurpd-based slave, slapd only accepts writes
from the updatedn that have been generated by slapd for replication.
In both of these cases, the structuralObjectClass is provided (and other
In short, it seems you're doing something you shouldn't be .... maybe you
should tell us what you are trying to accomplish ...
ISP Systems Specialist - Monitoring/Authentication Team Leader