Hi
We have recently deployed vCloud Director 5.5.0 (build 1323688) and attached our vCenter Server Appliance 5.5.0.5101 (build 1398493) to it. We are using self-signed certificates for both vCloud director certificates, following the procedures described in the vCloud Director Installation and Upgrade Guide.
Every few days our vCloud director loses the connection to the vCenter server. As a consequence we need to manually reconnect the vCenter server. We see the following error in vcloud-container-debug.log:
| 2013-12-14 04:07:12,474 | DEBUG | | 7e06867c-1d10-4e63-9826-27a10d840ddfListener (240) | AbstractVlsiServiceBehavior | | VCenterVimVlsiServiceBehaviorImpl@133cf92e https://<vcenter server hostname>:443/sdk/vimService PropertyCollector:propertyCollector PropertyCollector.waitForUpdatesEx: completionStatus=false | |
| 2013-12-14 04:07:12,475 | ERROR | | 7e06867c-1d10-4e63-9826-27a10d840ddfListener (240) | VcUpdateListenerImpl | | Break on Unrecoverable error in Outer WFU Loop | |
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
| at sun.security.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source) | |
| at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) | |
| at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572) | |
| at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:692) | |
| at org.apache.http.conn.scheme.SchemeSocketFactoryAdaptor.connectSocket(SchemeSocketFactoryAdaptor.java:65) | |
| at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) | |
| at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151) | |
| at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125) | |
| at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:641) | |
| at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:480) | |
| at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) | |
| at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) | |
| at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:111) | |
| at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:98) | |
| at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:526) | |
| at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:507) | |
| at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:295) | |
| at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:265) | |
| at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:169) | |
| at com.sun.proxy.$Proxy1097.waitForUpdatesEx(Unknown Source) | |
| at com.vmware.vcloud.vimproxy.internal.impl.Vc41UpdateListener.getUpdatesFromVC(Vc41UpdateListener.java:112) | |
| at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.getUpdates(VcUpdateListenerImpl.java:1155) | |
| at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.innerWaitForUpdatesLoop(VcUpdateListenerImpl.java:906) | |
| at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.outerWaitForUpdatesLoop(VcUpdateListenerImpl.java:600) | |
| at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.run(VcUpdateListenerImpl.java:349) |
The line "javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated" is indicating some problem with the SSL certificates. However, I'm unable to find out what exactly might be the problem.
In vCloud director I have _not_ checked the checkbox to verify SSL certificates (Administration => General).
Things I have tried so far:
* Re-created new SSL certificates, replacing the old ones in the keystore
* Re-configured vcloud director using /opt/vmware/vcloud-director/bin/configure -r
* Detached vCenter server from vCloud director and attached it again
So far to no avail.
Has anyone experienced that problem too? Any suggestions for a workaround or is this a known issue?
Any help is appreciated!
cheers,
- Fabian