Self-hosted Hyperion server: removing current Hyperion software

Applies to:

• Hyperion version 2.11.0 or later
• Hyperion Core Client version 2.x or later

OS requirements:

• CentOS 7 / RHEL 7 / Ubuntu 16.04

Note: current Hyperion software will not work on earlier OS versions.

These instructions allow the removal of the Hyperion and Hyperion Core Client software components from a self-hosted Hyperion server that is currently associated with a Core account, as in the following scenarios:

Core account cancellation : if a Core subscription is no longer active, continued operation of the Hyperion software is not permitted, as described in this article.

Core account changes : if a self-hosted Hyperion server needs to be moved from one company's Core account to another Core account, first perform the removal instructions in this article, then associate the self-hosted Hyperion server with the new Core account using the installation steps in this article.

Part 1 : removal of Hyperion/ Hyperion Core Connector software

CentOS 7 / RHEL 7

Perform the following commands at the terminal:

sudo systemctl stop redis.service sputnik.service sputnik-ui.service proton.service

sudo yum remove -y teradek-sputnik proton 

sudo rm -rf /opt/teradek /etc/proton.toml /etc/sputnik*.conf /var/log/sputnik* /var/log/proton*

Ubuntu 16.04

Perform the following commands at the terminal:

sudo systemctl stop redis.service sputnik.service sputnik-ui.service proton.service

sudo dpkg -P teradek-sputnik proton 

sudo rm -rf /opt/teradek /etc/proton.toml /etc/sputnik*.conf /var/log/sputnik* /var/log/proton*

Part 2 : removal of Hyperion listing from Core inventory

Log in to the Core account that had the Hyperion server removed and go to Inventory > Hyperions. The Hyperion server should show as Offline, and allow selection / removal of the server from the list using the drop-down menu.