On 5/5/2014 3:37 AM, Graham Leggett wrote:
What appears to be happening is that during the replication process, an LDAP operation that is accepted on servera is being rejected by serverc. The replication process is brittle, and has not been coded to handle any kind of error during the replication process, and so fails abruptly with "ERROR bulk import abandoned" and no further explanation.
I don't know specifically what happened in your case, but wanted to note that in general what you are saying is not true (or if true it means there's been a serious regression recently). Replication is designed to be tolerant of the kind of error you're thinking of (i.e. an operation error on a single entry won't stall replication for other entries).
Now, the error you're reporting is on replica initialization, rather than incremental change replication. In that case it is more reasonable to fail the entire initialization operation if a single entry fails syntax or schema check (on the basis that it isn't appropriate to propagate a data integrity error beyond the source server). However it is very surprising that this happens without any reasonable diagnostic output. If you were to try to import the same ldif data (which uses the same underlying code to process the entries), you should see a big honking error message, and only the bad entries rejected (the operation as a whole should succeed). The explosion of errors relating to database files is very definitely not the intended behavior here, which makes me suspect something else deeper and more odd is afoot.
Possibly some of the above behavior has changed recently, although it is hard to imagine why someone would deliberately degrade its behavior : I'm speaking from memory as to how it was intended to work last time I dug into this code in detail..
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
