Try it free

Troubleshooting fapolicyd on private Synthetic locations

  • Latest Dynatrace
  • Troubleshooting
  • Published Nov 06, 2026

This page helps you find the missing fapolicyd rule when the ActiveGate, the Synthetic engine, or a monitor on a private Synthetic location doesn't work. For the full rule set and how to apply it, see Requirements for private Synthetic locations or, in Classic, Requirements for private Synthetic locations in Classic.

To find a missing rule, check the audit log: sudo ausearch -m FANOTIFY -i. It shows each blocked program, but not the file it tried to open. To see the files, run fapolicyd in debug mode, as described in the Red Hat documentation on troubleshooting problems related to fapolicyd. Afterwards, run sudo systemctl reset-failed fapolicyd and sudo systemctl start fapolicyd.

If the ActiveGate or the Synthetic engine doesn't start, don't rely on systemctl status. The unit can show active or Result=success, and the wrapper script prints Dynatrace Synthetic Engine started even when the engine doesn't run. Check the logs named below instead.

ActiveGate doesn't start

Check the logs in /var/log/dynatrace/gateway/, then add the matching rules to your rules file.

dynatracegateway-start_<timestamp>.log shows …/launcher/dynatracegateway: Operation not permitted

allow perm=execute exe=/usr/bin/bash : path=/opt/dynatrace/gateway/launcher/dynatracegateway ftype=application/x-executable trust=0
allow perm=execute exe=/opt/dynatrace/gateway/launcher/dynatracegateway : path=/opt/dynatrace/gateway/jre/bin/java ftype=application/x-executable trust=0

DynatracegatewayLauncher_<timestamp>.log shows libjli.so: cannot open shared object file or NoClassDefFoundError

allow perm=open exe=/opt/dynatrace/gateway/jre/bin/java : dir=/opt/dynatrace/gateway/jre/lib/ ftype=application/x-sharedlib trust=0
allow perm=open exe=/opt/dynatrace/gateway/jre/bin/java : dir=/opt/dynatrace/gateway/lib/ ftype=application/java-archive trust=0

dynatracegateway.*.log shows Failed to enable ZStd compression support or Failed to enable Snappy compression support

The ActiveGate runs, but falls back to gzip for HTTP request encoding.

allow perm=open exe=/opt/dynatrace/gateway/jre/bin/java : path=/opt/dynatrace/gateway/lib/native/libzstd-jni.so ftype=application/x-sharedlib trust=0
allow perm=open exe=/opt/dynatrace/gateway/jre/bin/java : path=/opt/dynatrace/gateway/lib/native/libsnappyjava.so ftype=application/x-sharedlib trust=0

After each failed start, the ActiveGate watchdog waits twice as long before the next retry. After you change the rules, restart dynatracegateway instead of waiting for the next retry.

Synthetic engine doesn't start or never reaches Running

Check the logs, then add the matching rules to your rules file.

journalctl -u vuc shows setenv.sh: line 102: /opt/dynatrace/synthetic/jre/bin/java: Operation not permitted, New main PID … does not exist or is a zombie, or status=4/NOPERMISSION

allow perm=execute exe=/usr/bin/bash : path=/opt/dynatrace/synthetic/jre/bin/java ftype=application/x-executable trust=0
allow perm=execute exe=/usr/bin/bash : path=/opt/dynatrace/synthetic/vucontroller/vucwrapper ftype=application/x-executable trust=0
allow perm=execute exe=/opt/dynatrace/synthetic/vucontroller/vucwrapper : path=/opt/dynatrace/synthetic/jre/bin/java ftype=application/x-executable trust=0

journalctl -u vuc shows libjli.so: cannot open shared object file

allow perm=open exe=/opt/dynatrace/synthetic/jre/bin/java : dir=/opt/dynatrace/synthetic/jre/lib/ ftype=application/x-sharedlib trust=0

/var/log/dynatrace/synthetic/VucwrapperLauncher_<timestamp>.log shows NoClassDefFoundError: org/apache/logging/log4j/status/StatusListener

allow perm=open exe=/opt/dynatrace/synthetic/jre/bin/java : dir=/opt/dynatrace/synthetic/vucontroller/lib/ ftype=application/java-archive trust=0

The engine never reaches Running and restarts about every two and a half minutes

Java can't start its helper processes. /var/log/dynatrace/synthetic/vuc-http.log can show Cannot run program "/opt/dynatrace/synthetic/jre/bin/java": error=1, Operation not permitted.

allow perm=execute exe=/opt/dynatrace/synthetic/jre/bin/java : path=/opt/dynatrace/synthetic/jre/lib/jspawnhelper ftype=application/x-executable trust=0
allow perm=execute exe=/opt/dynatrace/synthetic/jre/lib/jspawnhelper : path=/opt/dynatrace/synthetic/jre/bin/java ftype=application/x-executable trust=0

vuc-http.log shows HTTP monitor executor process not alive right after start, and the newest /var/log/dynatrace/synthetic/executors/*StdErr.log shows NoClassDefFoundError: org/slf4j/LoggerFactory

The HTTP monitor executor starts and exits immediately, and the engine restarts about every two and a half minutes.

allow perm=open exe=/opt/dynatrace/synthetic/jre/bin/java : dir=/opt/dynatrace/synthetic/vucontroller/libhttpexecutor/ ftype=application/java-archive trust=0

No error in the logs

Without this rule, monitors keep working, but the audit log shows blocked file opens by the Synthetic engine.

allow perm=open exe=/opt/dynatrace/synthetic/jre/bin/java : dir=/var/tmp/dynatrace/synthetic/ ftype=application/x-sharedlib trust=0

Browser monitors don't run

Starting with version 1.351, private Synthetic locations on Red Hat Enterprise Linux 9 and Rocky Linux 9 use Chrome for Testing, installed in /usr/lib/chrome_for_testing/. Chrome for Testing isn't an RPM package, so fapolicyd doesn't trust it. On a new installation or after an upgrade, the browser check fails with Operation not permitted, the Synthetic engine restarts about every six minutes, and browser monitors don't run.

allow perm=execute exe=/usr/bin/bash : path=/usr/lib/chrome_for_testing/chrome-linux64/chrome ftype=application/x-executable trust=0
allow perm=execute exe=/opt/dynatrace/synthetic/jre/lib/jspawnhelper : path=/usr/lib/chrome_for_testing/chrome-linux64/chrome ftype=application/x-executable trust=0
allow perm=execute exe=/usr/lib/chrome_for_testing/chrome-linux64/chrome : path=/usr/lib/chrome_for_testing/chrome-linux64/chrome ftype=application/x-executable trust=0
allow perm=execute exe=/usr/lib/chrome_for_testing/chrome-linux64/chrome : path=/usr/lib/chrome_for_testing/chrome-linux64/chrome_crashpad_handler ftype=application/x-executable trust=0
allow perm=execute exe=/usr/lib/chrome_for_testing/chrome-linux64/chrome_crashpad_handler : path=/usr/lib/chrome_for_testing/chrome-linux64/chrome_crashpad_handler ftype=application/x-executable trust=0
allow perm=open exe=/usr/lib/chrome_for_testing/chrome-linux64/chrome : dir=/usr/lib/chrome_for_testing/chrome-linux64/ ftype=application/x-sharedlib trust=0

ICMP checks fail on a host with OneAgent

OneAgent adds liboneagentproc.so to /etc/ld.so.preload, and every process loads it. fapolicyd blocks the library, and ICMP requests of network availability monitors fail with object '/lib64/liboneagentproc.so' … cannot be preloaded.

allow perm=open all : path=/usr/lib64/liboneagentproc.so ftype=application/x-sharedlib trust=0

fapolicyd reports the resolved path. On Red Hat Enterprise Linux 9, /lib64 is a link to /usr/lib64, so the rule uses /usr/lib64.

Related tags
Digital Experience