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

[jiggamaine01]

I just upgraded my ESXi server from 5.5 to 6.5 and when i attempt to power on a VM i get the error "Failed - Transport (VMDB) error -45: Failed to connect to peer process."

Does anyone have a clue on this? My log file is attached.

[TheBobkin]

Hello jiggamaine01,

Are you using Unlocker on this? From reading other forums, many encountered the same issue after upgrading when using this application.

Others on Communities encountered this when a ramdisk was full so check this from the CLI using vdf -h  .

Bob

[jiggamaine01]

I didn't use unlocker and my ramdisk isn't full. I even tried to create a new VM, and i get the same error when trying to power it on.

[Mparayil]

Hi,

I wold like to know are you trying to power On the VM from vCenter or Host directly, for me it looks like a vCenter VPXd Related issue. please try powering on the VM from Host directly and let me know the status so we can focus on specific component. you can try disabling the DRS NOTE: if you are not using any resource Pool the we can disable and enable it back.

let me know if you are able to power On directly connection to Esxi host.

regards

Manoj VP

[Mparayil]

if you are not able to power it on from ESXi host then check if any process for this vm is still running

You can also try to resolve by reloading the virtual machine configuration on the ESXi/ESX host. To reload the virtual machine configuration, run these commands in SSH session of the host:

    vmware-vim-cmd vmsvc/getallvms  ( check if the VM process is running or not if Still running reload the vmx by the vmid on left side corner)

(Note the vmid of the virtual machine)

    vmware-vim-cmd vmsvc/reload vmid

On ESXi, substitute vim-cmd for vmware-vim-cmd.

let me know the status we will continue if the issue still exists

regards

Manoj VP

[Mparayil]

can you confirm if you are trying to power ON the Below Virtual machine "VE Community Edition"

2017-11-27T17:33:58.948Z info hostd[E081B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: VM /vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition/EVE Community Edition.vmx opID=875c71b3 user=root] in directory /vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition

2017-11-27T17:33:58.948Z info hostd[E081B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: Exec()'ing /bin/vmx /vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition/EVE Community Edition.vmx opID=875c71b3 user=root]

2017-11-27T17:33:58.962Z info hostd[E081B70] [Originator@6876 sub=Libs opID=875c71b3 user=root] Vigor: VMKernel_ForkExec(/bin/vmx, detached=1): status=0 pid=139614

2017-11-27T17:33:58.965Z info hostd[CDCAB70] [Originator@6876 sub=Libs] SOCKET 10 (47)

2017-11-27T17:33:58.965Z info hostd[CDCAB70] [Originator@6876 sub=Libs] recv detected client closed connection

2017-11-27T17:33:58.965Z info hostd[CDCAB70] [Originator@6876 sub=Libs] VigorTransportClientProcessError: Remote disconnected

2017-11-27T17:33:58.965Z info hostd[CDCAB70] [Originator@6876 sub=vm:/vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition/EVE Community Edition.vmx]  VMX did not report err via stderr

2017-11-27T17:33:58.974Z info hostd[E781B70] [Originator@6876 sub=Hostsvc] Decremented SIOC Injector Flag2

2017-11-27T17:33:59.006Z warning hostd[E781B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition/EVE Community Edition.vmx] Failed operation

2017-11-27T17:33:59.006Z verbose hostd[E781B70] [Originator@6876 sub=PropertyProvider] RecordOp REMOVE: latestPage[441], session[527e788b-4e2c-4f9c-77ab-fb6ff7d11897]522abd8c-52f3-f1b4-82ac-eb38b50a8a6a. Applied change to temp map.

2017-11-27T17:33:59.006Z verbose hostd[E781B70] [Originator@6876 sub=PropertyProvider] RecordOp ADD: latestPage[451], session[527e788b-4e2c-4f9c-77ab-fb6ff7d11897]522abd8c-52f3-f1b4-82ac-eb38b50a8a6a. Applied change to temp map.

2017-11-27T17:33:59.006Z verbose hostd[E781B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.

2017-11-27T17:33:59.006Z info hostd[E781B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 451 : Cannot power on Eve-Lab on esxilab.unity.com in ha-datacenter. A general system error occurred:

2017-11-27T17:33:59.006Z info hostd[E781B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/591243ea-e9b68d14-8b1d-6805ca4f4378/EVE Community Edition/EVE Community Edition.vmx] State Transition (VM_STATE_POWERING_ON -> VM_STATE_OFF)

2017-11-27T17:33:59.006Z verbose hostd[E781B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: disabledMethod, 1. Sent notification immediately.

2017-11-27T17:33:59.006Z info hostd[E781B70] [Originator@6876 sub=Vimsvc.TaskManager] Task Completed : haTask-1-vim.VirtualMachine.powerOn-179725858 Status error

2017-11-27T17:33:59.006Z verbose hostd[E781B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: info, haTask-1-vim.VirtualMachine.powerOn-179725858. Applied change to temp map.

[jiggamaine01]

Yes that is the virtual machine I was trying to power on.

[Mparayil]

are you trying from vCenter interface or thick Client directly from ESXi host,

[jiggamaine01]

From the Web interface. Vcenter server is a VM on the ESXi lab that i can't power on.

[TheBobkin]

Hello jiggamaine01,

Have you tested installing ESXi on some other media (e.g. Thumb-drive) and booting from this so as to rule out some failure of the upgrade?

If this works and you also can't afford to lose settings on the original installation then you could roll-back to last ESXi upgrade by booting from Altbootbank - could also just use this as first option if you don't care about the ESXi settings/config:

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

(Regarding the VM in logs - Gallente FTW :smileygrin: )

Bob

[jiggamaine01]

i fixed the issue by running the unlocker script. Took me a while to find the folder on the internet with the needed files.

[Kasper56]

Do you have to still have the link to where the unlocker scripts are that you used?  I am experiencing the same exact issue.  Thanks.

[ThatSeattleGuy]

Likely this is not the cause of your issue, but since I just spent the day fighting the exact same error, I thought I would give back to the community with my solution. Two words: swap space.

I had attached two datastores to my new VM. Neither one was anywhere near the size of the disk array it was on (in other words, there was lots of free space left in both disk arrays outside of what each datastore took up.) However, when I assigned the datastores as "disk1" and "disk2" to the VM, I told ESXi to use the entirety of both - every last byte. Apparently that's a no-no (at least under the vm default settings for where swap lives) because ESXi seems to need needs to create swap space outside the assigned disk space for the VM, but inside the datastore (something that was not obvious to me as a n00b). Result was the cryptic "Transport error -45" error, with the real error  ("cannot extend swap") buried deep in the vm logs visible only via ssh.

Why (a) the web interface to build the new vm lets you configure a machine this way, when it knows it can't be booted, and more importantly (b) why the error message you get is so ridiculously uninformative...well, talk to the vmWare guys about that. All I know is that when I made the first disk 14gb smaller than the datastore it lived on (to match the 14gb of RAM I'd assigned to the VM), everything magically started working.

Hope that helps somebody, someday. /DR/

[MST3751]

I am having the same issue how did you run that script?