When trying to access the configuration or the profiles of any Control-M Module deployed by Control-M Application Pack, the error "managed to connect but the agent dir in the response doesn't match, no point to continue" is prompted.

Knowledge Article

Article Number

000377679

Old Article Number

Article Type

Solutions to a Product Problem

Title

When trying to access the configuration or the profiles of any Control-M Module deployed by Control-M Application Pack, the error "managed to connect but the agent dir in the response doesn't match, no point to continue" is prompted.

Summary

When trying to access the configuration or the profiles of any Control-M Module deployed by Control-M Application Pack, the error "The request failed with the following information ; error message <managed to connect but the agent dir in the response doesn't match, no point to continue>" is prompted.

Product

Control-M Application Pack

Component

Control-M Application Pack

Applies to

Control-M Application Pack all supported versions.

Problem

When trying to access the configuration or the profiles of any Control-M module deployed by Control-M Application Pack, the error "The request failed with the following information ; error message <managed to connect but the agent dir in the response doesn't match, no point to continue>" is prompted.

When the issue is reproduced with Control-M/Agent's debug enabled (agdbglvl 5), the error "Check connection Failed. Got reply from AP Server on a different agent" and "Redirection" entries appear in the "APPACK_TUNNEL_XXXXX.log".

1119 18:29:45:029 APPACK_TUNNEL: [be_remoting.cpp:217] Request url: http://localhost:39580/dispatcher-919200/dispReceiver/
1119 18:29:45:029 APPACK_TUNNEL: [be_remoting.cpp:220] Sending check_connection_req: <?xml version='1.0' encoding='UTF-8'?><ECSCM><HEADER><ACTION>check_connection</ACTION></HEADER><BODY /></ECSCM>
1119 18:29:45:029 APPACK_TUNNEL: [be_remoting.cpp:743] post
1119 18:29:45:029 APPACK_TUNNEL: [be_remoting.cpp:756] curl_version_info_data version 7.44.0
1119 18:29:45:034 APPACK_TUNNEL: [be_remoting.cpp:225] Response: <HTML>
<HEAD><TITLE>Redirection</TITLE></HEAD>
<BODY><H1>Redirect</H1></BODY>

1119 18:29:45:034 APPACK_TUNNEL:Check connection Failed. Got reply from AP Server on a different agent: <HTML>
<HEAD><TITLE>Redirection</TITLE></HEAD>
<BODY><H1>Redirect</H1></BODY>

1. Verify the AP tomcat port by checking the value of the parameter "TOMCAT_PORT=" in the file {Control-M/Agent Installation Directory}/ctm/cm/AP/data/one_params.properties.

2. By running the next CURL test with the Control-M/Agent's user id, it may be possible to see the proxy configuration redirecting the Control-M Application Pack requests (substitute the values below from 39580 with the AP tomcat port from step 1, and from 919200 with your Control-M Application Pack version):

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X GET http://localhost:39580/dispatcher-919200/status/

if curl does not work, the following wget command can be used as an alternative:

wget -d --header="Accept: application/json" --header="Content-Type: application/json" http://localhost:39580/dispatcher-919200/status/

If the Agent is running on a Linux/Unix environment as root, re-run the command above after switching to the root user using the command "su - root" to verify if the proxy server is loaded with the user's environment variables.

You may see output similar to the output below from the proxy server:

HTTP/1.1 301 Moved Permanently
Server: BlueCoat-Security-Appliance
Location:http://10.248.173.128
Connection: Close

<HTML>
<HEAD><TITLE>Redirection</TITLE></HEAD>
<BODY><H1>Redirect</H1></BODY>

3. Depending on the environment, running the following command as both the Agent user, and then as the root user, may also provide information on the proxy configuration: echo $http_proxy

Cause

A proxy configuration in the Control-M/Agent's machine is redirecting the Control-M Application Pack requests.

Solution

Engage your sysadmin to disable the proxy configuration for the Control-M Application Pack requests. Once the proxy is disabled run the CURL test to validate it, you may receive an output similar to the following:

curl -i -H "Accept: application/json" -H "Content-Type: applicat ion/json" -X GET http://localhost:39580/dispatcher-919200/status/
HTTP/1.1 404
Content-Type: text/html;charset=utf-8
Content-Language: en
Content-Length: 1107
Date: Fri, 08 Jan 2021 16:57:12 GMT

<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title>< style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;backgr ound-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;colo r:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,s ans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-famil y:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Ta homa,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Taho ma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black ;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none; }</style></head><body><h1>HTTP Status 404 – Not Found</h1><hr class="line" /><p> <b>Type</b> Status Report</p><p><b>Message</b> /dispatcher-919200/status /</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><h3>Apache Tomcat/9.0.14</h3></body></html>

Once the proxy is disabled, you must be able to access the configuration and connection profiles of any Control-M Module deployed by Control-M Application Pack.

Attachment(s):