Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot Access The Standby Server At This Time. (CM 6.3)

Status
Not open for further replies.

Richard_Harrow

Technical User
Aug 31, 2023
26
0
1
AE
So everything is up and okay, but for some reason, I'm getting the above error.

When collecting logs, I noticed something very peculiar regarding the duplication link IP of one of the CMs:

20240308:003709061:30528583:filesyncd(5590):HIGH:[ERROR: ssl_read: SSL_read fail ed: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify f ailed]
20240308:003709061:30528584:filesyncd(5590):HIGH:[ERROR: start_tlv: SSL negotiat ions must have failed.]
20240308:003709061:30528585:filesyncd(5590):HIGH:[ERROR: failed to start initial TLV exchanges]
20240308:003709061:30528586:filesyncd(5590):HIGH:[ERROR: client_mgr-2: filesync api failed for host 192.11.13.14]
20240308:013108060:30530071:filesyncd(5590):HIGH:[ERROR: ssl_read: SSL_read fail ed: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify f ailed]
20240308:013108060:30530072:filesyncd(5590):HIGH:[ERROR: start_tlv: SSL negotiat ions must have failed.]
20240308:013108060:30530073:filesyncd(5590):HIGH:[ERROR: failed to start initial TLV exchanges]
20240308:013108060:30530074:filesyncd(5590):HIGH:[ERROR: client_mgr-2: filesync api failed for host 192.11.13.14]
20240308:020501732:30530948:filesyncd(5590):HIGH:[ERROR: ssl_read: SSL_read fail ed: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify f ailed]
20240308:020501732:30530949:filesyncd(5590):HIGH:[ERROR: start_tlv: SSL negotiat ions must have failed.]
20240308:020501732:30530950:filesyncd(5590):HIGH:[ERROR: failed to start initial TLV exchanges]
20240308:020501732:30530951:filesyncd(5590):HIGH:[ERROR: client_mgr-2: filesync api failed for host 192.11.13.14]
20240308:020501753:30530952:filesyncd(5590):HIGH:[ERROR: ssl_read: SSL_read fail ed: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify f ailed]
20240308:020501753:30530953:filesyncd(5590):HIGH:[ERROR: start_tlv: SSL negotiat ions must have failed.]
20240308:020501753:30530954:filesyncd(5590):HIGH:[ERROR: failed to start initial TLV exchanges]
20240308:020501753:30530955:filesyncd(5590):HIGH:[ERROR: client_mgr-2: filesync api failed for host 192.11.13.14]


It keeps saying the filesyncing is failing and is saying the SSL negotiations have failed. I think the issue is somehow linked to SSL handshaking, but when checking the certs on both CMs, they're not going to be expiring anytime soon. Any idea how I can resolve this?
 
Have you verified both the active and standby CM? Also, check the CA that created is trusted by both.
You might see more looking at the file sync logs in /var/log/ecs or in the GUI.
 
As Arlo555 says, make sure the same root CA is loaded on each CM in the duplex. Note that after you load the cert, CM must be restarted.

We're all ignorant, just in different subjects.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top