XCOM transfer/ping error "XCOMU1317E Local discover request failed."

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC

Issue/Introduction

New High Availability environment POC under Amazon Linux EC2 using a standard XCOM for Linux 12.0 installation and a network filesystem for a load balancer to handle the XCOM failover. 

XCOM file transfer or ping is failing with:
XCOMU1317E Local discover request failed

Version:
=== CA XCOM Data Transport Trace r12.0 23114 SP00 64bit (for <no SNA support>)

Cause

Trace files show "invalid EyeCatcher" "(grep: warning: s)" and "( warning: stray )" messages that XCOM did not recognise as expected data i.e.

Unsecure:
*****
 lu62.c 9570: Txpi  701: Received remote data block at 0X7FFD367008E0 starting with invalid EyeCatcher 0X67726570 (grep: warning: s)
 fsmachin.c 5255: Xrcvwt rc = -9, changing to state ERROR_LOCAL_DISCOVER_REQUEST.
 fsmachin.c 3731: Statistics is set successfully.
 fsmachin.c 3743: SNA Confirm Deallocate State(4), XCOM xcbp->state = 1317 -- XCOMU1317E Local discover request failed.
*****

Secure:
*****
E - catoossl.c(5177): TcpReceiveSSL: SSL_ERROR_SSL ret = -1 ret2 = 336130315 SSL_error_buf <error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number>
REASON <wrong version number>.
E - catotxpi.c(1751): Unable to receive header
 lu62.c 9568: Error 304 reason 0x1 Processing Xrcvwt/TxpiReceive.
 lu62.c 9570: Txpi  304: SSL Socket receive error return value = 1
 fsmachin.c 5255: Xrcvwt rc = -9, changing to state ERROR_LOCAL_DISCOVER_REQUEST.
 fsmachin.c 3731: Statistics is set successfully.
 fsmachin.c 3743: SNA Confirm Deallocate State(4), XCOM xcbp->state = 1317 -- XCOMU1317E Local discover request failed.
...
E - txpiutil.c(351): Error 701
E - txpiutil.c(351): Txpi  701: Received remote data block at 0X7FFD01777360 starting with invalid EyeCatcher 0X20776172 ( warning: stray )
E - catotxpi.c(1772): Error converting stream buffer header.
E - catotxpi.c(2259): Receive failed. Aborting receive of TXPI_HDR_TERM
E - catotxpi.c(2301): TxpiTerm: pfTermSSL.
E - catoossl.c(5303): TcpTermSSL pConnection->ssl=1f58b40.
E - catoossl.c(5361): Error 306
E - txpierr.c(179): Not setting dwReturnCode; old value: 701
E - catoossl.c(5361): Txpi  306: SSL Socket term error return value = 1
E - catoossl.c(5363): TcpReceiveSSL: SSL_ERROR_SSL ret = -1 ret2 = 336462231 SSL_error_buf <error:140E0197:SSL routines:SSL_shutdown:shutdown while in init>
 REASON <shutdown while in init>.
*****

Resolution

It is possible that there is some environmental issue on the remote partner system caused by install/upgrade of any other third party application which is issuing these messages on every new process creation and is dumping these messages into socket buffers. As XCOM doesn't understand these messages, it is closing the socket connection.
Google search indicates several packages such as rkhunter (Rootkit Hunter) may cause this problem due to issues with specific versions of grep. 
Check with the admin of the remote system to investigate these strange messages and their origin.