#XCOMU0298E Unable to allocate remote transaction program: Txpi 215: Socket send error return value = 9XCOMU0780E Txpi 308: TxpiInitSSL Failed msg = <error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol> value = 4294967295:tcp 0 0 0.0.0.0:8044 0.0.0.0:* LISTENtcp 0 0 0.0.0.0:8045 0.0.0.0:* LISTENtcp6 0 0 :::8046 :::* LISTENtcp6 0 0 :::8047 :::* LISTENComponent: XCOM Data Transport for Linux
Release: Any
Support could not recreate the problem with the same XCOM 11.6 16083 SP01 level and also using the same xcom.glb, xcom.cnf and configssl.cnf files.
It was suggested to run this openssl test:
openssl s_client -connect 127.0.0.1:8045 -showcerts -status -msg > openssl.out 2>&1
In the openssl.out file the SSL handshake showed that after the client hello, the server hello immediately failed with the same error as show in the xcom.log file:**********CONNECTED(00000003)>>> TLS 1.2 [length 0005] 16 03 01 01 25>>> TLS 1.2 Handshake [length 0125], ClientHello 01 00 01 21 03 03 66 7b 3b a0 3f 76 8e 7b 0f 13... 00 0f 00 01 01140014278428560:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794:...**********
Interestingly Support received the exact same openssl output when the xcomd is not started.
Although "netstat -an | grep 804" shows xinetd is started & listening on 8045 and the unsecure "xcomtcp -ping" for port 8044 is working, there may be some problem with the xcomd process causing the SSL handshake to fail.
After restarting xcomd the problem was resolved.