IBM Support

Meaning of 'Not able to connect after 1 tries' message in db2ClusterPing output

Question & Answer


Question

What is the meaning of the following pattern message in 'db2ClusterPing' or 'db2cluster -verify -req -rdma_ping' output.

Starting connection test number 1
host01:CMA:6e05:c571b700: 9607 us(9607 us): dapl_cma_active: non-consumer REJ, reason=8, DST 40.23.2.128, 63032
Not able to connect after 1 tries. Timeout not yet reached, Going to retry to connect after sleeping for 1 sec
Connected to Server (40.23.2.128) in 8613 microseconds after 2 attempt
100 bytes from 40.23.2.128: seq=0 time=66
100 bytes from 40.23.2.128: seq=1 time=11
100 bytes from 40.23.2.128: seq=2 time=11
100 bytes from 40.23.2.128: seq=3 time=11
100 bytes from 40.23.2.128: seq=4 time=10
100 bytes from 40.23.2.128: seq=5 time=10
100 bytes from 40.23.2.128: seq=6 time=10
100 bytes from 40.23.2.128: seq=7 time=10
100 bytes from 40.23.2.128: seq=8 time=10
100 bytes from 40.23.2.128: seq=9 time=10
round-trip average: 15 microseconds

 

Answer

"Not able to connect after 1 tries. Timeout not yet reached, Going to retry to connect after sleeping for 1 s"

The message just means that the server was not ready when the client tries to connect to it. 
As long as the client is able to connect to the server, it can be ignored.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008Pm0AAE","label":"PureScale->Cluster Management"}],"ARM Case Number":"TS003871953","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"All Version(s)"}]

Document Information

Modified date:
30 June 2020

UID

ibm16242632