This morning our VMware VirtualCenter Server
Service stopped unexpectedly. My
colleague restarted the vCenter server, confirmed that all related services had
successfully restarted and was then able to log back into vCenter. (Thanks Mark!)
I took a look at the vpxd logs and noticed there
were several entries regarding SSO.
(For
Windows Server 2008, the vpxd logs are located in the following directory: C:\ProgramData\VMware\VMware
VirtualCenter\Logs)
2013-11-14T10:25:45.273-07:00 [00496 error
'HttpConnectionPool-000001'] [ConnectComplete] Connect failed to <cs
p:000000000b633090, TCP:vcentersvr.mydomain.com:7444>; cnx: (null), error:
class Vmacore::SystemException(No connection could be made because the target
machine actively refused it. )
2013-11-14T10:26:21.446-07:00 [01076 error
'[SSO][SsoCertificateManagerImpl]'] [CreateAdminSsoServiceContent] Failure
while trying to connect to SSO Admin server: No connection could be made
because the target machine actively refused it.
. Will retry in 10 seconds.
2013-11-14T10:27:21.673-07:00 [01076 warning
'[SSO][SsoCertificateManagerImpl]'] [CreateAdminSsoServiceContent] Max
connection attempts (10) reached. Giving up ...
2013-11-14T10:27:21.673-07:00 [01076 error
'Default'] Failed to intialize VMware VirtualCenter. Shutting down...
This issue is caused by a realtime virus scan
putting a lock on files used by SSO.
To resolve this issue, exclude the scanning of the
SSO folder:
X:\Program Files\VMware\Infrastructure\SSOServer
No comments:
Post a Comment