Tips for how to troubleshoot certain installation issues
These are the statuses you may see in the OverOps application:
|The installation completed successfully, the Collector is attached and monitoring the application(s).|
|You need to install the Collector or you need to verify that the Collector is connecting to the backend.|
|You still need to install both the Collector and the Micro-Agent.|
|The Collector is running but there’s no Micro-Agent connected to it.|
No OverOps Agents Found
If you get a message during the installation process that no OverOps Micro-Agents could be found, this may indicate that the application(s) attached to the Micro-Agents aren’t running. Verify that the applications are running (or restart them) and then check this step again.
It could also mean that the folder with the Takipi installation has the wrong permissions or Owner depending on your OS and the user under which your application is running has no rights to the Takipi installation folder.
Make sure that the Takipi folder and all subfolders and files have the same Owner / Rights as the user under which your application is running!
-agentlib vs -agentpath
To attach the OverOps agent to your application you use either -agentlib or -agentpath java argument. The -agentlib argument is created when you use one of our installers that required root access.
If you are not sure or the takipi agent cannot be found use -agentpath instead. In general, it is a good practice to use -agentpath to account for different installation paths than the default.
Please validate the paths!
“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:
- 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:
If you cannot find the Takipi folder, re-install OverOps.
- 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:
|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:
- 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.
- Validate that you have enough disk space available. The collector requires at least 11% free diskspace to run.
- 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:
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: email@example.com.
Installation Key Lost
The installation key can be retrieved through one of the following methods:
- Search your Inbox for firstname.lastname@example.org.
- When you install OverOps on a machine, the key is stored in the secret.key file located in
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: