Problem parsing the AFM that is coming from Application Server

Document ID : KB000041047
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

autoping -m {servername} returns failed status from the application server.

autosys@bo-atsysa-p01>$ autoping -m ALL 
CAUAJM_I_50023 AutoPinging Machine [XXXXXXXXXXX] 
CAUAJM_I_50280 AutoPing from the Scheduler WAS SUCCESSFUL. 
CAUAJM_E_10229 Communication attempt with the CA WAAE Agent has failed! [XXXXXXXXX:7520] 
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL. 

CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.
CAUAJM_I_50023 AutoPinging Machine [XXXXXXXXXXXXX] 
CAUAJM_I_50280 AutoPing from the Scheduler WAS SUCCESSFUL.
CAUAJM_E_10229 Communication attempt with the CA WAAE Agent has failed! [XXXXXXXXX:7520] 
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL. 
CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL. 

 

Environment: 

WA AE 11.3.6 SP3 

 

Cause:

The agent is having a problem parsing the AFM coming in from the Application Server during the autoping. Here is the resulting error in the receiver.log in agent.

02/24/2016 16:43:07.139 EST-0500 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverSession.accept[:300] - Invalid data received 
--------------------- 
00000000 |32 30 31 36 30 32 32 34 20 31 36 34 33 30 37 31| |20160224 1643071| 
00000010 |32 2B 30 35 30 30 20 57 41 5F 41 47 45 4E 54 20| |2+0500 WA_AGENT | 
00000020 |41 43 45 5F 41 50 50 5F 62 6F 2D 61 74 73 79 73| |XXXXXXXXXXXXXXX| 
00000030 |61 2D 70 30 31 2C 72 77 61 2D 61 74 73 79 73 61| |XXXXXXXXXXXXXX| 
00000040 |2D 70 30 31 20 38 5F 31 33 32 33 38 33 34 36 5F| |-p01 8_13238346_| 
00000050 |31 5F 31 34 35 36 33 35 30 31 38 36 5F 35 30 35| |1_1456350186_505| 
00000060 |36 32 39 5F 43 4D 2F 57 41 41 45 5F 57 46 30 2E| |629_CM/WAAE_WF0.| 
00000070 |31 2F 4D 41 49 4E 20 43 4F 4E 54 52 4F 4C 20 4D| |1/MAIN CONTROL M| 
00000080 |47 52 41 44 44 52 20 50 6F 72 74 28 37 35 30 30| |GRADDR Port(7500| 
00000090 |29 20 41 64 64 72 65 73 73 28 62 6F 2D 61 74 73| |) Address(bo-ats| 
000000A0 |79 73 61 2D 70 30 31 2E 64 63 2E 66 6D 63 6E 61| |ysa-p01.dc.fmcna| 
000000B0 |2E 63 6F 6D 29 20 53 6F 63 6B 65 74 46 61 63 74| |.com) SocketFact| 
000000C0 |6F 72 79 49 64 28 70 6C 61 69 6E 29 20 55 73 65| |oryId(plain) Use| 
000000D0 |72 28 41 43 45 5F 41 50 50 5F 62 6F 2D 61 74 73| |r(XXXXXXXXXX| 
000000E0 |79 73 61 2D 70 30 31 2C 72 77 61 2D 61 74 73 79| |XXXXXXXXXXX| 
000000F0 |73 61 2D 70 30 31 29 | |sa-p01) | 

 

This issue occurs when the AutoServerId has two host strings as below in the config.<instance name> of primary, secondary and TB.

On the primary :


AutoServerId=<INSTANCE>_APP_<local_machine_name>, <INSTANCE>_APP_<local_machine_name>

One the shadow :


AutoServerId=<INSTANCE>_APP_<local_machine_name>, <INSTANCE>_APP_<local_machine_name>

The same on the TB.

 

Resolution:  

The installer does this when both app servers are specified during the installation interview. We have reported this to development. This entry should only contain the local machine name prefixed by ‘<INSTANCE>_APP_’, or ‘ACE_APP_’ . All you need to do is modify both config files and set the entries like this :

On the primary:
AutoServerId=<INSTANCE>_APP_<local_machine_name>


On the shadow:
AutoServerId=<INSTANCE>_APP_<local_machine_name>

 

On the TB:

AutoServerId=<INSTANCE>_APP_<local_machine_name>