Ah, I don't have RA rh5-->dr-rh1.
So, I could setup a RA from all multimaster to dr-rh1 to avoid this kind of
problems.
I'm not sure to understand. Really, I have a real time RA from rh5 to rh1, and
from rh1 to rh5. So, if I initialize rh1 from rh5, rh1 should still replicates
to dr-rh1,
Hi Thierry,
thank you for these hints. I resolved by setting the "full_machine_name" to
the fqdn of the host.
But I still have another issue very similar to
https://access.redhat.com/solutions/2690611
Because I realized to have a RHDS 11.4 I try to ask to that support too.
Thank you
Warm
Gasp, I suspect the problem seems to be here. In the agreements I see
dn: cn=it 2--\3E1,cn=replica,cn=c\3Dit,cn=mapping tree,cn=config
objectClass: top
objectClass: nsds5replicationagreement
cn: it 2-->1
cn: it 2--\>1
nsDS5ReplicaRoot: c=it
description: it 2-->1
nsDS5ReplicaHost: srv1.example.com
Even if I fix as described the above issue, if I restart a replica, then the
suppliers stop to send the update and they claim with
"The remote replica has a different database generation ID than the local
database. You may have to reinitialize the remote replica, or the local
replica."
So,
> does srv2 run 1.4.3.22 ?
Yes, it is a fresh installation.
> you could try to delete the BDB region files, first stop the LDAP service,
> then delete the files
> /var/lib/dirsrv/slapd-xx/db/"__db.00*
uhm... I keep these file in a RAM fs. srv2 and srv3 are fresh installations and
received his
Hello,
I'm dealing with the update from 389-ds 1.3.9.1 to 1.4.3.22 in three
multimaster servers:
- srv1
- srv2
- srv3
srv1 replicates to srv2 and srv3.
srv2 replicates to srv1 and srv3.
srv3 replicates to srv1 and srv2.
Let suppose I reinstall srv3 with 389ds 1.4.3.22, and I initialize it
Hello Simon,
I can't find any error log related to this, I'll check again.
I don't have selinux enabled.
For now I solved setting the path in dscreate phase. Maybe this is the simplest
way for me.
The good surprise is that the process create the path by itself after the
start, I don't need an
Hello, could you help me to set `nsslapd-db-home-directory`?
I would like to change that path in order to move the cache in a RAM fs.
I tried with
` /usr/sbin/dsconf -D "cn=Directory Manager" -w *** ldap://tst-example.com:389
backend config set --dbcachesize=209715200
Hello,
thank you for the feedback. I tried to open a Feature Request here:
https://github.com/389ds/389-ds-base/issues/4703
Thank you to consider this.
Kind Regards
Marco
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To
Hello,
I like to use
[dsconf](https://directory.fedoraproject.org/docs/389ds/design/dsadm-dsconf.html)
to manage my 389ds instances.
I like also Ansible to manage the configuration. From Ansible, if I run dsconf
command I see some problems of idempotency.
For example, if I run the first
[...]
> Since you are already using python, you could more easily just use lib389
> directly rather
> than subprocess to dsconf btw:
>
>
> from lib389 import DirSrv
> import logging
[...]
I leave just a note on this...
Really at the moment I prefer trust on dsconf. I see that the lib389
Hello William,
> Can you re-run with 'dsconf -v "? dsconf should be able to
> work remotely.
This is the output on "manage" host:
[root@manage ~]# dsconf -v -D "cn=Directory Manager" -w password
ldap://tst3.example.com:389 backend config get
DEBUG: The 389 Directory Server Configuration Tool
Hello,
I'm new in this list, thank you for developing 389ds!
I would like some hints about lib389.
dscreate allows to set some parameters only when you create an instance.
So it' very difficult to maintain all configuration parameters among db and
instances and replicated instances.
I'm
13 matches
Mail list logo
