1
Legacy system running CentOS 5 with VMware Server 2.02 (build-203138).
Things were working (relatively) well until recently, when a different machine hosting DNS and DCHP services crashed for unrelated reasons. After that, VMware appears unable to either start or stop, failing on "Virtual Ethernet". The various network bridges report OK (checking /var/log/messages seems to confirm this).
The only error message reported when starting the service or running vmware-config.pl is vmnetBridge: Can't connect bridge eth0 to virtual network '0'(Resource deadlock avoided). (from /var/log/messages)
My theory is that a virtual network daemon crashed during my outage, and left behind a file or PID lock somewhere, but I have no way to confirm, or where such a file might be hidden.
wilcroft
Posted 2018-03-06T23:56:27.390
Reputation: 111
What is "VMware 2.02"? "VMware" is the name of a company; it makes a number of different products (VMware Workstation, Player, Fusion, Server, vSphere/ESX, ...) – jamesdlin – 2018-03-07T02:46:26.567
Sorry, Server. (Edited post accordingly) – wilcroft – 2018-03-07T05:05:36.270