Skip to main content

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk




Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading.
Issue occur when the customer was performing migration activity of virtual machine.

We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.

On VCSA Shell:
service-control --status vmware-vpxd shows "stopped"
service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again

VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.

Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA.
After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.

Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.

VCSA has generated the core dump at /var/core. From core dump its identify that the issue identified with a single VM into the environment. Where the network adaptor on that VM was showing  NULL value in DB.

Thought about getting into its DB, as its embedded DB , login into vPostgres using below path.

Login to vPostgress
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres

Tried to the VM from below command.

select v.id, v.local_file_name, h.IP_ADDRESS FROM VPX_VM v, VPX_NIC n, VPX_HOST h WHERE v.id=n.entity_id and v.host_id=h.id and n.network_name=''; (get affected VM)

select * from vpx_entity where id = '<YOURID>'; (get affected VM Name)

Fix the VM and VPXD issue

Remove Network Adapter, save config, readd Network Adapter
service-control --start vmware-vpxd

Once the vpxd services started. You can login to the vCenter without any issue.


Happy Sharing..  J

Comments

  1. vCenter 6.5 windows based... same issue. Issue resolved after Update DNS entries in hosts file and reboot server.

    ReplyDelete

Post a comment

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl