I saw this exception: -
ADMU0116I: Tool information is being logged in file
/opt/ibm/WebSphereProfiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to connect to
host odm.uk.ibm.com at port 8879., resulting from: [SOAPException:
faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line
"": java.util.NoSuchElementException;
targetException=java.lang.IllegalArgumentException: Error parsing
HTTP status line "": java.util.NoSuchElementException]
ADMU4123E: Ensure that the Deployment Manager is running on the specified host
and port. Also ensure that the security configuration in
ssl.client.props on the node is compatible with the Deployment
Manager.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
/opt/ibm/WebSphereProfiles/AppSrv01/logs/syncNode.log
whilst attempting to synchronise a WebSphere Application Server (WAS) node within a managed cell: -
/opt/ibm/WebSphereProfiles/AppSrv01/bin/syncNode.sh `hostname`
I knew the root cause; I'd updated the cell to enforce TLS 1.2 rather than the potentially weaker SSL_TLS.
Therefore, I knew that I'd have to "tell" the profile that hosts the node, via the ssl_client.props file, which I'd duly edited: -
vi /opt/ibm/WebSphereProfiles/AppSrv01/properties/ssl.client.props
However, I had changed it from: -
com.ibm.ssl.protocol=SSL_TLS
to: -
com.ibm.ssl.protocol=TLSv12
wherea, of course, I should've written: -
com.ibm.ssl.protocol=TLSv1.2
Once I fixed my (user) error, the syncNode.sh script ran sweet as: -
ADMU0116I: Tool information is being logged in file
/opt/ibm/WebSphereProfiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
Realm/Cell Name:
Easy when you know how ...