CloudSpark
Contributor
Contributor

vMotion error: "A general system error occurred: Launch failure" "Transport (VMDB) error -45: Failed to connect to peer process"

We have four ESX servers in an HA cluster, all identical hardware (HP DL360p Gen8). We are having problems with one of the servers.

When trying to vMotion TO the server, if the guest is running, we get the error: "A general system error occurred: Launch failure" "Transport (VMDB) error -45: Failed to connect to peer process"

We can successfully vMotion the guest TO the server if it is NOT running.

Once the guest is migrated to the troubled server, it then cannot be started. The same error pops up: "Transport (VMDB) error -45: Failed to connect to peer process"

Attached are the following log files:

/var/log/vpxa

/vmfs/volumes/ILAB/WSUS/vmware.log

Can someone point me in the right direction for a fix on this? Really not finding much substance on the net to fix it.

Thanks

0 Kudos
12 Replies
admin
Immortal
Immortal

Have you seen this article and is it applicable to your situation-

Transport (VMDB) error -45: Failed to connect to peer process

Regards,

Randhir

If you found my answers useful please consider marking them as Correct OR Helpful

0 Kudos
CloudSpark
Contributor
Contributor

I saw that article. I checked and I have not run out of space or inodes.

0 Kudos
daphnissov
Immortal
Immortal

What version of ESXi are you running? I had this exact same issue but years ago on either 5.1 or 5.5 and the cause was some of the agents HP puts in their customized ISO had a memory leak or some other issue. It was fixed with updated versions of that agent, but you had to reboot the host to get it to service vMotions. I looked for the HPE advisory but can't find it. It may not be the same issue at all, but the symptoms are exactly the same.

0 Kudos
TheBobkin
VMware Employee
VMware Employee

Hello CloudSpark

daphnissov, is this what you were referring to?:

https://kb.vmware.com/s/article/2085618

Is it only live migration of this one VM from one host to one particular host?

Or from ANY host to one particular host?

Or any VMs from one host to one particular host?

Or any VMs from any host to one particular host?

Have you tried removing the ISO that is loaded as a CD/DVD device? And/or is this accessible from all hosts?:

'/vmfs/volumes/2acd7416-7fc32fe8/ISO/en_windows_server_2012_r2_vl_with_update_x64_dvd_6052766.iso'

Bob

0 Kudos
daphnissov
Immortal
Immortal

That sounds very familiar...maybe it's it.

0 Kudos
CloudSpark
Contributor
Contributor

No, the version I am running is ESX6.5.

It only happens with live migrations.

0 Kudos
gbulloch
Contributor
Contributor

I have the same symptoms, also not running out of space on the hosts. Mine is a cluster and Windows based vCenter that is only used by a Horizon 7.4 environment, issue started after the last round of patches. Interesting the build number on the hosts in this environment is 6.5 7388607 and according to VUM it's fully patched and compliant with 6.5U1 ESXi upgrade but on my mixed workload environment with a vCSA, all of the hosts are on build 7526125. Exact same model of server, exact same ESXi image profile, using standard not OEM images. Not sure if related to my issues but seems odd.

Did you ever get this resolved?

I have a ticket open with support, I will post the results of that once it's sorted. My guess is I need to rebuild the hosts.

0 Kudos
MartinWest
Contributor
Contributor

Hello everybody

I have the same problem.

Anyone have a solution?

regards

Maritn

0 Kudos
gbulloch
Contributor
Contributor

Hi Martin,

I had to power off both of the hosts in the cluster that was affected by this issue to resolve it however since patching the hosts a month or so ago, I haven't had it occur again.

My hosts are currently on 6.5U1 build 8294253 which is not the latest build anymore but has been stable for me.

VMware support never came up with a root cause for this unfortunately.

0 Kudos
Shan_Virtual
Enthusiast
Enthusiast

Hi gbulloch,

Did you get any update from VMware support team.I am facing similar issue.

Regards,

Shan-virtual

vcp 3\4\5
0 Kudos
gbulloch
Contributor
Contributor

Hi Shan,

No unfortunately not but the issue has not reoccurred since I patched to those build levels so it does appear to be a bug in an older build.

0 Kudos
dokjones
Contributor
Contributor

I had the same error message and it was due to the backend storage array running out of space, so check that as well.

0 Kudos