Skip navigation
2017

Error

 

vmware-vpxd: vpxd failed to initialize in time.

vpxd is already starting up. Aborting the request.

 

 

Stderr =

2017-03-27T16:19:06.131Z   {

    "resolution": null,

    "detail": [

        {

            "args": [

                "Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: "

            ],

            "id": "install.ciscommon.command.errinvoke",

            "localized": "An error occurred while invoking external command : 'Command: ['/sbin/service', u'vmware-vpxd', 'start']\nStderr: '",

            "translatable": "An error occurred while invoking external command : '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

ERROR:root:Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

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

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

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

        }

    ],

    "componentKey": null,

    "problemId": null

}

Unable to start service vmware-vpxd, Exception: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "vmware-vpxd"

            ],

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

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

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

        }

    ],

    "componentKey": null,

    "problemId": null

 

 

vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

 

Re-search here problem was in DNS server , PSC and VC were not able to ping DNS server that why got this error,

 

Originator@6876 sub=HttpConnectionPool-000001] [ConnectComplete] Connect failed to

 

DNS/AD team resolved DNS issue after that vpxd started successfully.

Once primary DNS server down , PSC lost the communication on secondary DNS.

Scenario:- 2 PSC appliances, 2 DNS server (appliances) with NLB

 

error:- The v Sphere Client could not connect to vCenter FQDN or IP Address. The server vCenter FQDN or IP Address took too long to respond. (The command has timed out as the remote server is taking too long to respond.

 

Cause:- This issue occurs if the primary DNS server is unavailable. Due to this, the default timeout & retry values used by vCenter Server Appliance to switch the secondary DNS server cause an excessive delay.

 

Resolution:-

To reduce the timeout value and allow the appliance to fail over to the next available DNS server, modify the /etc/resolv.conf file.

 

Note: If you are using a dispersed vSphere topology with one or more external PSCs, vCenter Management nodes, and Single Single On node, you must perform these steps on all appliances. If you modify the DNS settings through the VAMI or the virtual machine console, these values are lost and need to be reapplied.

Note: Take a snapshot of vCenter Appliance before proceeding.

  1. Take an SSH session to vCenter Server Appliance.
  2. Take a backup of the /etc/resolv.conf file.
  3. Open the /etc/resolv.conf file using a suitable text editor.
  4. Add these values to the end of the file:

    options timeout:1 attempts:1 rotate

    Notes:
    • The timeout value controls the time in seconds before moving on to the next DNS server.
    • The attempts value controls the number of retries before moving to the next DNS server.
    • The rotate value adds a round robin behavior.
    1. Save and close the file.
    2. Reboot the appliance.

     

    RajeevVCP4 Expert
    vExpert

    503 Service Unavailable

    Posted by RajeevVCP4 Mar 5, 2017

    After fresh installation of vcenter server 6.0 ( all components on single virtual machines) I got this error.

     

    I saw vpxd (vcenter) service was stopped I tried to restart it bu got below error.

     

     

    Solution:- I changed it delay restart and restart web client service ( that was also stopped) after 1-2 minutes vpxd started it self.

     

    Now I am able to logon through web client ( it also take 5-10 minutes for initializing )