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

Java agent not connecting since fixpack 7.1.14

abder
Visitor
collector.log


Hi all,


We have an issue since we upgraded to 7.1.14.


One of our java agent is not connecting anymore to the collector/server. We never had this problem before that fixpack (works fine with 7.1.13).

Below is the log file of the dynatraceAgent (contains a connectivity error):

	2018-11-08 15:53:02 UTC [000001c8] info  [native] Loading collector peer list from d:/applis/dynatrace/dynatraceagent7.1/agent/conf/collectorlist.INT_PMSIGv2_APP_TOMCAT
2018-11-08 15:53:02 UTC [000001c8] info [native] 1 entries loaded
2018-11-08 15:53:02 UTC [000001c8] info [native] Dynatrace Bootstrap Agent 7.1.0.1803
2018-11-08 15:53:02 UTC [000001c8] info [native] Using d:/applis/dynatrace/dynatraceagent7.1 as Agent storage
2018-11-08 15:53:02 UTC [000001c8] info [native] Log file is d:/applis/dynatrace/dynatraceagent7.1/log/dt_INT_PMSIGv2_APP_TOMCAT_bootstrap_12684.0.log
2018-11-08 15:53:02 UTC [000001c8] info [native] Trying to connect to Collector for up to 20 seconds
2018-11-08 15:53:03 UTC [000001c8] info [native] Error connecting: connect()/apr_socket_connect(), 730061, Connection refused
2018-11-08 15:53:04 UTC [000001c8] info [native] ... last message repeated 1 time ...
2018-11-08 15:53:04 UTC [000001c8] info [native] Connected to Collector ***********************:9997
2018-11-08 15:53:04 UTC [000001c8] info [native] Handshake with Collector (7.1.14.1019) successful
2018-11-08 15:53:04 UTC [000001c8] info [native] Collector requests to use agent version 7.1.14.1019 (hash: 0008bec96098b2d7478efdf3794e6613)
2018-11-08 15:53:04 UTC [000001c8] info [native] Checking availability of requested agent binary windows-x86-64 with version 7.1.14.1019
2018-11-08 15:53:04 UTC [000001c8] info [native] Start loading local agent binary
2018-11-08 15:53:04 UTC [000001c8] info [native] Successfully loaded agent binary d:/applis/dynatrace/dynatraceagent7.1/agent/downloads/appmon/native/7.1.14.1019/windows-x86-64/dtagent.dll

From the collector side, we never have the usual message that confirms the connection (INFO [AgentPeerPool] added agent '...' to pool - number of agents: 16).

We have instead an exception related to the connectivity with the dynatrace server on port 8041 (see attached file collector.log).

We never nedded to use that port before. According to the documentation :

" 1 These ports are used for the Node.js Agent (Linux only) to connect the Collector to the Server."

Our java agent is hosted in a windows server 2012 with a tomcat 8 and java 8.

So I don't understand why is it trying to connect via that port and do you think this is the root cause of our problem ?

Thanks for any help.


Thanks


Abder


3 REPLIES 3

mathieu_chatte1
Advisor

Hello,

The log states "Connection refused", which would mean that either the host address / ip address or the port number is wrong for the collector, or the collector isn't up, or some firewall prevents the connection.

Is 8041 port openned between Collector and Server ?

Regards,

Mathieu


abder
Visitor

Hi Mathieu,

Thanks for replying.

Indeed this port hasn't been opened between collector and server. Also, as our collector and server are in different VLANs all connections are made through an F5. The configured VIP on the F5 allows only traffic on port 6699 (collector>server), 2021 (client>server) and 9911 (dynatrace Web).

Do we need to update our architecture and configure the F5 and the firewall to allow traffic on port 8041 as well ?

thanks


Yes, you must set the same rules on the F5