Warranty Void if....

Our VMware vSphere 5.1 server died over the weekend. Basically the vmware-vpxd service wouldn't initialize. This prompted a call to VMware support. VMware support was on the phone with us for two days, at which point they issued the dreaded Prima Nocte of support. "Oh Sorry, it seems you are not running a supported config, we can not go any further with this case, do you agree with this statement?"

We aren't running a supported config? Ouch. The VMware tech pointed us to an article outlining the maximum hosts and guests for the embedded database on vSphere 5.1. Unfortunately for us, we are slightly over the allowed limits for 5.1.












vSphere is very central to what we do, so we went down the road of restoring backups. Unfortunately that avenue ended in the same place. That darn vmware-vpxd service just would not initialize. Time to start digging.

 Let see what this Linux box is doing now that it is booted.


That doesn't seem normal. Let me guess, some long running query is stopping the vmware-vpxd service from starting.























Connect to the database and see if there are any queries running.





Sorry for the line wrap, but as expected there is a long running query.












Wow 357324 rows on a recursive query, that could explain our issue.










Before everyone freaks out about me nuking the table contents, I did a bit of research. There is actually a vSphere 5.5 article instructing users to delete the contents in certain scenarios. We are also quite desperate at this point. Time for a reboot.

Back in business! Time to upgrade to vSphere 5.5.

Comments

Popular posts from this blog

Cisco VRF-Lite Guest Network and OpenDNS

Work Folders, Folder Redirection, Symbolic Links, Oh My!

Ansible: Good Things Come to Those Who Wait