A general controller error occurred. Connection refused while powering on virtual machine

Recently I had an issue where I was trying to power on a VM from vCenter but unable to power on.

While powering on getting below error.

“A general controller error occurred. Connection refused.”

VCenter server which Im running is 6.0 and on appliance (VCSA).

Steps I follow to resolve the issue:

While investigation I found it’s a issue of Workflow manager service which was causing VM to start from vCenter. However, I was able to power on the VM from ESXi, which shows that the issue is not with VM or ESXi . It’s the issue with the services of workflow, which are not allowing VM to poweron from vCenter.

I tried below steps to verify the status of the VMware vCenter Workflow Manger service from VCSA.

1) Login to VCSA via Putty.

2) shell.set --enabled True

3) service-control --status vmware-vpx-workflow

Status of the services was showing stoped, So, I tried to start the service by using command.

service-control --start vmware-vpx-workflow.

I was getting error while starting the workflow services.

Now I tried to verify the disks space of VCSA by using df –vdf. Where I found that the space is about to 100% at /storage/logs disk. Removed the unwanted data from this location and make some space to breath.

Later I again try to start the vmware workflow services and its started successfully and by that VM from vCenter was able to poweron without any issue.

Happy Sharing.... :)

Comments

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

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. :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e

Virtualvmx

Search This Blog