Troubleshooting Remote Data Processor

This article provides general troubleshooting tips for RDP, including troubleshooting for inactive RDP after an upgrade.

Prerequisite:

Table of contents:

See Upgrading a Remote Data Processor on Windows Servers for instructions on upgrading RDP.

Troubleshooting Inactive RDP After an Upgrade

If RDP is inactive or shows no heartbeat after an upgrade to v7.1.0, proceed with the following steps:

  1. Download the SSL certificate of your MI application from browser
  2. Access the RDP machine, place the downloaded certificate under C:\Program Files\Metric Insights\Data Processor\bin\jdk-23.0.1\lib\security\server.crt
  3. Run the Command Prompt as Administrator
  4. Open the directory with the certificate: cd C:\Program Files\Metric Insights\Data Processor\bin\jdk-23.0.1\lib\security
  5. Run the following command to add the SSL certificate to the JDK keystore: keytool -import -trustcacerts -alias <MI_hostname> -file server.crt -keystore cacerts
    • Replace <MI_hostname> with your application's hostname
  6. Restart the RDP service

General Troubleshooting Tips

1. Check If RDP Is Active

The list of Remote Data Processors helps to define whether the Data Processor profile is active and the connection was established:

  • If your Remote Data Processor is active, it will be shown in default black and the column Last Heartbeat Time will have a value equal to the time you started RDP Daemon Service plus up to 2 minutes.
  • If your Remote Data Processor is not active, it will be displayed in red. The column Last Heartbeat Time will have a value with the last time it successfully connected (if have ever been before) or be empty if never connected.

2. Restart Metric Insights Data Processor Windows Service

On the Windows machine where RDP was installed access Services. In the list of services find Metric Insights Data Processor Daemon service, Start or Restart the service.

3. Check System Resources on Windows Machine

If Windows service could never start up or stops within a few minutes check if you have enough CPU and Memory on the Remote Data Processor Server so the Remote Data Processor service doesn't consume too much system resources.

If you still encounter any problems please contact [email protected] for further investigation.

If Windows service could never start or stops in a couple of minutes, check whether there is enough CPU and Memory on the Remote Data Processor Windows machine so the Data Processor Daemon service doesn't consume too much system resources.

If you encounter any other problems establishing connectivity with Remote Data Processor please contact [email protected] for further investigation.