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

[saiyen2002]

Hi,

I am using ESXi 5.5, build 1281650.

I am having the problem of not being able to start any VM's without getting the following message

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

Failed to power on '/vmfs/volumes/51a6288d-06384dd1-6fd5-089e01a03cd5/test/test.vmx'.

There are currently 5 VM's. 1 of them is running and it is fine, but I am afraid to turn it off worrying it may not come back up again.

The above error happens even when i create new machines.

I have in total 3 of these ESXi installation, all running on the same build and same hardware.

Only difference that I can see right now is that int he server summary under Genreal there is no Image Profile, it is blank. My w other working servers show ESXI-T.T.0-1331820-standard. I do not know if this means anything

Any assistance will be appreciated.

Regards,

[ClintColding]

If you move the VM to another host will it power on?

[saiyen2002]

diggin deeper i found in the event log the 'the file table of the ramdisk is full'

googleing aroudn the error message showed tells me that I should free up some inodes to make sure there is space free. Not sure what i meant but i had to delete lots of snmp files.

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

this seems to have fixed my problem.

One thing I do not understand though is that before clearing up the snmp files the vdf -h showed root as 53% full. There was still space left so machines should still have started up.

Now it is 1%.

Thanks

[Souvik25]

Hello, not sure if your issue is sorted now... I had a similar problem with the vC server and PSC. They wont power on with the same error message. On digging deeper, I found an issue with storage (My vC and PSC were on an external DD drive that had maxed out causing the failure). So it might be worth to check the storage side too. Cheers

[gbispo]

I also looked at my storage space and saw that it was full. After cleaning I managed to raise the VM

[Brina777]

What worked for me .... remove vm from inventory and adding it back to inventory ... booted with no issues