1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
I have the same problem after the initial snapshot. I traced the error to this:
In the vcenter-client logs I see this error:
{
"message": "VixDiskLibVim: Failed to verify SSL certificate: actual thumbprint=**VCENTER_THUMBPRINT** expected=**THUMBPRINT_FROM_CONFIG**\n",
"log": {
"type": "Remote",
"name": "Agent",
"level": "INFO",
"level_number": 20
},
"source_code": {
"function": "Log",
"file": "com.amazonaws.cloudendure.agent.snapshotflavor.JVixLoggerImpl"
},
"runtime_thread": 24,
"origin": {
"hostname": "mymgn.local"
},
"@timestamp": "2022-08-31T18:39:18.128Z"
}
And then the snapshot transport fails, for what I see, in the vcenter-client.config file there is a thumbprint of the vCenter from the initial agent configuration, but when It fetches it again its different. I checked the thumbprint manually and I get the same as the agent when tries to transport the snapshot. So I don't know where it got the other one.
Getting the thumbprint with:
openssl s_client -connect vcenterhostname:port < /dev/null 2>/dev/null | openssl x509 -fingerprint -noout -in /dev/stdin
replace it in vcenter-client.config file, and running "vcenter_configuration_update" script seemed to work.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
Hi,
You nailed it with this response. Thank you and great find! Ironically, I have gotten nothing from AWS support, but this seems to have fixed it for me. I still see some other errors in the logs so my hope is to use the support case to identify the answer to your question above about how that thumbprint is initially obtained. I will reply back here if/when I receive that answer. Great job and thank you for sharing!
Thanks!