Offline upgrades¶
To upgrade Plixer Scrutinizer collectors/servers that do not have access to https://files.plixer.com
, an offline repository can be created on the primary reporter. For assistance, contact Plixer Technical Support.
To set up the offline repository and start the upgrade process, follow these steps:
Important
In the following instructions, VERSION should be replaced with the full target version number (e.g., when upgrading to v19.4.0, replace VERSION with 19.4.0
).
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/VERSION_offline.tgz
to a computer with Internet access.Download
https://files.plixer.com/plixer-repo/scrutinizer/VERSION-checksum-offline.txt
and validate the checksum of the .tar file.Enter
df -h
and confirm that the primary reporter has at least 84 GB of free disk space under/var/db/big
.Start an SSH session with the primary reporter as the
plixer
user.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
Move the .tar file to the appropriate directory on the primary Reporter.
scp VERSION_offline.tgz [email protected]:/var/db/big/offline/VERSION_offline.tgz
Extract the contents of the file to the same directory.
sudo tar -zxvf /var/db/big/offline/VERSION_offline.tgz -C /var/db/big/offline
Important
Extracting the contents of the .tar file will exhaust all available space on the appliance.
Create a symlink to the
offline
directory from thehtml
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 from the offline repository.
curl -o scrutinizer-install.run -L -k https://127.0.0.1/plixer-repo/scrutinizer/VERSION/scrutinizer-install.run
Download the checksum file and validate the integrity of the
scrutinizer-install.run
file.
curl -o scrutinizer-checksums.txt -k https://127.0.0.1/plixer-repo/scrutinizer/VERSION/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
scrutinizer-install.run
file as theroot
,plixer
(recommended), orec2-user
user.x.x.x.x
should be replaced with the IP address or hostname of the offline repository host.
REPO_HOST=local LOCAL_REPO_BASEDIR=/var/db/big/offline ./scrutinizer-install.run -- -kImportant
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.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) orpasswords
.
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.