Re-Installing OverOps

The OverOps Collector that runs the daemon process called takipi-service or TakipiService.exe, keeps the state mainly under the /opt/takipi/work folder. During the upgrade procedure, this state is preserved, as well as any configuration changes made in takipi.properties file, so that only the binaries are upgraded. However, in some rare cases - either when the state gets corrupted (the server runs out of disk space) or if a version is faulty - you may be prompted to carry out a complete re-installation, including uninstalling and then re-installing OverOps. This procedure erases the properties and the installation key, therefore, you should save the properties and the installation key in a temporary location location so that you can access them easily..

Changes to the takipi.properties file require restarting the Collector. Click here to learn how to restart the Collector.

The Collector also keeps the state of the Micro-Agents that are communicating with it. Because OverOps maintains information about each Micro-Agent in the /opt/takipi/work folder, removing that folder breaks that connection between the Micro-Agent and the Collector, and a VM restart will be required to re-establish the link.