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

[Rapetou]

After the last power outage, some virtual machines are ok but others are generating this error message when I try to start them.

Client version: 1.23.0

Client build number: 6506686

ESXi version: 6.5.0

ESXi build number: 7388607

Any idea?

Thanks

[SureshKumarMuth]

Do you see any .lck file in the VM directory ? Try to delete the .lck file and power it on.

[Rapetou]

I tried it with 2 different VM's and I get the exact same error message

[SureshKumarMuth]

since there was power outage , the vms are not safely shutdown, may be the .lck left over would cause this.

Do you see any .lck files on the vm folder.

Launch ssh session to the host and navigate to the vm folder and check if you see .lck files.

[Rapetou]

I deleted the .lck file and the result is the same. I still get the following error message:

Failed to power on virtual machine OXE-Main. Transport (VMDB) error -45: Failed to connect to peer p...

[admin]

Could you please share vmkernel.log and vpxa.log to do further investigation .

Regards,

Randhir

[Rapetou]

Hi Randhir,

Thank you for your reply. As requested, see both log files in attachment.

Thanks

[admin]

2018-01-05T14:20:35.354Z cpu0:67600 opID=9e0865bd)Config: 706: "SIOControlFlag2" = 1, Old Value: 0, (Status: 0x0)

2018-01-05T14:20:35.370Z cpu1:70391)Vol3: 3091: Failed to get object 28 type 3 uuid 59df1973-c5175496-bcf7-f44d306b39a0 FD 250018c4 gen 1db :Not found

2018-01-05T14:20:35.371Z cpu0:70391)Vol3: 3091: Failed to get object 28 type 3 uuid 59df1973-c5175496-bcf7-f44d306b39a0 FD 250018c4 gen 1db :Not found

2018-01-05T14:20:35.371Z cpu0:70391)Vol3: 3091: Failed to get object 28 type 3 uuid 59df1973-c5175496-bcf7-f44d306b39a0 FD 250018c4 gen 1db :Not found

2018-01-05T14:20:35.371Z cpu0:70391)WARNING: Swap: 3723: Failed to create swap file '/vmfs/volumes/59df1973-c5175496-bcf7-f44d306b39a0/OXE STBY/vmx-OXE-Main-804771917-1.vswp' : Not found

2018-01-05T14:20:35.371Z cpu0:70391)MemSched: 7807: Could not initialize swap file.

2018-01-05T14:20:35.371Z cpu0:70391)MemSched: 7821: Could not set new swap scope.

Check out this vmware KB. which have multiple reason for this state of your issue. hope you get it fixed from this.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201383...

Regards,

Randhir

[Rapetou]

I finally gave up.

I transferred my VM's on an external drive and was able to run them from that drive. I then decided to export all my machines and reinstall ESXi and format the drive.

I'm re-importing back my vm's now. We'll see!