Upgrading to v19.5.1¶

Because Plixer Scrutinizer v19.5.1 includes an OS update, v19.4.0 is required for the upgrade. If you are running an older version, follow this guide to upgrade your server/appliance to v19.4.0.

For assistance or clarifications, contact Plixer Technical Support.

Note

The upgrade will take at least one hour to complete.
The plixer user SSH password will be needed during the upgrade. If necessary, it can be reset when the OS upgrade script is run.
If root login is enabled on the Plixer Scrutinizer server, it will be disabled as part of the upgrade.
If the Plixer Scrutinizer server is able to access files.plixer.com, the REPO_HOST variable should be set to files.plixer.com for the steps outlined below. For offline upgrades, the IP address of the offline repo should be used instead.

Upgrade process¶

The process of upgrading a v19.4.0 Plixer Scrutinizer server to v19.5.1 involves the following steps:

Backing up the v19.4.0 database and server-specific files
Downloading the operating system upgrade script, olmigrate.run, and running it a total of four times (with a reboot between runs)
Downloading and running the Plixer Scrutinizer v19.5.1 installation script (scrutinizer-install.run)
Verifying that the v19.4.0 data has been successfully migrated after v19.5.1 is installed

Pre-upgrade preparation¶

[Hardware appliances] Create a full backup of the current Plixer Scrutinizer install and store it on an external system/drive.
[Virtual appliances] Back up the current Plixer Scruinizer install by taking a VM snapshot.
Review the general upgrade preparation guide and complete any steps that apply.
[Offline upgrades] If the Plixer Scrutinizer server does not have access to files.plixer.com, set up an offline repository for this upgrade.

Upgrading the server¶

Once all preparation steps have been completed, follow these steps to upgrade the appliance:

Important

For offline upgrades, REPO_HOST should point to the IP address of the offline repo instead of files.plixer.com.
In distributed clusters, complete the upgrade for all remote collectors before upgrading the primary reporter.
To verify the current progress of the OS upgrade at any time:
```
cat /etc/motd
```
or check versions between runs (NAME= and VERSION= lines):
```
cat /etc/os-release
```
If any errors are encountered during the upgrade process, run the following to collect log files:
```
sudo tar -czf /tmp/olmigrate_logs.tar.gz /var/log/olmigration/ /var/log/leapp/ /var/log/messages /var/log/Scrutinizer-Install.log
```
Afterwards, move /tmp/olmigrate_logs.tar.gz off the server before reverting. Plixer Technical Support will require the logs to better assist you with any issues.

SSH to the v19.4.0 server to be upgraded as the plixer user.
Verify that the current working directory is correct (plixer):
```
cd /home/plixer/
```

Download the OS upgrade script and its checksum file:

REPO_HOST=files.plixer.com
curl -k -o olmigrate.run https://$REPO_HOST/plixer-repo/scrutinizer/19.5.1/olmigrate.run
curl -k -o olmigrate.run.sha256 https://$REPO_HOST/plixer-repo/scrutinizer/19.5.1/olmigrate.run.sha256

Validate the integrity of olmigrate.run:

cat olmigrate.run.sha256
sha256sum olmigrate.run

Update permissions for the OS upgrade script:
```
chmod a+x olmigrate.run
```
Run the olmigrate.run script a total of four times:
```
REPO_HOST=files.plixer.com ./olmigrate.run -- -k
```
Important

Reboots between runs of the OS upgrade script (olmigrate.run) can take a long time. Before trying to reconnect to the server, start a PING to the Plixer Scrutinizer IP address and wait for it to become available again. Do NOT manually reboot the server.
After the fourth olmigrate.run run (there will be no reboot), change directories to /tmp for the installation of Plixer Scrutinizer v19.5.1:
```
cd /tmp/
```

Download the Plixer Scrutinizer v19.5.1 installation script and its checksum file:

REPO_HOST=files.plixer.com
curl -k -o scrutinizer-install.run https://$REPO_HOST/plixer-repo/scrutinizer/19.5.1/scrutinizer-install.run
curl -k -o scrutinizer-install.run.sha256 https://$REPO_HOST/plixer-repo/scrutinizer/19.5.1/scrutinizer-install.run.sha256

Validate the integrity of scrutinizer-install.run:

cat scrutinizer-install.run.sha256
sha256sum scrutinizer-install.run

Update permissions for the installation script:

chmod a+x scrutinizer-install.run

Run scrutinizer-install.run to install Plixer Scrutinizer v19.5.1:

REPO_HOST=files.plixer.com ./scrutinizer-install.run -- -k

After the installation script finishes running, reboot the appliance:

sudo shutdown -r now

After the reboot, run the following commands to verify that the system is in working order:

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

If the heartbeat checks are successful, then the appliance has been successfully upgraded to Plixer Scrutinizer v19.5.1.

Offline upgrades to v19.5.1¶

The following instructions for setting up an offline repo are intended for upgrading to Plixer Scrutinizer v19.5.1 only.

Deploy a new Plixer Scrutinizer v19.4.0 VM and assign an IP address to it.
SSH to the VM as the plixer user:
```
ssh plixer@SCRUTINIZER_VM_IP
```

Create the offline repo directory and assign it the correct permissions:

sudo mkdir /var/db/big/offline
sudo chown plixer:plixer /var/db/big/offline

Download the offline tar file for 19.5.1 and its checksum file:

curl -o /var/db/big/offline/19.5.1_offline.tgz https://files.plixer.com/plixer-repo/scrutinizer/19.5.1_offline.tgz
curl -o /var/db/big/offline/19.5.1_offline.tgz.sha256 https://files.plixer.com/plixer-repo/scrutinizer/19.5.1_offline.tgz.sha256

Validate the integrity of 19.5.1_offline.tgz:

cat /var/db/big/offline/19.5.1_offline.tgz.sha256
sha256sum /var/db/big/offline/19.5.1_offline.tgz

Extract the offline tar file:

cd /var/db/big/offline
tar xvf 19.5.1_offline.tgz

Create a symlink in the html directory to the offline repo:

ln -s /var/db/big/offline/plixer-repo /home/plixer/scrutinizer/html/plixer-repo

After the offline repo has been set up, the VM’s IP address should be used in place of files.plixer.com for REPO_HOST in the upgrade instructions.