Skip navigation

Blog Posts

Total : 3,478

Blog Posts

1 2 Previous Next



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": [



            "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": [



            "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.

Buy VMware vSphere Essentials Kit v. 6 subscription license 3-years purchase


Screen Shot 2017-01-16 at 10.20.48 AM.png

Get into the GAME at - Where signing up is easy, but earning that CloudCred will take some skill ...


Take a look at what's new Around the Cloud - and make today PRESTIGE DAY.

Challenge yourself to reach the next Prestige Level - earn the new badge icon and reset your score!


New Task 4168: VMware Community Podcast: Photon - CNA

New Task 4169: Horizon 7.1 is GA. What’s New – Part 2

New Task 4170: vSAN on a nuclear submarine?

New Task 4171: vSAN 6.5 and ESXi 6.5 with the Intel® Optane™ SSD DC P4800X

New Task 4172: White Board Presentations: Security

New Task 4173: White Board Presentations: vCenter Server

New Task 4174: White Board Presentations: PowerCLI





VMware Technology Network recently launched a successful platform upgrade from Jive 7 to Jive 8, bringing our community

new and improved features and functionality.


Take a look at some of these key new upgrades with today’s Triple-Point Tuesday tasks at


Play & win at CloudCred One of the many great VMware Communities.


Task 4164: VMTN Spotlight Search

Task 4165: VMTN Forums by Language

Task 4166: VMTN Mobile Interface

Task 4167: VMTN News Stream



3XTuesday VMTN.png


VMware Technology Network recently launched a successful platform upgrade from Jive 7 to Jive 8, bringing our community new and improved

features and functionality.


Take a look at some of these key new upgrades with today’s Triple-Point Tuesday tasks at


Play & win at CloudCredOne of the many great VMware Communities.

Task 4164: VMTN Spotlight Search

New Task 4165: VMTN Forums by Language

New Task 4166: VMTN Mobile Interface

New Task 4167: VMTN News Stream




Plus: Welcome Horizon 7.1 - now Generally Available.



Task 4070: Raising the Bar

Task 4071: Here comes… Horizon Cloud

Task 4072: The next Horizon

New Task 4160: VMware EUC TV Playlist

New Task 4161: Horizon 7.1 is GA. What’s New – Part 1

New Task 4162: VMware TV: Leadership Perspectives

New Task 4163: Transforming Security: The Principle of Least Privilege



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.



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

    • 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.


    This guide provides step-by-step instructions to configure and test VMware Identity Manager as a trusted federation Service Provider with Okta.  Okta acts as the Identity Provider.


    Triple-Points Tuesday is on now at

    Take advantage of these new tasks, today only, for Triple-Points!


    New Task 4157: New Community Warrior: Wil van Antwerpen

    New Task 4156: Join the March 16 VMware {code} Townhall

    New Task 4155: Call for Papers - Last Day

    New Task 4154: Advanced Power CLI - in under 100 min.

    New Task 4153: vRealize Log Insight - in under 90 min.



    VMware Community PodcastSAP.png

    New Task 4158: VMware Community Podcast: SAP Adapter




    Check out this excellent resource, and your chance to WIN a FREE on-demand course and exam voucher!

    *This live event occurs via WebEx, Wednesday, March 15, 2017. GMT: 9-10am


    Task 4047: Tech Wednesdays - March 15: Design considerations for VDI and RDSH-Hosted Apps

    Task 4046: Tech Wednesdays - March 15: Share the news!

    Task 4045: Tech Wednesdays Featured HOL: Introduction to Horizon 7

    Task 4044: VMware Horizon 7 Fundamentals





    And finally, dive in to the completely updated Mentoring Badge set of tasks!


    Mentoring is a critical part of building a community - vital to CloudCred and any healthy group.

    We're glad to have you as a valued CloudCred player, and encourage you to check out this important new badge.




    See you soon.

    To understand snapshot removal from multiple VMs using single vSphere CLI command

    I came across a situation where I had to quickly gather details of all ESXi host hardware details. For small environment this can be obtained via VIClient UI but if the environment is large it makes lot of sense to have some script ready to serve this purpose for you. After some hit-n-trials finally the script was ready to capture these details and the entire process of collecting around 300 host details was so fast that the output was ready and stored in a nice .csv format within minute.

    So here is the script and required pre-requisites to run it

    1. Server from where this script is run should have Powershell & PowerCLI (modules) installed on it
    2. However the script should call for VMware snapins to run itself but incase it fails to do so please add “VMware.VimAutomation.Core” snapin manually into Powershell
    3. The server from where you are running this script shall talk to vCenter server on Port 443
    4. Replace the BOLD values with desired vCenter server details & credentials


    Connect-VIServer -Server server_fqdn -User username -Password passwd

    Add-PSSnapin VMware.VimAutomation.Core -ErrorAction 'SilentlyContinue'


    $esxi = Get-VMHost | Sort Name

    $D = $esxi | Select-object @{N="HostName";E={ $_ | Get-VMHostNetwork | select -ExpandProperty Hostname}},Manufacturer,Model,ProcessorType,NumCpu,MemoryTotalGB,Version,Build

    $D | Export-Csv -Path "path_name\file_name.csv"

    With this I end this blog.... I hope it helps... .till then Happy Reading..

    With the growing infrastructure and huge amount of  components (both physical as well as virtual) accountability and availability of these components are also increasing. Every time if there is any incident and customer logs a case with vendor support team the first thing they ask for is Logs. With the increase in number of various software components it becomes even more challenging to keep track of its various logs.

    One common answer which I have been hearing from customer is that they have setup SYSLOG server. To be honest ask this question to yourself how many times have you logged into syslog server? I have seen cases where customer have configured SYSLOG server and forgot about it and one odd day when they stuck up into some issue and then start exploring their syslog server for relevant logs. So the bottom line is logs are very important for any infrastructure and maintaining logs is equally important and challenging as well.

    VMware positions itself to cater this need with its vRealize LogInsight (aka vRLI) product. This product not only stores various logs but also structures them in a nicely manner so that it makes lot of sense for the administrator to view, analyze and share it among their peer. vRLI comes in the form of Windows.msi, Linux.rpm or standalone .ova appliance. The latest release in this segment is vRLI 4.3.2, please click here for Download & Release Notes of the product. The beauty of this product is to integrate seamlessly with vSphere or vRealize Operations Manager platform to display results in interactive dashboard. Please check vRLI Install & Configure demonstration and sizing vRLI documentation to identify correct sizing for your environment.

    Customer have option to configure Extra Small, Small, Medium or Large deployment based upon EPS (Events per Second) in their environment. This is very important to size your appliance correctly considering future growth otherwise it may result into situation where administrators are spending their productive time fixing management solution issues rather than doing day-2 tasks.

    Once the solution is configured at the first login user will landup on the below shown page, let’s understand various components of vRLI available on this page


    1. This is the address pane from where vRLI IP address or FQDN is accesses. If vRLI is configured in Cluster configurations instead of individual node IP address its VIP (Virtual IP) will be accessed. Configuring a new node will be similar to deploying new vRLI vAPp into the environment, the only change will be instead of selecting ‘Start New Deployment’ customer has to select ‘Join Existing Deployment’ and rest of the process will remain the same
    2. There are two types of dashboard options available to the customer the one in above screenshot is ‘Interactive Analytics‘ where it shows holistic event information coming from various esxi hosts or vCenter server
    3. The information available on this dashboard can then be sorted in various formats. Currently it is showing as Events one can select other options available like Field Table, Event Types, Event Trends etc
    4. This is query bar where one can create custom query to search for a specific event or select from available queries to get desired results Also in the same query bar one can select how old event we want to search starting from 5 min upto desired time frame  – I will be sharing example on this portion in later part of this blog
    5. From this drop-down one can select the time frame of event where 1 bar = 10 seconds. Administrator can customize this from 1 sec to desired time frame to get their required interactive view

    Now we got familiar with the various custom options available on dashboard let’s try to search desired log using this dashboard and see how it can help us to find a particular log event.

    Let’s take an example that I want to search all ESXi events from past 48 hours where the text contain Error


    Here we have the result based upon the query we just created, imagine if I had to find similar events from SYSLOG server or from vCenter log bundle how difficult this process would have been. Also the output is presented in a nice graphical format which makes the overall findings even more easier to understand when the event has occurred. This is one of the example of creating a custom query, it all depends upon customer’s requirement and their imagination to create various queries to get desired output.

    There are 2 more options on top-right corner of the screenshot showing Snapshot & Add to Dashboard. Taking a snapshot creates an image of this result which can be used as reference at any point in time for future reference and if customer wants to run (this) custom query frequently in their environment then they have the ability to add it to dashboard using Add to Dashboard wizard so that every time the process is not repeated.

    On Interactive dashboard customer gets the ability to Create Alert from Query option which means that if they want an alert to be triggered when a specific condition is True they can do so by creating their own alert


    After selecting Create Alert from Query option below shown screen will appear where customer has to fill relevant information and every time this condition is satisfied they will be alerted on over the email.


    Another good option available on Interactive Dashboard is to export event or charts to .csv but the option which is more useful is ability to Share Query. Let’s consider above example where I have collected some logs based upon the query I wrote, now imaging if I have to share the same dashboard to my peer then this option gives me the ability to share it in the form of a URL which any admin (who has access to vRLI) can run on it’s login and get same view as I have selected. This saves lot of time while sharing information amongst peer of a desired result.


    So far we have discussed various use cases of vRLI in this post but it doesn’t stop there. Now let’s explore Dashboard option (selected below). This is the place where customer can select any type of event from all the available/configured solutions from their infrastructure. Currently I have selected VMware-vSphere suit and listed are the available set of dashboards from the collected logs based upon their event types.

    For demonstrayion purpose I have selected VMware-vSphere General-Overview event trend for custom time frame i.e. 01-Nov-2016 to 31-12-2016 clicking any of the chart will take to the further deep insights of that event


    Apart from managing logs vRLI is capable of capturing its own health which can be accessed via its Admin page and selecting System Monitor option. It shows the current resource utilization of vRLI appliance and if there are performance issues then this is the best landing page to understand what is the resource consumption of this vApp. Also from Statistic tab customer can identify EPS


    Here is the option to configure Cluster functionality for vRLI. If customer has mulitple vRLI nodes it will appear here and they can create VIP (Virtual IP) to access it. Also Cluster upgrade activities and downloading log bundle can be performed from this page


    Since vRLI is seamlessly integrated with vSphere / vROps so from this page customer can provide vSphere or vROps credentials and configure it. Using this they can leverage to store and present logs from both of these solutions directly on vRLI dashboard. For other solutions in place VMware provides various Content Packs which can be configured in vRLI to store their logs



    Under General configurations customer can provide email ID or DL of the group whom they want to be alerted incase of any event. Also they can configure retention policy where administrator will be alerted when disk usage of vRLI vApp is hitting threshold along with browser timeout value


    Time plays a very crucial role while troubleshooting any log bundle hence it becomes equally important in vRLI as well to configure correct time to the appliance. Best practice is to point vRLI to organizational NTP server but incase customers don’t have centralized NTP server they can point it to global NTP server or ESXi host time as well


    Here customer can configure their SMTP server information which vRLI will use to send email alerts. Most of the things remains default except FQDN of SMTP server


    This was an overview of this wonderful product but the best thing I would suggest is to deploy this solution in your environment and get your hands dirty with it. I’m sure administrators would love this product because it not only saves lot of productive time but also gives insights of the problem to dig-deep.

    With this I end this blog… I hope it helps.. till then Happy reading….

    Please visit my blog vrealize for more blogposts


    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 )

    1 2 Previous Next


    Looking for a blog?

    Can't find a specific blog? Try using the Blog page to browse and search blogs.