I think you are correct for a "no", from the admin guide:
"
What Directory Units Are Replicated
The smallest unit of of the directory which can be replicated is a database.
This means that one can replicate an entire database but not a subtree
within a database.
Therefore, when creating the
I've got two 389 multi-supplier replicated instances that I want to replicate
to two new ones just temporarily for migration purposes. Since this is
production, it would be ideal if it could be replicating right up to the second
I make the new ones live. However, I simplified the configuration
On 8/23/23 10:08 AM, Omar Pagan wrote:
Getting the following error after following all the documentation for deploying
389ds and 389dsgw. Please help.
What documentation? dsgw (Directory Server Gateway) hasn't been
"supported/maintained" in over 10+ years so I am not surprised it's not
Hi Julian,
It would be helpful to get a pstack/stacktrace so we can see where DS is
stuck:
https://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Hangs
Thanks,
Mark
On 8/24/23 4:13 AM, Julian Kippels wrote:
Hi,
I am using 389-ds Version 2.3.1 and have encountered the same
Hi,
I am using 389-ds Version 2.3.1 and have encountered the same error
twice in three days now. There are some MOD operations and then I get a
line like this in the errors-log:
[23/Aug/2023:13:27:17.971884067 +0200] - ERR - ldbm_back_seq - deadlock
retry BAD 1601, err=0 Unexpected dbimpl
