Agentless Application Migration Service Last Snapshot Job Failed

0

Hello, Setting up AMS with agentless discovery and replication onprem using vCenter 7.x works fine for the initial snapshot creation and replication but subsequently fails on any further snapshot creation/updates on the VM so the virtual machine shows as "stalled" in the AMS console. Checking all requirements, and the fact that it works initially, I am unable to decipher as to why subsequent snapshots are failing and there isn't much documentation on troubleshooting this so I was curious if someone had hit this before and might have some guidance?

Environment:

  • vCenter 7.x
  • Windows 2019 VM and Ubuntu 20 VM in testing - both show "stalled" after successful initial replication
  • MGN client plugin 1.1.6

Thanks for any help!

laughmk
asked 2 years ago778 views
1 Answer
1
Accepted Answer

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.

answered 2 years ago
  • 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!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions