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

AMD will not connect to RUM Console

ptanner
Newcomer

I installed a new license file and rebooted the AMD server (not in Production yet) and the Console can no longer connect to the AMD server. I am also seeing an error "No contact with AMD probe."

8 REPLIES 8

Tomasz_Lisowski
Advisor

You should check if rtmgate process is running on AMD. You can check that by using ndstat command. If it is running try to telnet from console machine to 443 port on AMD to check if firewall is not blocking the port.

david_alonso
Dynatrace Pro
Dynatrace Pro

Not only the rtm gate, see if the full AMD is running, can you print the output of your ndstat command, maybe is the rtm process too. Can you print your ndstat command output?

ptanner
Newcomer
[root@dpdldynamd ~]# ndstat
=== OS type
Red Hat Enterprise Linux Server release 7.2 (Maipo)


=== upgrade.bin type
upgrade-amdclassic-amdos7-x86_64-ndw-12-04-07-0025-b001.bin


=== The default Java machine
openjdk version "1.8.0_71"
OpenJDK Runtime Environment (build 1.8.0_71-b15)
OpenJDK 64-Bit Server VM (build 25.71-b15, mixed mode)


=== Installed Java packages
java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64
java-1.8.0-openjdk-headless-1.8.0.71-2.b15.el7_2.x86_64


=== Installed packages
adlexv2page-12.4.7-2.el7.x86_64
adlexpage2trans-12.4.7-3.el7.x86_64
rtmperf-12.4.7-1.el7.x86_64
tomcat-amd-12.4.7-1.el7.x86_64
cpwrdlm-4.5.0-16.2.el7.x86_64
rtmgate-12.4.7.6-1.el7.x86_64
cba-12.4.7-15.el7.x86_64
nfc-12.4.7-15.el7.x86_64
adlexrtm-ndw.12.4.7.15-1.el7.x86_64
amdstatsmerger-12.4.7-1.el7.x86_64


=== Probe type: rtm


=== RTM probe:
4517 compuwa+ S<l 1:28 /usr/adlex/rtm/bin/rtm -i 0 /usr/adlex/rtm/bin/rtm.config
=== RTM watchdog process:
1321 root S 0:00 /usr/bin/perl /usr/adlex/rtm/bin/rtm.run start
=== No RTM HS processes
=== KPA processes:
1264 root Ss 0:00 /usr/adlex/rtm/bin/kpad /usr/adlex/config/rtm.config
=== RTMGATE process:
2036 compuwa+ Sl 0:28 java -server -Ddelta.root=/usr/adlex -Djava.protocol.handler.pkgs=adlex.rtm.gate.vpn -XX:+UseAltSigs -DRTM_TYPE= -Xmx512m -Xss512k -classpath /usr/share/tomcat/bin/cpwr_bootstrap.jar:/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/usr/share/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
=== V2PAGE process:
1117 compuwa+ Ssl 0:05 /usr/adlex/rtm/bin/v2page
=== PAGE2TRANS process:
1153 compuwa+ Ss 0:00 /usr/adlex/rtm/bin/page2trans
=== CBA process:
1183 compuwa+ Ssl 0:00 /usr/adlex/cba/bin/cba
=== NFC process:
1170 compuwa+ Ssl 0:01 /usr/adlex/nfc/bin/nfc
=== AMDSTATSMERGER process:
1159 compuwa+ Ss 0:00 /usr/bin/perl /usr/adlex/rtm/bin/amdstatsmerger.pl
=== RTMPERF process:
1144 root Ss 0:00 /usr/bin/perl /usr/local/bin/perf.monitor.pl

ptanner
Newcomer

I cannot telnet on port 443 as well. The CAS and AMD servers are on the same subnet. I have verified that the AMD server has not firewall running.

david_alonso
Dynatrace Pro
Dynatrace Pro

All the process are up and running. Have you migrated this AMD? can you try to telnet the 9091? if the 9091 works, can you try to connect using this port instead of the 443 and no secure connection.

ptanner
Newcomer

Thanks for the help. It ended up being the RHEL 7 firewall which I was informed multiple times was not on. I ended up looking myself and disabled it this morning. Everything is working now.

good to hear. Sometimes it is always interesting to doublecheck the things well done! 🙂

I've seen this issue so many times..and according to my own statistics it's always due to the firewalld service. So to everyone reading this post please make sure the firewall service is disabled and then try again to set up the connection from the RUM Console.

Cheers,

Raff