Hi William,
the el8 is a new server, the el7 is an existing server which hosts some important stuff limiting it to be upgrading for a while.
on the el8 side we have:
cn=replication manager,cn=config
cn=directory manager,cn=config
ldaps port 636
over the lan, no firewalls in place, hosts can telnet on each other to the ports
On the el7 side we have Directory server still
showing port: 389 from console, under encryption, ssl is enabled,
port 636 is listening, is this a problem in itself? We have tried
setting up the method with a pin file in the /etc/dirsrv/slap*
folder, though it wasnt recognising the pin, even with chmod 400
and same owner as the dirsrv folder.
in replication on el7 side, we have replication > user root
current supplier dn, uid=Directory Manager,cn=config
On 2 Dec 2021, at 00:30, Lewis Robson <robsonl@xxxxxxxxxxxxxxx> wrote: Hello all, I have a main ldap database on an alma el8 server, this works okay and we can replicate from 8 to 8 via the cockpit web manager. We however, have a server that is on el7, we can install 389ds however the commands and setup is different and it uses the 389 ds console, our end goal is to replicate the stuff from the EL8 database to the el7 using master / slave. is there any way to get the el8 version onto el7, and if not, how do i go about replicating everything? I have set up so that tls is enabled and can ping, telnet etc to the el7 server from the el8 however when i try to replicate after entering in the details, i get errors such as: authentication mechanism [SIMPLE]: error -1 (Can't contact LDAP server), system error -5987 (Invalid function argument.), network error 0 (Unknown error, host "linux-el8:636") (same when trying to replicate over non tls, port 389)I'd ask why do you want to mix el7 and el8 like this first and foremost? To know more about why that error is happening we'll probably need to see the replication agreements on both sides.thanks _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure-- Sincerely, William Brown Senior Software Engineer, Identity and Access Management SUSE Labs, Australia _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- Lewis Robson Systems Administrator Conscious Solutions Limited Tel: 0117 325 0200 Web: https://www.conscious.co.uk
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
