We have a single master and 3 replicas. Updates are more or less "remove from the load balancer one at a time / yum -y upgrade / reboot / re-add to load balancer" when being cautious, and "yum -y upgrade / stagger reboot" when not being cautious. The ldap server is resilient enough that changes will be tracked and distributed.
On Mon, Apr 29, 2019 at 3:33 PM Patrick Landry <patrick.landry@xxxxxxxxxxxxx> wrote:
_______________________________________________Hmmm, no advice here? I would have presumed someone here is runningwith packages from the RHEL repository. I'll open a ticket with Redhat butit would be reassuring to hear from someone who has real-world experience.From: "Patrick Landry" <patrick.landry@xxxxxxxxxxxxx>
To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
Sent: Thursday, April 18, 2019 4:47:25 PM
Subject: [389-users] Proper upgrade procedure using Redhat repo and yumI have two servers running with multi master replication. The servers arerunning RHEL 7.4 with 389-ds installed via yum using the rhel-7-server-rpmsrepository. The hosts are behind a load balancer and all client access is throughthe load balancer.I would like to upgrade to the latest release available in rhel-7-server-rpms. Ihave the following packages installed related to 389ds:389-admin-1.1.46-1.el7.x86_64
389-admin-console-1.1.12-1.el7.noarch
389-admin-console-doc-1.1.12-1.el7.noarch
389-adminutil-1.1.21-2.el7.x86_64
389-console-1.1.18-1.el7.noarch
389-ds-1.2.2-6.el7.noarch
389-ds-base-1.3.7.5-21.el7_5.x86_64
389-ds-base-libs-1.3.7.5-21.el7_5.x86_64
389-ds-console-1.2.16-1.el7.noarch
389-ds-console-doc-1.2.16-1.el7.noarch
389-dsgw-1.1.11-5.el7.x86_64Only two of those packages appear to have updates available; 389-ds-base and 389-ds-base-libs.Is this the correct procedure?
- remove server1 from the load balancer config to halt client requests
- stop the dirsrv and dirsrv-admin services on server1
- run "yum upgrade 389-ds-base 389-ds-base-libs" on server1
- run "setup-ds-admin.pl -u" on server1
- restart dirsrv and dirsrv-admin on server1
- verify replication is still working
- add server1 back to load balancer config
- repeat steps 1-7 on server2
I presume that replication will continue to work after upgrading server1 but beforeupgrading server2. I believe that at step 4, I don't *also* have to run "setup-ds.pl".Is that correct?Thanks.--
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx--
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Theadora Strother
Systems Administrator Senior
Information Technology Services
University of Michigan-Dearborn
19000 Hubbard Drive, 238 FCN
Dearborn, MI 48126
Systems Administrator Senior
Information Technology Services
University of Michigan-Dearborn
19000 Hubbard Drive, 238 FCN
Dearborn, MI 48126
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
