OverOps is not active - No communication
- Verify that OverOps is installed on the same machine as which you wish to monitor and that the Takipi folder is can be found on that machine:
Linux /opt/takipi Windows C:\Takipi macOS /Library/Takipi
If you cannot find The Takipi folder, re-install OverOps.
- If OverOps is installed, verify that the Takipi service 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 the Takipi-service is running. If the Takipi 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
- If OverOps was installed and the service is running on the server, check the Internet connection. Takipi requires a constant connection to function properly.
- 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:
- If all 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: firstname.lastname@example.org.
OverOps is not active - No connected JVMs found/Only 32bit JVMs found/-agentlib:TakipiAgent argument is misplaced
- When you start the JVM, verify that the -agentlib:TakipiAgent is set up correctly: located in the right place, no mistypes, and a space separating it from other startup arguments.
Note: -agentlib is a JVM argument and must appear before the -jar/-cp/-classpath arguments. Verify that you followed the instruction to connect with the correct launcher.
- Verify that the JVM is running when clicking Test Installation. OverOps cannot monitor JVM/applications that have not been started.
- Verify that OverOps was successfully loaded:
Add -Dtakipi.silent=false to the startup arguments. This argument adds notifications to the application console, providing more information regarding the installation. If OverOps was loaded, the following messages are displayed:
OverOps is loading and then OverOps loaded successfully.
- Verify that the JVM argument was added to the JVM to be monitored.
- Verify that the OverOps Agent is a 64-bit JVM. OverOps does not monitor 32-bit processes. If you’re running a 32-bit JVM, download 64-bit Java and try again.
- Verify that you’re running an Oracle/OpenJDK Java. For macOS users, Apple JVMs are not supported. Download Oracle’s 64-bit Java and try again.
- OverOps looks for errors within the customer's code, known 3rd party libraries are not monitored. If the JVM only contains 3rd party code, an error message may be displayed when testing the installation. If such a message is displayed after OverOps was loaded, check that the JVM OverOps is connected to contains your code. If not, remove the 3rd party library and try again.
Note: To turn off this limitation and monitor 3rd party code, click here for instructions.
If you're still having trouble, click here or use our live chat to contact the OverOps support team.
The installation key can be retrieved through one of the following methods:
- Search your Inbox for email@example.com.
- When you install OverOps on a machine, the key is stored in the secret.key file located in
Linux /opt/takipi/work/secret.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.