Troubleshoot ActiveGate

Find out how to solve problems related to ActiveGate.

Can't connect to Environment ActiveGate


If you've installed OneAgent with an existing proxy setting that doesn't allow connection to Environment ActiveGate, OneAgent won't be able to connect to Environment ActiveGate directly. To enable OneAgent to connect to Environment ActiveGate, please re-install OneAgent with no proxy or proxy-related setting.

Failed to enable Snappy compression support java.lang.UnsatisfiedLinkError in Linux


ActiveGate by default uses snappy compression and loads a native library of Snappy-Java from the ActiveGate temp directory (the native library is extracted from a snappy JAR distributed with ActiveGate so that no native code is downloaded from the Internet). In case code execution in the temp directory isn't allowed, ActiveGate falls back to another type of compression and reports SEVERE in the log file:

2018-03-13 01:16:57 UTC SEVERE [<collector>] [RequestEncoder] Failed to enable Snappy compression support java.lang.UnsatisfiedLinkError: /var/opt/dynatrace-managed/security-Gateway/tmp/snappy-1.1.2-4d99d023-9e45-4e01-b482-aa9c1ba3cfe5-libsnappyjava.so: /var/opt/dynatrace-managed/security-Gateway/tmp/snappy-1.1.2-4d99d023-9e45-4e01-b482-aa9c1ba3cfe5-libsnappyjava.so: failed to map segment from shared object: Operation not permitted

When execution code from the temp directory isn't possible, ActiveGate may still use snappy compression by using java.io.tmpdir with the required execute permission defined in the configuration file. To enable this:

  1. Define the java.io.tmpdir directory in /opt/dynatrace/gateway/launcher/dynatracegateway.ini as follows:
    -Djava.io.tmpdir=<temp_dir_with_exection_permitted>
  2. Restart ActiveGate

Too many open files in Linux


The Linux operating system has a limit on the number of open files that a process can handle. This limit is set automatically in ActiveGate version 1.145, so it's highly recommended that you update to ActiveGate version 1.145 or higher.

If you choose not to update to v1.145 or higher, set the number of open files to at least 500000 for user root to ensure proper operation. The current limit can be checked via the ulimit -H -n command. Note that this limit is set per user, so if you run ActiveGate on a different user than root, you'll need to update the associated configuration file accordingly.

How do I configure the open-files limit?

To configure the permitted number of open files

  1. Create the file /etc/security/limits.d/80-dynatrace.conf with the following content: root hard nofile 500000.
  2. Log out, log back in, and restart ActiveGate.

Make sure the system limit for the number of open files is higher. To view the system limit, execute the following command:
cat /proc/sys/fs/file-max.

If required, follow the steps below to change the system limit

  1. Add fs.file-max=1000000 to /etc/sysctl.d/80-dynatrace.conf.
  2. Execute sysctl -p /etc/sysctl.d/80-dynatrace.conf to apply the new value.

Can't connect VMware vCenter to Dynatrace. vCenter or ESXi host displays "Unknown host" error


Dynatrace probably can't connect due to a network security setting that's in effect. To resolve this issue, you can exclude the host from proxy communication by specifying the non-proxy hosts:

Backup

Make sure you back up all configuration files before manually making any changes.

To specify non proxy hosts

On ActiveGate, edit the /opt/dynatrace/gateway/launcher/dynatracegateway.ini file.

Define the -Dhttp.nonProxyHosts parameter:

-Dhttp.nonProxyHosts=<hostname>

See Excluding hosts from proxy communication on the Setting up proxy for ActiveGate page.