Find out how to solve problems related to installing OneAgent on Linux.
OneAgent is shipped with trusted Dynatrace SSL certificates, which are used to verify that OneAgent connects successfully to Dynatrace Server or ActiveGate.
If your environment uses a proxy (thereby requiring an update to the remote server's SSL certificate), then you may encounter a
Server certificate check failed message during the initial connection check.
To resolve this issue, specify the trusted proxy certificate that is to be utilized by OneAgent. To do this, provide a copy of your proxy's SSL certificate as a file called
custom.pem in the
/var/lib/dynatrace/oneagent/agent/customkeys directory. The file
custom.pem should contain the proxy’s certificate along with any intermediate certificates as required.
One of the following may have occurred
- The process isn’t supported by our monitoring technology. You can always check which process types Dynatrace supports.
- The process isn’t working on your server. Please ensure that your servers are running and that the processes are operational.
- There is delay in communication between Dynatrace and your Dynatrace OneAgent. If this is the case, please wait a few moments and try again.
- Your Dynatrace OneAgent isn’t working properly. Go to Settings > Monitoring overview to confirm that monitoring is enabled for the host running your software.
If you're still unable to resolve this issue, please contact us at Dynatrace answers. Also, consider installing Dynatrace OneAgent on a different machine.
Following installation of Dynatrace OneAgent, your Apache web server must be completely restarted to enable monitoring. To do this correctly, it's important to understand the difference between "partial" and "complete" restarts. In the case of partial restarts, the main Apache process re-reads its configuration files, re-opens its log files, and then restarts its worker processes. Dynatrace OneAgent however, requires a complete Apache web server restart in which all workers and—most importantly—the main Apache process are shut down entirely and then restarted.
See Stopping and Restarting Apache HTTP Server for more information on the different types of available restarts.
How to perform a complete restart
You may be accustomed to restarting Apache by issuing an
apachectl restart command. Oddly, this command only results in a partial Apache restart.
To execute a complete Apache restart and enable deep monitoring with Dynatrace OneAgent, you need to first invoke a complete shutdown using the
apachectl stop command. Only following this step can you restart the server using
apachectl start .
It's fine to use
service apache2 restart on Ubuntu systems. Note however that whatever commands you use, you'll likely need superuser rights (sudo).
Dynatrace OneAgent consists of different processes that communicate via a TCP port with a watchdog. At startup, Dynatrace OneAgent watchdog attempts to open the first available port between port
50100. In some cases you may need this port for your own applications that are started after Dynatrace OneAgent. In such cases, you can change the port range that the Dynatrace OneAgent watchdog uses by modifying the file
watchdoguserconfig.conf is located in the following directory:
- On Linux at
- On Windows at
You can change the watchdog listening port by modifying the following line in the file:
From, for example:
Be sure to restart Dynatrace OneAgent service following your changes.
Please see Which network ports does Dynatrace Server use? for information on the ports used by Dynatrace.
If you see an
Operation not permitted error in the Linux console or the installation logs, make sure that OneAgent installation isn't blocked by antivirus software installed on the host.