I hate VMware some days.

Inexplicably after some updates our Vcenter stopped starting. Everything and I mean everything pointed to an issue with the SSL self-signed certs VMware generates leading us to these KB's.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2036760

https://communities.vmware.com/message/2123347

Even though nothing in regard to those had changed the only thing we could find is that some WSUS patches were applied.

We even created a SR with VMware which led us through most of the same steps including removing all the vCenter software reinstalling...course all that and the same error continues.

So we completely reloaded the server thinking something like .Net or something must be messed up. After all that.... Error still continued.

So we thought....hmm only thing we didn't try is starting with a new database.... OK create a completely new database and the error stopped and we can log into VMware.... EXCELLENT - Its something in the database..

So we looked at the VPX_Parameter table and the SSL.Version was set to like SSLv3. We believe that one of our DOD STIG requirements said it should be SSLv3, so it looks like due to POODLE and other vulnerabilities that someone either Mircosoft or VMware disabled SSL3 support changed the row from SSLV3 to ALL which was the way our VDI vCenter was configured. So after all of that WOOT we can login into vCenter.......

BUT now our database is hosed due to moving domains on the rebuild or something (we needed to do that from another project) so we went ahead and just used a new database, re-added hosts, created clusters, etc.

Went home for the weekend WSUS rebooted the server Sat night and come into work on Monday and then vCenter had stopped working again..... FML

Different error which we resolved fairly quickly since its a new error. The vCenter service just kept continually crashing... we had this in the past and since we had rebuilt, reinstalled, etc we figured it was a setting in our VPXD.cfg which got lost which lead us back to the this KB

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2065630

Adding this <ThreadStackSizeKb>1024</ThreadStackSizeKb>  fixed the issue and we are all good again....


UGGGGGHH!

Comments

Popular posts from this blog

All things Organized

Finished SVS upgrades

Little Healthcare/Cash for Clunkers Humor