Linux

Upgrade to HAProxy Enterprise 1.6r2

The following upgrade procedure installs a new major version of HAProxy Enterprise.

1. Take the server that you want to upgrade out of the cluster.

2. Install HAProxy Enterprise 1.6r2 by running the following command and replacing <HAProxy Enterprise Key> with the key you received when you registered:

   $ curl -s https://www.haproxy.com/static/install_haproxy_enterprise.sh | sudo bash /dev/stdin 1.6r2 <HAProxy Enterprise key>

3. Update additional modules: you may be running additional modules with HAProxy Enterprise, which you must also reinstall when you upgrade to a new release. Install a package using its name, for example:

   • apt Debian/Ubuntu
   • yum CentOS/RedHat/etc

   $ # On Debian/Ubuntu
   $ sudo apt-get install hapee-1.6r2-lb-update

   $ # On CentOS/RedHat/Oracle
   $ sudo yum install hapee-1.6r2-lb-update

4. Copy /etc/hapee-[previous-version]/hapee-lb.cfg over to /etc/hapee-1.6/hapee-lb.cfg and any associated files (maps, certificates, etc).

5. Disable the old HAProxy Enterprise version from starting with the system, as follows:

   $ sudo systemctl disable hapee-<previous-version>-lb

6. Ensure that the new HAProxy Enterprise version starts with the system, as follows:

   $ sudo systemctl enable hapee-1.6-lb

7. Stop the old HAProxy Enterprise daemon and start the new daemon:

   $ sudo systemctl stop hapee-<previous-version>-lb
   $ sudo systemctl start hapee-1.6-lb

   On older systems that do not have systemctl, use:

   $ sudo service hapee-1.6-lb start

8. Run tail -f /var/log/syslog (or distribution equivalent) to check for warnings or errors.

9. Run curl localhost to ensure that HAProxy Enterprise is responding. Adjust address/port as needed, and use a local address that is currently active on the box and not a VRRP IP.

10. Put the upgraded server back into the cluster.

11. Repeat this procedure on secondary servers.

Upgrade to HAProxy Enterprise 1.6r2 from 1.6r1

When upgrading HAProxy Enterprise 1.6r1 to 1.6r2, the following conditions apply:

• The directory names do not change.

• The configuration files are located in the same place.

• The init scripts keep the same names.

• Each release of a version is mutually exclusive, which means that another release of an HAProxy Enterprise version cannot run together on the same server.

• HAProxy Enterprise repositories, GPG key, and customer subscription key remain the same.

1. Take the server that you want to upgrade out of the cluster.

2. Run the following command to install the new release:

   $ curl -s https://www.haproxy.com/static/install_haproxy_enterprise.sh | sudo bash /dev/stdin 1.6r2 <HAProxy Enterprise key>

3. Restart the service:

   $ sudo systemctl hapee-1.6-lb start

   On older systems that do not have systemctl, use:

   $ sudo service hapee-1.6-lb start

4. Run tail -f /var/log/syslog (or distribution equivalent) to check for warnings or errors.

5. Run curl localhost to ensure that HAProxy Enterprise is responding. Adjust address/port as needed, and use a local address that is currently active on the box and not a VRRP IP.

6. Put the upgraded server back into the cluster.

7. Repeat this procedure on secondary servers.

Post-upgrade

After you upgrade, see the section on additional packages on how to enable and configure each one.

After the new HAProxy Enterprise version has been running for a while, you can uninstall the old HAProxy Enterprise version. To uninstall a package:

$ # On Debian or Ubuntu
$ sudo apt purge hapee-<previous-version>-lb

$ # On CentOs/RedHat/Oracle
$ sudo yum remove hapee-<previous-version>-lb

Update HAProxy Enterprise

The update procedure installs the latest build for your current HAProxy Enterprise version in order to benefit from the latest bug fixes.

$ # On Debian/Ubuntu
$ sudo apt update
$ sudo apt upgrade

$ # On CentOs/RedHat/Oracle
$ sudo yum update