Installation Troubleshooting Follow

Here are some tips for how to troubleshoot certain installation issues.

Contents

Connection Statuses

Connection Problems

"OverOps is not active" Message

Lost Installation Key

Restarting the OverOps Collector

 

Connection Statuses 

These are the statuses you may see in the OverOps application:

Status Explanation
image.png The installation completed successfully, the Collector is attached and monitoring the application(s).
image__1_.png

You need to install the Collector or you need to verify that the Collector is connecting to the backend.

image__2_.png You still need to install both the Collector and the Micro-Agent.
image__3_.png The Collector is running but there's no Micro-Agent connected to it.

 


Connection Problems 

"OverOps is not active" Message

The installation instructions guide you through the installation process from start to finish, including attaching OverOps to the application. If the setup was incomplete or unsuccessful, an 'OverOps is not active' message is displayed. The different message types with possible solutions are described below.

OverOps is not active - No communication

 

This message indicates that the OverOps service installed on your machine/server was unable to communicate with the OverOps backend. To solve the problem, troubleshoot as follows:

  1. Verify that OverOps is installed on the same machine as the machine you wish to monitor and that the Takipi folder can also be found on that machine:

    Linux  /opt/takipi
    Windows   C:\Takipi
    macOS   /Library/Takipi

    If you cannot find the Takipi folder, re-install OverOps.
  2. If OverOps is installed, verify that the service  called Takipi service or Takipi (depending whether you installed Java or .NET) is running on your machine. The service must run continuously, communicating with the OverOps backend.

    Linux From a terminal, run: ps -ef | grep -v grep | grep takipi-service and find the Process ID. If the Takipi service is not running, start it by running either sudo service takipi start -OR- sudo start takipi
    Windows From the services screen, verify that a service called Takipi-service or Takipi is running. If that service is not running, right-click and select Start.
    macOS From a terminal, run: ps -ef | grep -v grep | grep takipi-service and find the Process ID. If the Takipi service is not running, start it by running sudo launchctl load /Library/LaunchDaemons/com.takipi.service.plist
  3. If OverOps was installed and the service is running on the server, check the Internet connection. The service requires a constant connection to function properly.
  4. Verify that the proxy server/VPN is not blocking OverOps. OverOps communicates via port 443 (Standard HTTPS). If you're working via a proxy server or a local/company firewall, verify that:
    • Port 443 is open for outgoing HTTPS/SSL communication.
    • takipi-service.exe (Win)/takipi-service (Linux/macOS) is authorized to send and receive data.
    • The proxy allows access to:
      • backend.takipi.com
      • prod1-sparktale.s3.amazonaws.com
      • d16f8x4wee2da2.cloudfront.net

Note: Adding these servers to the proxy requires restarting the Collector.

If these settings seem to be correct, but you still see the same message while testing the connection, use the live chat or email us at: hello@overops.com.

 


Installation Key Lost

The installation key can be retrieved through one of the following methods:

  1. Search your Inbox for hello@overops.com.
  2. When you install OverOps on a machine, the key is stored in the secret.key file located in
    Linux /opt/takipi/installation.key
    Windows  C:\Takipi\work\secret.key
    macOS  /Library/Takipi/work/secret.key

In addition, you can generate a new key, however, data collected and encrypted using the previous key will no longer be available. Click here to learn more.

 


Restarting the OverOps Collector

To stop or restart the Collector:

  Stop Start
Linux Run: sudo service takipi stop Run: sudo service takipi start
Windows   Run services.msc and stop TakipiService Run services.msc and start TakipiService
macOS Run: sudo launchctl unload /Library/LaunchDaemons/com.takipi.service.plist  Run: sudo launchctl load /Library/LaunchDaemons/com.takipi.service.plist 

Comments

0 comments

Join Conversation