Host Server1 in Servercluster is not responding...

[Jaune]

It happen two time this morning that one host in my Server Cluster lost connectivity. It occur once while We were doing a snapshot of a VM and the other time it was when we attached the VM to a local Workstation CDRom.

We are currently running ESXRanger in the same time. Could it be related to that? Host become to busy and stop responding?

Looking at the logs under var/log/vmware/vpx/vpxa.log

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Check resources every 30 secs, soft limit 76800, hard limit 128000.

Setting system limit of 1024

Set system limit to 1024

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

Authd error: 514 Error connecting to hostd-vmdb service instance.

Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)

-- BEGIN task-internal-1 -- --

-- FINISH task-internal-1 -- --

-- BEGIN task-internal-2 -- --

NFC connection accept timeout: 180000 milliseconds

NFC request timeout: 180000 milliseconds

NFC read timeout: 60000 milliseconds

NFC write timeout: 600000 milliseconds

-- FINISH task-internal-2 -- --

-- BEGIN task-internal-3 -- --

============BEGIN FAILED METHOD CALL DUMP============

Invoking on

Arg host:

Thanks

[CliveD]

UPDATE A win Sorry no fix in this comment.

I have the same errors with an ESX 3.01 server that became disconnected in VI Client 2.01

VMs on the ESX server are still running ok.

On ESX:

Fixed an issue with non synced time.

Restarted the vmware-vmkauthd service

Restarted the mgmt-vmware service

On Vi Client server:

restarted the Virtual Service Center Service

Within VI Client:

Disconnected the ESX server from the cluster.

Reconnected the ESX server....

40 minutes later and still listed as "In progress"

Any ideas?

--Updated:

Extra information.

I can ping the esxserver (forward and reverse lookup) from the virtual service center server ok.

I can connect directly to the esx server and see the running VMs using VI Client, bypassing Virtual Center.

Update#2:

On the ESX server,

I restarted the mgmt-vmware service

then I restarted the vmware-vxpa service

On the VI Client the Connect operation mentioned earlier failed after almost an hour.

I tried Connect again for the problem esx server and after 10 minutes it connected!!!

I reconfigured for HA and all is ok!