Having a weird issue after moving a vCenter DB from a dedicated SQL server, back to the vCenter Server with full blown SQL installed (Don't ask why!)
The migration has gone OK, but the vCenter service refuses to start as localhost is resolving to ::1 not 127.0.0.1. This appears to be a known issue as described in this article:
We've followed that to the letter and amended the hosts file and ensure that ipv6 is not selected on the network connection. Yet still when we ping localhost it resolves to ::1!! Any ideas how to stop this so we can get the vCenter Server service to start?
The exact error message from the log file is:
2014-01-23T16:18:09.621Z [06784 error '[SSO][SsoFactory_CreateFacade]'] Unable to create SSO facade: vmodl.fault.SystemError.
2014-01-23T16:18:09.621Z [06784 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
--> backtrace rip 000000018018aa3a
--> backtrace rip 0000000180102b18
--> backtrace rip 0000000180103f3e
--> backtrace rip 000000018008d6db
--> backtrace rip 0000000001115c2c
--> backtrace rip 0000000001136512
--> backtrace rip 000007f644152821
--> backtrace rip 000007f64414c63c
--> backtrace rip 000007f64436cbeb
--> backtrace rip 000007f8328cbaa1
--> backtrace rip 000007f831211832
--> backtrace rip 000007f832c8d609
Which seems to match the description in the KB article.
Checking the network adapter for the Vcenter VM that we're working on, IP6 is not enabled, only IP4.
The hosts file has the IPv4 localhost entry, but the IPv6 entry is rem'd out.
I've done an ipconfig /flushdns, and rebooted the server, but in both cases a ping localhost still responds with ::1