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

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)