info730
Contributor
Contributor

unable to start vmware-vpxd/vpxd service for vCenter appliance 6.7

Jump to solution

Hello,

I' currently installed vCenter 6.7 whenever tried to access SSO but its giving error ::---

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00007f3838015470] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Whenever trying to start service from terminal i got this error:

root@photon-machine [ ~ ]# service-control --start vmware-vpxd

Operation not cancellable. Please wait for it to finish...

Performing start operation on service vpxd...

Error executing start on service vpxd. Details {

    "resolution": null,

    "problemId": null,

    "componentKey": null,

    "detail": [

        {

            "localized": "An error occurred while starting service 'vpxd'",

            "translatable": "An error occurred while starting service '%(0)s'",

            "id": "install.ciscommon.service.failstart",

            "args": [

                "vpxd"

            ]

        }

    ]

}

Service-control failed. Error: {

    "resolution": null,

    "problemId": null,

    "componentKey": null,

    "detail": [

        {

            "localized": "An error occurred while starting service 'vpxd'",

            "translatable": "An error occurred while starting service '%(0)s'",

            "id": "install.ciscommon.service.failstart",

            "args": [

                "vpxd"

            ]

        }

    ]

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
johncol
VMware Employee
VMware Employee

See p33 here for the DNS requirements  https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-vcenter-server-67-installation-guide.pdf

If you installed with the IP as the PNID ( Primary Network Identifier) then its deployed with that information on the Certs, registered with SSO with that IP etc

Changing that IP  will break it

See  here also VMware Knowledge Base

View solution in original post

0 Kudos
5 Replies
daphnissov
Immortal
Immortal

Based on the output you pasted, I can tell that you have not correctly deployed the vCSA appliance. So you will need to delete this appliance and re-deploy through the proper method (graphical installer) ensuring you have the prereqs completed before you begin.

0 Kudos
info730
Contributor
Contributor

@

Thanks for reply,

Previously  it was working fine and i already added one host and managed  for vCenter.

This issue faced only when i changed vCenter ip.

0 Kudos
daphnissov
Immortal
Immortal

Based on the host name, this wasn't deployed properly. If you deployed using an IP only and not a fully-qualified host name, you cannot change the IP. If you did this, then changing that IP is what broke it. You need to use a FQDN to install vCSA, not an IP.

0 Kudos
info730
Contributor
Contributor

daphnissov

Thanks daphnissov​  for your immediately response 

Any other option which i can  try to resolve this before going to deploy again .:smileyconfused:

Also can you please explain why does it depends upon FQDN.?

0 Kudos
johncol
VMware Employee
VMware Employee

See p33 here for the DNS requirements  https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-vcenter-server-67-installation-guide.pdf

If you installed with the IP as the PNID ( Primary Network Identifier) then its deployed with that information on the Certs, registered with SSO with that IP etc

Changing that IP  will break it

See  here also VMware Knowledge Base

View solution in original post

0 Kudos