Latest release¶

After completing the recommended pre-upgrade preparations, follow the instructions below to upgrade Plixer Scrutinizer to the latest version.

Note

Only deployments on v19.5.3 (v19.5.4 for AWS AMIs) can be upgraded directly to v19.6.0 and beyond. For older versions, follow the steps in these guides to upgrade to the required Plixer Scrutinizer 19.5.x release before upgrading to the latest version.
If the Plixer Scrutinizer server being upgraded to v19.6.0 does not have Internet access, an internal NTP server can be configured by running the following:
```
sed -i -e '/^pool/aserver NTP_ADDRESS' -e 's/^pool/#&/' /etc/chrony.conf
```
After Plixer Scrutinizer has been upgraded to v19.6.0 or higher, any Plixer ML Engine deployments must also be upgraded to v19.5.0 or the latest available version. This will enable the ML management and configuration options integrated into the Plixer Scrutinizer UI.
To obtain a copy of the AMI installer, contact Plixer Technical Support.

Contact Plixer Technical Support for any concerns or assistance.

Online upgrades¶

To download and install the latest version upgrade for Plixer Scrutinizer, follow these steps:

SSH to the primary reporter as the plixer user and start a new tmux session (to maintain the upgrade session if the SSH connection is lost):
```
tmux new -s upgrade
```

Download the installer for the latest version:

cd /tmp
curl -o scrutinizer-install.run https://files.plixer.com/plixer-repo/scrutinizer/19.6.0/scrutinizer-install.run

Download the checksum file and validate the integrity of scrutinizer-install.run:

curl -o scrutinizer-checksums.txt https://files.plixer.com/plixer-repo/scrutinizer/19.6.0/scrutinizer-checksums.txt
cat scrutinizer-checksums.txt
sha256sum scrutinizer-install.run

Set the correct permissions for the installer:
```
sudo chmod 755 scrutinizer-install.run
```
Run the installer as the plixer user:
```
./scrutinizer-install.run
```
[Distributed cluster upgrades only] When prompted for the authentication method to use for remote collectors in the cluster, enter either existing (recommended) or passwords.
After the installer finishes running, execute the following heartbeat checks to verify communication between nodes:
```
scrut_util --check heartbeat --type database
scrut_util --check heartbeat --type api
```

If the heartbeat checks are successful, the upgrade is complete.

Offline upgrades¶

To upgrade Plixer Scrutinizer collectors/servers that are unable to access https://files.plixer.com, an offline repository can be created on the primary reporter.

To set up the offline repository and start the upgrade process, follow these steps:

Perform a backup of the current Plixer Scrutinizer install as described in the recommended upgrade preparation steps.
Download https://files.plixer.com/plixer-repo/scrutinizer/19.6.0_offline.tgz to a computer with Internet access.
Download https://files.plixer.com/plixer-repo/scrutinizer/19.6.0-checksum-offline.txt and validate the checksum of the .tar file.
Start an SSH session with the primary reporter as the plixer user.
Confirm that the primary reporter has at least 84 GB of free disk space under /var/db/big:
```
df -h
```
Create a new directory for the offline installation files and set the correct permissions to give the plixer user access to it:
```
sudo mkdir /var/db/big/offline
sudo chown plixer:plixer /var/db/big/offline
```
Copy the .tar file to the new directory (where REPO_HOST_IP is the IP address of the primary reporter/offline repository host):
```
scp 19.6.0_offline.tgz plixer@REPO_HOST_IP:/var/db/big/offline/19.6.0_offline.tgz
```
Extract the contents of the file to the same directory (this will exhaust all available storage on the appliance):
```
sudo tar -zxvf /var/db/big/offline/19.6.0_offline.tgz -C /var/db/big/offline
```
Create a symlink to the offline directory from the html directory, so the files can be served by Apache:
```
sudo ln -s /var/db/big/offline/plixer-repo /home/plixer/scrutinizer/html/plixer-repo
```
From the appliance to be upgraded, download the installer using the offline repository host IP:

curl -o scrutinizer-install.run -L -k https://REPO_HOST_IP/plixer-repo/scrutinizer/19.6.0/scrutinizer-install.run

Download the checksum file and validate the integrity of the scrutinizer-install.run file.

curl -o scrutinizer-checksums.txt -k https://REPO_HOST_IP/plixer-repo/scrutinizer/19.6.0/scrutinizer-checksums.txt

cat scrutinizer-checksums.txt

sha256sum scrutinizer-install.run

Set the correct permissions for the installer.

sudo chmod 755 scrutinizer-install.run

Run the installer as the plixer user, replacing x.x.x.x with the IP address or hostname of the offline repository host:

REPO_HOST=x.x.x.x
LOCAL_REPO_BASEDIR=/var/db/big/offline
./scrutinizer-install.run -- -k

Distributed cluster upgrades only - When asked how the installer should log in to remote collectors in the cluster, enter either existing (recommended) or passwords.
After the installer has finished running, the following heartbeat checks should be run to verify that all nodes (including standalone deployments) are able to communicate normally:

scrut_util --check heartbeat --type database
scrut_util --check heartbeat --type api

If all heartbeat checks are successful, then the systems have been upgraded successfully.