Cannot start VM, "a general system error occurred, connection refused"

Armitage318
Armitage318 used Ask the Experts™
on
Hi,
I am using ESXi 6.0.
I am not able to start any VM from vSphere client.
If I connect to specific host, I can start VM without problems.

According to this URL:

https://communities.vmware.com/thread/517731

I tried to check status of every process on my VCSA, I got this:

vcsa:/bin # service-control --status
INFO:root:Service: vmware-rhttpproxy, Action: status
Service: vmware-rhttpproxy, Action: status
2017-11-09T08:42:38.411Z   Running command: ['/sbin/service', u'vmware-rhttpproxy', 'status']
2017-11-09T08:42:38.468Z   Done running command
INFO:root:Service: vmware-cis-license, Action: status
Service: vmware-cis-license, Action: status
2017-11-09T08:42:38.469Z   Running command: ['/sbin/service', u'vmware-cis-license', 'status']
2017-11-09T08:42:38.649Z   Done running command
INFO:root:Service: vmware-psc-client, Action: status
Service: vmware-psc-client, Action: status
2017-11-09T08:42:38.650Z   Running command: ['/sbin/service', u'vmware-psc-client', 'status']
2017-11-09T08:42:38.702Z   Done running command
INFO:root:Service: vmware-sca, Action: status
Service: vmware-sca, Action: status
2017-11-09T08:42:38.702Z   Running command: ['/sbin/service', u'vmware-sca', 'status']
2017-11-09T08:42:38.880Z   Done running command
INFO:root:Service: vmware-netdumper, Action: status
Service: vmware-netdumper, Action: status
2017-11-09T08:42:38.881Z   Running command: ['/sbin/service', u'vmware-netdumper', 'status']
2017-11-09T08:42:38.951Z   Done running command
INFO:root:Service: vmware-syslog, Action: status
Service: vmware-syslog, Action: status
2017-11-09T08:42:38.952Z   Running command: ['/sbin/service', u'vmware-syslog', 'status']
2017-11-09T08:42:39.042Z   Done running command
INFO:root:Service: vmware-syslog-health, Action: status
Service: vmware-syslog-health, Action: status
2017-11-09T08:42:39.042Z   Running command: ['/sbin/service', u'vmware-syslog-health', 'status']
2017-11-09T08:42:39.229Z   Done running command
INFO:root:Service: vmware-vapi-endpoint, Action: status
Service: vmware-vapi-endpoint, Action: status
2017-11-09T08:42:39.230Z   Running command: ['/sbin/service', u'vmware-vapi-endpoint', 'status']
2017-11-09T08:42:39.331Z   Done running command
INFO:root:Service: vmware-vpostgres, Action: status
Service: vmware-vpostgres, Action: status
2017-11-09T08:42:39.331Z   Running command: ['/sbin/service', u'vmware-vpostgres', 'status']
2017-11-09T08:42:39.459Z   Done running command
INFO:root:Service: vmware-invsvc, Action: status
Service: vmware-invsvc, Action: status
2017-11-09T08:42:39.460Z   Running command: ['/sbin/service', u'vmware-invsvc', 'status']
2017-11-09T08:42:39.649Z   Done running command
INFO:root:Service: vmware-mbcs, Action: status
Service: vmware-mbcs, Action: status
2017-11-09T08:42:39.649Z   Running command: ['/sbin/service', u'vmware-mbcs', 'status']
2017-11-09T08:42:39.803Z   Done running command
INFO:root:Service: vmware-vpxd, Action: status
Service: vmware-vpxd, Action: status
2017-11-09T08:42:39.804Z   Running command: ['/sbin/service', u'vmware-vpxd', 'status']
2017-11-09T08:42:40.397Z   Done running command
INFO:root:Service: vmware-eam, Action: status
Service: vmware-eam, Action: status
2017-11-09T08:42:40.398Z   Running command: ['/sbin/service', u'vmware-eam', 'status']
2017-11-09T08:42:40.508Z   Done running command
INFO:root:Service: vmware-rbd-watchdog, Action: status
Service: vmware-rbd-watchdog, Action: status
2017-11-09T08:42:40.509Z   Running command: ['/sbin/service', u'vmware-rbd-watchdog', 'status']
2017-11-09T08:42:40.577Z   Done running command
INFO:root:Service: vmware-sps, Action: status
Service: vmware-sps, Action: status
2017-11-09T08:42:40.578Z   Running command: ['/sbin/service', u'vmware-sps', 'status']
2017-11-09T08:42:40.774Z   Done running command
INFO:root:Service: vmware-vdcs, Action: status
Service: vmware-vdcs, Action: status
2017-11-09T08:42:40.775Z   Running command: ['/sbin/service', u'vmware-vdcs', 'status']
2017-11-09T08:42:40.947Z   Done running command
INFO:root:Service: vmware-vpx-workflow, Action: status
Service: vmware-vpx-workflow, Action: status
2017-11-09T08:42:40.947Z   Running command: ['/sbin/service', u'vmware-vpx-workflow', 'status']
2017-11-09T08:42:41.024Z   Done running command
INFO:root:Service: vmware-vsan-health, Action: status
Service: vmware-vsan-health, Action: status
2017-11-09T08:42:41.024Z   Running command: ['/sbin/service', u'vmware-vsan-health', 'status']
2017-11-09T08:42:41.040Z   Done running command
INFO:root:Service: vmware-vsm, Action: status
Service: vmware-vsm, Action: status
2017-11-09T08:42:41.041Z   Running command: ['/sbin/service', u'vmware-vsm', 'status']
2017-11-09T08:42:41.148Z   Done running command
INFO:root:Service: vsphere-client, Action: status
Service: vsphere-client, Action: status
2017-11-09T08:42:41.149Z   Running command: ['/sbin/service', u'vsphere-client', 'status']
2017-11-09T08:42:41.324Z   Done running command
INFO:root:Service: vmware-perfcharts, Action: status
Service: vmware-perfcharts, Action: status
2017-11-09T08:42:41.325Z   Running command: ['/sbin/service', u'vmware-perfcharts', 'status']
2017-11-09T08:42:41.434Z   Done running command
INFO:root:Service: vmware-vws, Action: status
Service: vmware-vws, Action: status
2017-11-09T08:42:41.435Z   Running command: ['/sbin/service', u'vmware-vws', 'status']
2017-11-09T08:42:41.546Z   Done running command
INFO:root:Running:
 vmware-cis-license (VMware License Service) vmware-eam (VMware ESX Agent Manager) vmware-invsvc (VMware Inventory Service) vmware-perfcharts (VMware Performance Charts) vmware-psc-client (VMware Platform Services Controller Client) vmware-rhttpproxy (VMware HTTP Reverse Proxy) vmware-sca (VMware Service Control Agent) vmware-sps (VMware vSphere Profile-Driven Storage Service) vmware-syslog (VMware Common Logging Service) vmware-syslog-health (VMware Syslog Health Service) vmware-vapi-endpoint (VMware vAPI Endpoint) vmware-vdcs (VMware Content Library Service) vmware-vpostgres (VMware Postgres) vmware-vpxd (VMware vCenter Server) vmware-vsan-health (VMware VSAN Health Service) vmware-vsm (VMware vService Manager) vmware-vws (VMware System and Hardware Health Manager) vsphere-client ()
Running:
 vmware-cis-license (VMware License Service) vmware-eam (VMware ESX Agent Manager) vmware-invsvc (VMware Inventory Service) vmware-perfcharts (VMware Performance Charts) vmware-psc-client (VMware Platform Services Controller Client) vmware-rhttpproxy (VMware HTTP Reverse Proxy) vmware-sca (VMware Service Control Agent) vmware-sps (VMware vSphere Profile-Driven Storage Service) vmware-syslog (VMware Common Logging Service) vmware-syslog-health (VMware Syslog Health Service) vmware-vapi-endpoint (VMware vAPI Endpoint) vmware-vdcs (VMware Content Library Service) vmware-vpostgres (VMware Postgres) vmware-vpxd (VMware vCenter Server) vmware-vsan-health (VMware VSAN Health Service) vmware-vsm (VMware vService Manager) vmware-vws (VMware System and Hardware Health Manager) vsphere-client ()
INFO:root:Stopped:
 vmware-mbcs (VMware Message Bus Configuration Service) vmware-netdumper (VMware vSphere ESXi Dump Collector) vmware-rbd-watchdog (VMware vSphere Auto Deploy Waiter) vmware-vpx-workflow (VMware vCenter Workflow Manager)
Stopped:
 vmware-mbcs (VMware Message Bus Configuration Service) vmware-netdumper (VMware vSphere ESXi Dump Collector) vmware-rbd-watchdog (VMware vSphere Auto Deploy Waiter) vmware-vpx-workflow (VMware vCenter Workflow Manager)

Open in new window


According to this URL:

https://kb.vmware.com/s/article/2109887

I tried to start vmware-mbcs; service started fine, but I have same issue in vSphere client (cannot start any VM).

I tried to stop/start vmware-vpx-workflow, and I got this:

vcsa:/bin # service-control --start vmware-vpx-workflow
INFO:root:Service: vmware-vpx-workflow, Action: start
Service: vmware-vpx-workflow, Action: start
2017-11-09T08:53:48.614Z   Running command: ['/sbin/chkconfig', u'vmware-vpx-workflow']
2017-11-09T08:53:48.696Z   Done running command
2017-11-09T08:53:48.696Z   Running command: ['/sbin/service', u'vmware-vpx-workflow', 'status']
2017-11-09T08:53:48.788Z   Done running command
2017-11-09T08:53:48.788Z   Running command: ['/sbin/chkconfig', '--force', u'vmware-vpx-workflow', 'on']
2017-11-09T08:53:48.841Z   Done running command
2017-11-09T08:53:48.842Z   Running command: ['/sbin/service', u'vmware-vpx-workflow', 'start']
2017-11-09T08:54:05.887Z   Done running command
2017-11-09T08:54:05.887Z   Invoked command: ['/sbin/service', u'vmware-vpx-workflow', 'start']
2017-11-09T08:54:05.887Z   RC = 1
Stdout = VMware vCenter workflow manager is not running.
workflow port = 8088
Waiting for vpxd to initialize
Starting VMware vCenter workflow manager...
wrapper  | An encoding declaration is missing from the top of configuration file, /usr/lib/vmware-vpx/workflow/wrapper/conf/wrapper.conf, trying the system encoding.
wrapper  | An encoding declaration is missing from the top of configuration file, /etc/vmware/wrapper_common.conf, trying the system encoding.
wrapper  | An encoding declaration is missing from the top of configuration file, /etc/vmware/wrapper_linux.conf, trying the system encoding.
wrapper  | An encoding declaration is missing from the top of configuration file, /usr/lib/vmware-vpx/workflow/wrapper/conf/wrapper-classpath.conf, trying the system encoding.
wrapper  | Spawning intermediate process...
Waiting for VMware vCenter workflow manager..................
WARNING: VMware vCenter workflow manager may have failed to start.
Workflow start failed. Error code = 1

Stderr =
2017-11-09T08:54:05.888Z   {
    "resolution": null,
    "detail": [
        {
            "args": [
                "Command: ['/sbin/service', u'vmware-vpx-workflow', 'start']\nStderr: "
            ],
            "id": "install.ciscommon.command.errinvoke",
            "localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-vpx-workflow', 'start']\nStderr: '",
            "translatable": "An error occurred while invoking external command : '%(0)s'"
        }
    ],
    "componentKey": null,
    "problemId": null
}
ERROR:root:Unable to start service vmware-vpx-workflow, Exception: {
    "resolution": null,
    "detail": [
        {
            "args": [
                "vmware-vpx-workflow"
            ],
            "id": "install.ciscommon.service.failstart",
            "localized": "An error occurred while starting service 'vmware-vpx-workflow'",
            "translatable": "An error occurred while starting service '%(0)s'"
        }
    ],
    "componentKey": null,
    "problemId": null
}
Unable to start service vmware-vpx-workflow, Exception: {
    "resolution": null,
    "detail": [
        {
            "args": [
                "vmware-vpx-workflow"
            ],
            "id": "install.ciscommon.service.failstart",
            "localized": "An error occurred while starting service 'vmware-vpx-workflow'",
            "translatable": "An error occurred while starting service '%(0)s'"
        }
    ],
    "componentKey": null,
    "problemId": null
}

Open in new window


Any suggestion?
Thank you!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
Restart VCSA wait 30 minutes after restart and try again.

Author

Commented:
Hi Andrew,
did you mean: restart OS guest of VCSA vm, or restart all services (through CLI)?
Thank you
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Restart the appliance.
Hi, before restarting vcsa, I connected through web interface (port 5480) and I noticed a warning (related to insufficient log space).
So, I followed that URL:

https://kb.vmware.com/s/article/2143565

and all went fine without restart anything.
I understand that you both didn't have such further infos

thank you

Author

Commented:
solved by myself

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial