Secure Domain Connector - SDC SdmEtpkiEndpoint::send() socket invalid.

book

Article ID: 185795

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

We migrated one of our SDC servers from win2008 to win2016 on a new system. I have installed the SDC and am using the exact same config files on the servers (SDC and SDM). The new server, for some reason, is unable to connect to the DSS - or vice versa.  The ports are open and I can see a listening status on port 6844 but nothing established.

The error is:

Thu Mar 05 09:34:37 2020 : ERROR: SdmEtpkiEndpoint::send() socket invalid. Endpoint IP: 192.168.166.22:6844
Thu Mar 05 09:34:56 2020 : WARNING:  Could not connect to 192.168.166.22:6844
Thu Mar 05 09:34:56 2020 : WARNING:  Socket error: 0
Thu Mar 05 09:34:56 2020 : ERROR: SdmEtpkiEndpoint::send() socket invalid. Endpoint IP: 192.168.166.22:6844
Thu Mar 05 09:34:56 2020 : WARNING: SdmSDManager::intialize() completed
Thu Mar 05 09:35:18 2020 : WARNING:  Could not connect to 192.168.166.22:6844
Thu Mar 05 09:35:18 2020 : WARNING:  Socket error: 0
Thu Mar 05 09:35:44 2020 : WARNING:  Could not connect to 192.168.166.22:6844
Thu Mar 05 09:35:44 2020 : WARNING:  Socket error: 0

 

Similar error messages:

Tue Dec 22 22:24:49 2020: INFO: SdmSDManager::sendEchos() starting secdomAddr=192.168.22.24, uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043
Tue Dec 22 22:24:49 2020: INFO: SdmMgrIcmpMultiReqHandler::sendAndWait() starting uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043
Tue Dec 22 22:24:49 2020: DEBUG:  sendEchos sendAndWait() API send error code=2, retCode=1, uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043
Tue Dec 22 22:24:49 2020: INFO: SdmMgrIcmpMultiReqHandler::sendAndWait() ending retCode=1, uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043
Tue Dec 22 22:24:49 2020: WARNING:  sendEchos error. SecDomIP=192.168.22.24, uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043, code=1
Tue Dec 22 22:24:49 2020: INFO: SdmSDManager::sendEchos() ending retCode=1, uid=5fe27231-63be-1cb3-009c-008010ef0000-10802043

Cause

Firewall

Environment

Release : 20.2.x

Component : SPCAPP - Spectrum Applications

Resolution

Verify that Windows Firewall and/or Firewalld (IPTables) on linux are disabled.  When enabled, they block the connection.  Also verify that port 6844 is open on the firewall(s) between the SS and the SDC.  If all of that seemingly checks out, try reversing the connection.  If you have -accept in the SDM.config change it to -remoteconnect  and the same in sdc.config (if it was -remoteconnect change it to -accept).  On the SS you'll need to import the sdm.config again. On the SDC cycle the SDMConnector process.

Occasionally a SpectroSERVER restart can also clear this up.