Uninstalling or Reconfiguring Paragon Insights
This section describes the following tasks:
Uninstalling Paragon Insights
Paragon Insights on Ubuntu
To uninstall Paragon Insights (formerly HealthBot) on Ubuntu, enter the following command:
$ sudo apt-get [remove|purge] healthbot
The remove and purge options both perform
the same action. You can use either to uninstall Paragon Insights.
For example:
$ sudo apt-get purge healthbot
Paragon Insights on CentOS
When uninstalling Paragon Insights on CentOS, you might see warnings indicating that some of the package files are not found. You can safely ignore these warnings.
To uninstall Paragon Insights on CentOS:
Verify the SELinux mode, and if set to enforcing change it to permissive. This is required to allow the uninstall procedure to run.
$ getenforce Enforcing $ sudo setenforce 0 $ getenforce Permissive
Uninstall the Paragon Insights package and its components using the following format:
$ sudo yum remove <healthbot-package-name>
For example:
$ yum list installed | grep healthbot healthbot.noarch 2.0-2.1 installed $ sudo yum remove healthbot.noarch sudo yum remove healthbot.noarch Loaded plugins: fastestmirror Resolving Dependencies --> Running transaction check ---> Package healthbot.noarch 0:2.0-2.1 will be erased … <answer ‘y’ to prompts as needed> … Running transaction … Removed healthbot Erasing : healthbot-2.0-2.1.noarch 1/1 Verifying : healthbot-2.0-2.1.noarch 1/1 Removed: healthbot.noarch 0:2.0-2.1 Complete!Note:This procedure does not uninstall all of the software dependencies that were installed for Paragon Insights during installation.
Reset the SELinux mode to enforcing, if applicable.
$ getenforce Permissive $ sudo setenforce 1 $ getenforce Enforcing
Reconfiguring Paragon Insights
Use the healthbot reconfigure command to:
Change from a single-node installation to a multinode installation, or vice versa
Change the Paragon Insights server’s IP address
Change SSL certificates
For example:
$ sudo healthbot reconfigure ℹ️ Please have a look at below messages and acknowledge them to proceed: 1. Paragon Insights free model/freemium license tier is not available in this version. A valid license (trial or commercial) is needed to use Paragon Insights features. 2. The format of license key has been changed due to business reasons in this version. The system may have contained the older format of license keys, which are not valid now. You can log into the Juniper Agile Licensing Portal and choose to revoke the existing license and then re-activate the license to a new software version (that will provide you with a new format license key). This newly activated license can be added to the system post upgrade. 👨 Do you want to proceed? [Y/n] Y 👨 Do you want to reconfigure SSL certificates? [y/N]y 👨 Do you want system to create and use a self-signed SSL certificate? [Y/n] Y [executing ..] openssl req -nodes -x509 -newkey rsa:4096 -keyout /var/local/healthbot/certs/key.pem -out /var/local/healthbot/certs/cert.pem -days 36525 -subj "/C=US/ST=Ca/L=Svl/O=Juniper Networks/OU=Org/CN=localhost" -extensions SAN -reqexts SAN -config /tmp/ssl.conf [executing ..] rm -f /tmp/ssl.conf 📝 Creating /var/local/healthbot/healthbot.conf config file.. ℹ️ Checking space for docker images 🐳 Loading docker images. This may take some time.. 100%|███████████████████████████████████████████████████████████████████| 50/50 [01:43<00:00, 2.08s/it] ✅ Docker images successfully loaded ✅ Done making directories ℹ️ User has quit previous setup to reset iptables. Ignoring API server unreachability. 👨 Do you want to reconfigure kubernetes cluster? [y/N] y ╭────────────────────────────────────╮ │ │ │ Installing new Kubernetes cluster │ │ │ ╰────────────────────────────────────╯ ╭─────────────────────────────────────────╮ │ │ │ Existing cluster details found │ │ Master nodes: ['10.xxx.165.xxx'] │ │ Worker nodes: [] │ │ Master scheduling: True │ │ Ingress virtual IP: ['10.102.xxx.xxx'] │ │ │ ╰─────────────────────────────────────────╯ 👨 Do you want to use the same cluster details? [Y/n] Y ℹ️ Using pod CIDR: 10.xxx.0.0/16 ℹ️ Using service CIDR: 10.xx.0.0/12 ╭───────────────────────────────────────────────────────────────────────────────────╮ │ │ │ Pod CIDR and Service CIDR can be modified using one of the below approaches │ │ Interactive installation : │ │ - Set the environment variables "HB_POD_CIDR" and "HB_SERVICE_CIDR" │ │ - For non-root user, Use 'sudo -E' instead of 'sudo' to use the │ │ existing environment variables │ │ Silent installation : │ │ - Set the "pod_cidr" and "service_cidr" values in "healthbot.conf" file │ │ │ │ Post changing the configuration, stop all the healthbot services and reconfigure │ │ healthbot using "healthbot reconfigure" command. │ │ │ ╰───────────────────────────────────────────────────────────────────────────────────╯ ℹ️ Offline package not found ✅ Created inventory file ✅ Prepared cluster for new installation ✅ All node(s) validated successfully ✅ Installed Kubernetes cluster successfully ✅ Successfully executed post-install tasks on all host(s) ℹ️ Copying /etc/kubernetes/admin.conf directory to /var/local/healthbot/k8s.conf on master.. ℹ️ Finished copying. ℹ️ Patching docker registry: key=, value=, operator=Exists, effect=NoSchedule ℹ️ Patching docker registry: key=healthbot.juniper.net/dedicated, value=tsdb, operator=Equal, effect=NoExecute [executing ..] kubectl label nodes 10.xxx.xxx.215 healthbot.juniper.net/tsdb=10-102-165-215 --overwrite ✅ Copied helper files to input directory ⌛ Pushing images to registry ✅ Registry is ready 100%|███████████████████████████████████████████████████████████████████████| 50/50 [03:03<00:00, 3.67s/it] ✅ Successfully pushed images to registry ✅ Installation successful. Please run 'healthbot start' ——————————————————————————————————————————————————————————————————————
You can also reconfigure Paragon Insights using a configuration file. For example:
sudo healthbot reconfigure -c /path/configuration-file.conf
In this example, Paragon Insights is reconfigured to whatever settings are defined in the configuration file. For more information on the configuration file, see Using the Silent Installer.