Upgrading to v19.4.0¶

To upgrade to Plixer Scrutinizer v19.4.0, a v18.20 or v19.x install is required.

The following instructions cover the upgrade process for both standalone and distributed environments:

Perform a backup of the current Plixer Scrutinizer install as described in the recommended upgrade preparation steps.
SSH to the primary Reporter and start a new tmux session.
```
tmux new -s upgrade
```

Download the v19.4.0 installer.

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

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

curl -o scrutinizer-checksums.txt https://files.plixer.com/plixer-repo/scrutinizer/19.4.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
```
Important

For AMI cluster upgrades, it is also necessary to run chmod 755 /home/ec2-user before starting the installer. This will ensure that the SSH key used for communication between Plixer Scrutinizer Collectors has the correct permissions. Contact Plixer Technical Support for assistance.
Run scrutinizer-install.run on the primary Reporter as the root, plixer (recommended), or ec2-user user.
```
./scrutinizer-install.run
```

Note

If the server was previously upgraded from 18.20, you will be asked whether to delete the data.old backup that was created during that upgrade. Because a new backup should have been created prior to starting the current upgrade process, data.old can safely be deleted.

Distributed cluster upgrades only - When asked how the installer should log in to remote Collectors in the cluster, enter either existing (recommended) or passwords.

Important

When upgrading a distributed cluster from v18.20, passwords should be used. Prior to this step, the installer will also prompt the user to create a new plixer control key, which should be left blank unless encrypted keys are required.
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.