Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Selfmonitoring agents disconnected


Can somebody tell please the permitions on library? I see the only for read. Is the library of agent should be executive?

The agents DT_Server and DT_Server_Frontend are disconnected.




@Oleksandr M.

Did you restart the services of server and frontend?

1. Yes, but the 9999 port doesnot listening.

Please tel me the wright permitions which should be on directory ./selfmonitoring/

2. In selfmonitoring logs:

'localhost' returned multiple addresses

2017-10-11 11:19:53 [6c24e8c2] info [native] Could not retrieve LoadBalancing configuration from localhost:9999 (111): Connection refused
2017-10-11 11:19:53 [6c24e8c2] warning [native] Connection::connect(): Address resolution for 'localhost' returned multiple addresses. Using first returned:
2017-10-11 11:19:58 [6c24e8c2] severe [native] Exception while connecting to Server/Collector localhost, info:<connect()/apr_socket_connect(), 111, Connection refused>

cat /erc/hosts localhost localhost.localdomain localhost4 localhost4.localdomain4

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

Maybe need to set instead of localhost in dtserver.ini config?


@Oleksandr M.

As per my understanding you should contact your network team regarding opening the 9999 port.

Also if possible check for the firewall rules set in your environment.




firewalld is disabled on system

But selinux is there

How it should be started?

I see that Selfmonitoring not started. SelfmonitoringLauncher.log

2017-10-10 20:51:52 [5f61d836] info    [native] -----------------------------------------------------------------------------
2017-10-10 20:51:52 [5f61d836] info [native] Dynatrace Collector, Copyright (C) 2004-2016, Dynatrace
2017-10-10 20:51:52 [5f61d836] info [native] -----------------------------------------------------------------------------
2017-10-10 20:51:52 [5f61d836] info [native] Native Launcher version: - built 2016.09.16
2017-10-10 20:51:52 [5f61d836] info [native] Launcher configuration summary for Dynatrace Collector:
2017-10-10 20:51:52 [5f61d836] info [native] Launcher: /opt/dynatrace/dynatrace-6.5/server/selfmonitoring/dtselfmon
2017-10-10 20:51:52 [5f61d836] info [native] Java VM: /opt/dynatrace/dynatrace-6.5/jre/bin/java
2017-10-10 20:51:52 [5f61d836] info [native] Java version: 1.8.0_102 64-Bit
2017-10-10 20:51:52 [5f61d836] info [native] Startup jar: /opt/dynatrace/dynatrace-6.5/server/selfmonitoring/./plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
2017-10-10 20:51:52 [5f61d836] info [native] Working directory: /opt/dynatrace/dynatrace-6.5/server/selfmonitoring/.
2017-10-10 20:51:52 [5f61d836] info [native] Configuration file: /opt/dynatrace/dynatrace-6.5/server/selfmonitoring/dtselfmon.ini
2017-10-10 20:51:52 [5f61d836] info [native] Pid file: /var/run/
2017-10-10 20:51:52 [5f61d836] info [native] Native watchdog enabled, port: 50003, timeout: 180 sec (timeout for graceful shutdown: 300 sec)
2017-10-10 20:51:52 [5f61d836] info [native] Process created successfully, pid: 3865
2017-10-10 20:51:55 [5e320876] info [java ]
2017-10-10 20:52:01 [5eb2f876] info [java ] ... last message repeated 2 times ...
2017-10-10 20:52:01 [5eb2f876] info [native] New connection on port 50003 received
2017-10-10 20:52:01 [5eb2f876] info [native] Dynatrace Collector started successfully
2017-10-11 11:19:13 [5f61d836] info [native] Process 3865 terminated, exitcode: 0
2017-10-11 11:19:14 [5f61d836] info [native] Dynatrace Collector terminated

DynaMight Leader
DynaMight Leader

Hello @Oleksandr M.

Have a look on the following for the 'SElinux and AppMon product issues on Redhat'



Hello, I saw this. I will try to disable but at the last try

Also there in logs:

I think need to try change chmod 777 to all /selfmonitoring folder

2017-10-11 11:20:16 WARNING [Server] Failed to launch agent-based self-monitoring: com.dynatrace.diagnostics.server.Server startServer:1458 Destination '/opt/dynatrace/dynatrace-6.5/server/selfmonitoring/conf/sensors/plugins/com.dynatrace.diagnostics.knowledgesensor.dotnet.aspnet' cannot be written to

Hello all, I figured out in this case. The problem was in that the owner of some libraries was root. But server starts with dynatrace user, he could not had the write permissions. That is because in the past the server was started by root, and the owner for several librarys was changed to root.

The resolution - just chown -R dynatrace:dynatrace ./server/selfmonitoring/conf/sensors/plugins