Failed transport vmdb error 45 failed to connect to peer process

Transport (VMDB) error -45: Failed to connect to peer process после обновления VMware ESXi

mr_orangeV прислал заметку о решение проблемы с VMDB transport.

После обновления ESXi до версии 6.7 сборка 17499825 и вывода хоста из режима обслуживания, виртуальные машины не мигрировали обратно на хост с ошибкой:

Поиск корневых причин привёл к нескольким вариантам:

1. Опять кто-то где-то напутал в коде, такое уже было у HPE, можно поискать по фразе » had a bug that constantly wrote logs to the /tmp/vmware-root folder that eventually filled up the partition».
2. Кончилось место, в том числе под swap.
3. Mac OS Unlocker или в работе, или криво удален.

Как найти реальную причину?

Для начала прочитать все, что написано в комьюнити и БЗ: ссылка 01 и ссылка 02 kb 50113127.

Во второй KB указано, что «Confirm the presence of the Unlocker installation on the ESXi host using one or more of the following commands».

В моём случае эти команды не показали ничего, а команды ls -l /bin/vmx в kb нет.

Подключаемся к хосту по SSH и GUI, смотрим:

• Проверяем место: df –h
• Проверяем Ramdisk: vdf –h
• Проверяем snmp по kb 2040707 и inode: stat -f /vmfs/volumes
• Проверяем что у нас с симлинками: ls -l /bin/vmx
• Читаем (можно из GUI хоста) vmkernel и vpxd логи
  Ищем строки вида «vmx: Error in initial cartel setup: Failed to open /bin/vmx: Operation not permitted»

В моем случае, это оказался неудаленный полностью Unlocker.

Шаги решения

• cd /bin
• ls -l /bin/vmx и посмотреть куда он ведет
• cd /куда ведет симлинк и
• ls посмотреть на наличие vmx и unlocker
• cd /bin
• rm vmx – удалилить симлинк
• cp /откуда)/vmx /bin

Материалы для внеклассного чтения

ESXi host becomes unresponsive when attempting a vMotion migration or a configuration change (2040707)

Powering on or migrating a virtual machine fails with error: Transport (VMDB) error -45: Failed to connect to peer process. (50113127)

Unable to power on virtual machines on ESXi host with the error: «Invalid or unsupported virtual machine configuration.»

Почитать про аналогичные случаи и как их пытались решать в комьюнити

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

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

Yet another «Failed — Transport (VMDB) error -45» issue after updating esxi host. No (ramdisk) issues

upgrade esxi from 6.0 to 6.5,VM can’t power on

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

Мораль для тех, кто дочитал

Проверяйте IPMI и SSH доступ к хосту до начала работ. В том числе, что есть KVM, а ISO монтируется. Это не всегда так для старых серверов.

Планируйте время с запасом.

Планируйте запасной вариант и план отката, на случай, если что-то пойдет не так.

Учитывайте, что откат обновления у VMware крайне интересен (и прочитайте еще раз про IPMI).

Источник

Failed transport vmdb error 45 failed to connect to peer process

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

Client build number: 6506686

ESXi version: 6.5.0

ESXi build number: 7388607

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

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.

Источник

Server on ESXi not starting. «Transport VMDB error -45»

I have a server 2012 std r2 on an ESXi host that fails to start.

State = «Failed — Transport (VMDB) error -45: Failed to connect to peer process.»

Anyone have any ideas to resolve this? This happened after server was shut down to inflate a thin provisioned disk. now it will not start.

Any ideas/help is appreciated.

Thanks in advance.

Ensure AV Gear Plays Nice on the Corporate Network

What ESXi version & edition ?

Can you do a vMotion to another host and set storage options to Thick provisioning with eager-zero ?

What ESXi version & edition ?

Can you do a vMotion to another host and set storage options to Thick provisioning with eager-zero ?

Free edition Version 6.5.0 on Dell Poweredge R630

How did you inflate ??

Any backups ? Wait free version ??

Just reinstall the VM.

his solutions was » i had to delete lots of snmp files.»

By opening the datastore browser, vmdk file, right-click -> inflate. I do have backup. Was just hoping there was something simple I was overlooking.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Snap! — LifeLock Breach, Secret AI, Reversible Aging, Brain Fog?

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 16, 1956: SAGE Is Disclosed to the Public (Read more HERE.) Bonus Flashback: January 16, 1969: Soyuz 4 & 5 Make History (Read more HERE.) You need to hear .

File Permissions

Hi All,Last week my work asked me to remove all Security groups and set access levels per user. They also have decided that the no longer want these at Folder level but would rather it was File level across the whole server.The reason for this , They say .

Spark! Pro series – 16th January 2023

It is a new week, full of endless opportunities and possibilities. Let’s make the most of it! Just a reminder, if you are reading the Spark!, Spice it up. We like it spicy here! Today in History: NASA’s.

How do you like to learn?

There is a lot of buzz and actually also controversy about learning styles and multiple intelligences in the way that we think about learning, so not taking a side here and saying that it is a magical code that will unlock our ability to do all things. T.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Источник

Failed transport vmdb error 45 failed to connect to peer process

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I have a big problem moving two VMs.

I can move all VM’s in my cluster from one host to another except two. If I want to move them with vMotion, vMotion starts, stops at 20% and after some time I get the message:

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

— VCSA 6.5 most recent build

— vSphere ESXi 6.5 (Build: 8294253)

— NetApp Storage, Datastore via NFS mounted

Anybody got a solution here?

Many thanks and greetings

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

This could be due to lack of free space in Datastore and not being able to create a swap file.

We would see following entries in hostd.log

2017-01-25T17:26:01.292Z info hostd[A0AFB70] [Originator@6876 sub=vm:/vmfs/volumes/54e639e8-d1b40fa0-d11c-40a8f0253994/SCB-DVM-8046/SCB-DVM-8046.vmx] VMX exited: ‘0 MainRun: Could not reserve memory for the Virtual Machine Process during initial power on.-22 Initial VMX memory reservation failed.

2017-01-25T17:26:27.007Z warning hostd[E781B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/54e639e8-d1b40fa0-d11c-40a8f0253994/SCB-DVM-8046/SCB-DVM-8046.vmx] Failed operation

2017-01-25T17:26:27.008Z info hostd[E781B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 28125 : Cannot power on SCB-DVM-8046 on scb-srv-esx04.internal.tls.gov.tt in ha-datacenter. A general system error occurred:

Free up space in datastore would be my suggestion

Источник

Failed transport vmdb error 45 failed to connect to peer process

Here is the relevant excerpt from the log file:

Following the replies to the threads mentioned above I checked if I was running out of disk space:

What about ramdisk? Even though there is no mention in the log file (as suggested in VMware Knowledge Base​ ) that the ramdisk is full, I still ran vdf -h to see the ramdisk:

What about running out of inodes? Per I ran

But honestly do not know if Inodes: Total: 0 Free: 0 means out of inodes. What else should I be looking for?

I di dread in another thread about just reinstalling esxi back, but that does not explain why this is happening to begin with.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Do you have only one host? If not, are you seeing the same issue on all the hosts? Did you check the vmkernel.log for any errors with the storage?

To start of with, create a new VM and attach the existing disks from the VM. Then attempt to power it on.

If it still fails, share the hostd.log, vmkernel.log and vmware.log as soon as the power on fails.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Do you have only one host? If not, are you seeing the same issue on all the hosts?

Did you check the vmkernel.log for any errors with the storage?

Yep. Nothing besides what I have mentioned already.

To start of with, create a new VM and attach the existing disks from the VM. Then attempt to power it on.

Источник

VIC: vic-machine-windows.exe version v0.7.0-7145-3fab0b0 (0.8.0 rc1)
Harbor: 0.5.0
vCenter 6.5 — 2016 RTM3 — ob-4602587
Client Machine — Windows 7 (virtual box driver)
and Linux (Photon) — just to push an image from standard docker to harbor (for no-tls)

Steps:

1. Deploy Harbor OVA (http) and configure it with LDAP
2. Push busy box image to harbor
3. Create VCH no-tls with insecure-registry :80
4. Run the busybox image — got this error during poweron the container (vm)

VCH admin portal is pulling only 500 lines of vpxd log @mdubya66 said there is an issue open for this already.

vpxd log snippet

2016-11-22T21:17:11.671Z info vpxd[7FCEA67CF700] [Originator@6876 sub=vpxLro opID=11350fbe] [VpxLRO] -- FINISH task-506
2016-11-22T21:17:11.671Z info vpxd[7FCEA67CF700] [Originator@6876 sub=Default opID=11350fbe] [VpxLRO] -- ERROR task-506 -- vm-76 -- vim.VirtualMachine.powerOn: vim.fault.GenericVmConfigFault:
--> Result:
--> (vim.fault.GenericVmConfigFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.vigor.transport.vmdb",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "-45"
-->             },
-->             (vmodl.KeyAnyValue) {
-->                key = "2",
-->                value = "Failed to connect to peer process"
-->             }
-->          ],
-->          message = "Transport (VMDB) error -45: Failed to connect to peer process."
-->       },
-->       (vmodl.LocalizableMessage) {
-->          key = "vpxd.vm.poweron.unexpectedfailure",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e4dff003e1e4d86206337922e"
-->             }
-->          ],
-->          message = "An unexpected error was received from the ESX host while powering on VM wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e4dff003e1e4d86206337922e."
-->       }
-->    ],
-->    reason = "Transport (VMDB) error -45: Failed to connect to peer process."
-->    msg = "Transport (VMDB) error -45: Failed to connect to peer process."
--> }

Hostd log snippet

2016-11-22T21:17:11.989Z info hostd[E981B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5834a33f-379a2af0-dbb1-020006c9cf7b/wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e4dff003e1e4d86206337922e/wcBusybox1-
2016-11-22T21:17:11.989Z verbose hostd[E981B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-02-4a-bf1a user=vpxuser:vpxuser] RecordOp ASSIGN: disabledMethod, 4. Sent notification immediately.
2016-11-22T21:17:11.989Z info hostd[E981B70] [Originator@6876 sub=Vimsvc.TaskManager opID=11350fbe-01-02-4a-bf1a user=vpxuser:vpxuser] Task Completed : haTask-pool2-vim.ResourcePool.moveInto-127033076 Status succ
2016-11-22T21:17:11.989Z verbose hostd[E981B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-02-4a-bf1a user=vpxuser:vpxuser] RecordOp ASSIGN: info, haTask-pool2-vim.ResourcePool.moveInto-127033076. App
2016-11-22T21:17:12.028Z info hostd[97C2B70] [Originator@6876 sub=Vimsvc.TaskManager opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Task Created : haTask-4-vim.VirtualMachine.powerOn-127033077
2016-11-22T21:17:12.028Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ADD: recentTask["haTask-4-vim.VirtualMachine.power
2016-11-22T21:17:12.028Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ADD: recentTask["haTask-4-vim.VirtualMachine.power
2016-11-22T21:17:12.028Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ASSIGN: info, haTask-4-vim.VirtualMachine.powerOn-
2016-11-22T21:17:12.031Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp REMOVE: latestPage[220], session[52a946ef-7a94-00f
2016-11-22T21:17:12.031Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ADD: latestPage[230], session[52a946ef-7a94-00fa-7
2016-11-22T21:17:12.031Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change t
2016-11-22T21:17:12.031Z info hostd[97C2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Event 230 : wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95
2016-11-22T21:17:12.031Z info hostd[97C2B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5834a33f-379a2af0-dbb1-020006c9cf7b/wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e4dff003e1e4d86206337922e/wcBusybox1-
2016-11-22T21:17:12.031Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] SIOC: SIOC is notified not to start injector
2016-11-22T21:17:12.032Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ASSIGN: disabledMethod, 4. Sent notification immed
2016-11-22T21:17:12.032Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ASSIGN: info.cancelable, haTask-4-vim.VirtualMachi
2016-11-22T21:17:12.032Z verbose hostd[97C2B70] [Originator@6876 sub=PropertyProvider opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] RecordOp ASSIGN: info.cancelable, haTask-4-vim.VirtualMachi
2016-11-22T21:17:12.034Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or
2016-11-22T21:17:12.034Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Could not expand environment variable HOME.
2016-11-22T21:17:12.034Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] DictionaryLoad: Cannot open file "~/.vmware/config": No such file or direc
2016-11-22T21:17:12.036Z verbose hostd[9781B70] [Originator@6876 sub=PropertyProvider opID=3159bf22 user=vpxuser] RecordOp ASSIGN: info, haTask--vim.event.EventHistoryCollector.readNext-127033078. Applied change
2016-11-22T21:17:12.036Z verbose hostd[9781B70] [Originator@6876 sub=PropertyProvider opID=3159bf22 user=vpxuser] RecordOp ASSIGN: info, haTask--vim.event.EventHistoryCollector.readNext-127033078. Applied change
2016-11-22T21:17:12.038Z verbose hostd[9781B70] [Originator@6876 sub=PropertyProvider opID=3159bf23 user=vpxuser] RecordOp ASSIGN: info, haTask--vim.event.EventHistoryCollector.readNext-127033079. Applied change
2016-11-22T21:17:12.038Z verbose hostd[9781B70] [Originator@6876 sub=PropertyProvider opID=3159bf23 user=vpxuser] RecordOp ASSIGN: info, haTask--vim.event.EventHistoryCollector.readNext-127033079. Applied change
2016-11-22T21:17:12.047Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Starting vmx as /bin/vmx
2016-11-22T21:17:12.047Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Starting vmx as /bin/vmx
2016-11-22T21:17:12.047Z info hostd[97C2B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: VM /vmfs/volumes/5834a33f-379a2af0-dbb1-020006c9cf7b/wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e4dff003e1e4d86206
2016-11-22T21:17:12.047Z info hostd[97C2B70] [Originator@6876 sub=vm:VigorExecVMXExCommon: Exec()'ing /bin/vmx /vmfs/volumes/5834a33f-379a2af0-dbb1-020006c9cf7b/wcBusybox1-21f6414ab91eea2f0c18e7a4fd065806b1d95e6e
2016-11-22T21:17:12.048Z info hostd[97C2B70] [Originator@6876 sub=Libs opID=11350fbe-01-99-bf20 user=vpxuser:VSPHERE.LOCALAdministrator] Vigor: VMKernel_ForkExec(/bin/vmx, detached=1): status=0 pid=69749
- /var/log/hostd.log 13346/13478 99%

• What ESXi version & edition ?

  Can you do a vMotion to another host and set storage options to Thick provisioning with eager-zero ?

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  Free edition Version 6.5.0 on Dell Poweredge R630

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• How did you inflate ??

  Any backups ? Wait free version ?? 

  Just reinstall the VM…..

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  AaronG.

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  poblano

  his solutions was »

   i had to delete lots of snmp files.»

  solution as per vmware.com Opens a new window Opens a new window

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  By opening the datastore browser, vmdk file, right-click -> inflate.  I do have backup. Was just hoping there was something simple I was overlooking.

  
  1 found this helpful
  thumb_up
  thumb_down
  

I installed VMware Workstation on Debian 8.2 with

./VMware-Workstation-Full-12.1.0-3272444.x86_64.bundle

and

vmware-modconfig --console --install-all

installation without errors.

I installed Workstation on a Windows client to manage the VMS remote.

I’m able to create and delete on the Debian machine, but not to start a VM!

I get the following error message:

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

Have anybody an idea?

thats the result /var/log/vmware/hostd.log try to power on a vm

2016-01-12T10:02:26.137+01:00 info hostd[7F58E1090700] [Originator@6876 sub=Libs] VigorTransportClientProcessError: Remote connection failure
2016-01-12T10:02:26.137+01:00 info hostd[7F58E1090700] [Originator@6876 sub=vm:/vmware/W73/W73.vmx]  VMX exited: '0 /usr/lib/vmware/bin/vmware-vmx: error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory
2016-01-12T10:02:26.137+01:00 info hostd[7F58E1090700] [Originator@6876 sub=Libs] '
2016-01-12T10:02:26.139+01:00 verbose hostd[7F58E1090700] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmware/W73/W73.vmx] Vigor client state callback 0 error Transport (VMDB) error -45: Failed to connect to peer process.
2016-01-12T10:02:26.139+01:00 verbose hostd[7F58E1090700] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmware/W73/W73.vmx] Start Vmx message: Transport (VMDB) error -45: Failed to connect to peer process.
2016-01-12T10:02:26.139+01:00 verbose hostd[7F58E07A2700] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmware/W73/W73.vmx] Power On message: Transport (VMDB) error -45: Failed to connect to peer process.
2016-01-12T10:02:26.139+01:00 warning hostd[7F58E07A2700] [Originator@6876 sub=Vmsvc.vm:/vmware/W73/W73.vmx] Failed operation
2016-01-12T10:02:26.139+01:00 info hostd[7F58E07A2700] [Originator@6876 sub=Default] StuffEvent: fullFormat resource ID = event.VmFailedToPowerOnEvent.fullFormat
2016-01-12T10:02:26.140+01:00 verbose hostd[7F58E07A2700] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.
2016-01-12T10:02:26.140+01:00 info hostd[7F58E07A2700] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 6 : Cannot power on W73 on debian82.host.local in ha-datacenter. A general system error occurred:

But the libfile exists:

10:09 debian82.host.local:~# find / | grep libXcursor.so.1
/usr/lib/vmware/lib/libXcursor.so.1
/usr/lib/vmware/lib/libXcursor.so.1/libXcursor.so.1
/usr/lib/vmware-installer/2.1.0/lib/lib/libXcursor.so.1
/usr/lib/vmware-installer/2.1.0/lib/lib/libXcursor.so.1/libXcursor.so.1

vmware-ui-5368.log from Windows Operation System

2016-01-12T13:36:28.871+01:00| vmui| W115: Transport (VMDB) error -45: Failed to connect to peer process.
2016-01-12T13:36:28.871+01:00| vmui| I125: DlgUI: Transport (VMDB) error -45: Failed to connect to peer process.
2016-01-12T13:36:28.871+01:00| vmui| I125: VMPowerVIM::OnPowerChangeFailure -- 1 : false/Transport (VMDB) error -45: Failed to connect to peer process.

That are the processes currently running at the host

13:44 root@deb82:~# ps aux | grep vm
root       297  0.0  0.0      0     0 ?        S<   09:25   0:00 [kvm-irqfd-clean]
root       547  0.0  0.0  12860  3076 ?        Ss   09:25   0:01 /usr/bin/vmware-usbarbitrator
root       811  0.0  0.0 250092   516 ?        Ssl  09:25   0:00 /usr/lib/vmware/bin/vmware-vmblock-fuse -o subtype=vmware-vmblock,default_permissions,allow_other /var/run/vmblock-fuse
root       873  0.0  0.0   6848  1584 ?        Ss   09:25   0:00 /usr/bin/vmnet-bridge -s 6 -d /var/run/vmnet-bridge-0.pid -n 0
root       954  0.0  0.0   6820   188 ?        Ss   09:25   0:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1
root       961  0.0  0.0  16980  5628 ?        Ss   09:25   0:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1
root       964  0.0  0.0   9696  2624 ?        S    09:25   0:00 /usr/bin/vmnet-natd -s 6 -m /etc/vmware/vmnet8/nat.mac -c /etc/vmware/vmnet8/nat/nat.conf
root       966  0.0  0.0   6820   192 ?        Ss   09:25   0:00 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8
root       973  0.0  0.0  16980  5624 ?        Ss   09:25   0:00 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8
root       987  0.0  0.0  20812   476 ?        Ss   09:25   0:01 /usr/sbin/vmware-authdlauncher
root      1241  0.0  0.5 1483760 88384 ?       Sl   09:25   0:13 /usr/lib/vmware/bin/vmware-hostd -a /etc/vmware/hostd/config.xml

What i tried to exclude that the problem is a remote windows session:

started xming and enabled x11 forward with ssh session. thats the way i installed,managed vms in a previously test environment. but i’m not able to start the managementtool direct from the shell with the command: vmware (it seems it need a while after a few seconds it won’t bring up the gui and fall back to shell)

MY SOLUTION for that major problem:

I installed the host operation system again with minimal requirements and with systemtools (debian jessie 8.2)
After vmware workstation installation i’m able to connect, create and START any vms.
I don’t know whats the problem was before!
Thank all for the SUPPORT