OverOps is not active - No communication
- Make sure OverOps is installed on the same machine you wish to monitor. Please verify that the Takipi folder exists on that machine:
Linux /opt/takipi Windows C:\Takipi macOS /Library/Takipi
If this folder doesn't exist, please re-install OverOps.
- If OverOps is installed, make sure Takipi’s service is running on your machine. The service needs to be running continuously and communicating with OverOps' backend.
Linux Run in a terminal: ps -ef | grep -v grep | grep takipi-service and make sure there is a PID. If the Takipi service is not running, start it by running either sudo service takipi start -OR- sudo start takipi Windows Open your services screen and make sure the Takipi-service is running. If the Takipi service is not running, right click and start it. macOS Run in a terminal: ps -ef | grep -v grep | grep takipi-service and make sure there is a PID. If the Takipi service is not running, start it by running sudo launchctl load /Library/LaunchDaemons/com.takipi.service.plist
- Check your internet connection - If OverOps was installed and the service is running on your server, make sure you're able to connect to the internet. Takipi requires a continuous internet connection to function properly.
- Make sure your 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, please make sure:
- 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
- Make sure the -agentlib:TakipiAgent is set up correctly (located in the right place, no mistypes, with a space separating it from other startup arguments) when you start your JVM. Also note that -agentlib is a JVM argument and it must be written before the -jar/-cp/-classpath arguments. Be sure you followed the specific instructions for the launcher you’re trying to connect OverOps to. If placed incorrectly, OverOps will not be able to connect and monitor your JVM.
- Make sure your JVM is running when you click on “test connection” - If your JVM/app has not been started, OverOps will not be able to monitor it for exceptions/slowdowns.
- Verify that OverOps was successfully loaded: Add -Dtakipi.silent=false to the startup arguments. This will add notifications to your app's console, and allow you to get more info regarding the installation. If OverOps was loaded, these messages should be displayed there: [OverOps is loading] followed by [OverOps loaded successfully].
- Make sure you added the JVM argument to the same JVM you’re trying to monitor.
- Make sure you’re connecting the OverOps agent to a 64-bit JVM. OverOps does not monitor 32-bit processes. If you’re running a 32-bit JVM, download 64bit Java and try again.
- Make sure you’re running an Oracle / OpenJDK Java. macOS users: Apple’s JVMs are not supported. Please download Oracle’s 64-bit Java and try again.
- OverOps was loaded, but you still get an error message? Make sure you’ve connected OverOps to a JVM that contains your own code. Since OverOps was designed to find errors within your code, it won’t monitor known 3rd party libraries. If the JVM you’re running only contains 3rd party code, you might get an error message when testing the installation. Please connect OverOps to a JVM containing your own code and try again. Note: If you'd like to turn off these limitation and monitor 3rd party code, click here for instructions.
- Everything is set up correctly, but you’re still getting this message? We’re happy to help. Click here or use our live chat to get in touch.
If you've lost or forgotten your secret key, you can still retrieve it through one of the following methods:
- Search for the key in your inbox. The key which was generated for you when you signed up was emailed to you from 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
You can also generate a new key. However, data which was collected and encrypted using your previous key will no longer be available to you - Learn more.
|Windows||Run services.msc and stop TakipiService||Run services.msc and start TakipiService|