I am hoping someone can help here. We have two seperate vCO servers which use the same vCenter. Both of them are having issues connecting to the same vCenter. If I try another vCenter, there is no issue. This should remove vCO from the equation and prove that something is going on with this vCenter. We have updated it vCenter 5.5 Update 2 about two weeks ago and have not had any issues until yesterday. I am wondering if this is the cause and if anyone else has seen this issue?
Even stranger is, I am able to pull a license from this same vCenter, which should use the same SOAP WS.
Connectivity to the vCenter API is confirmed and the DNS name resolves. I am able to pull down this wsdl with wget on the vCO server.
sdk/vimService.wsdl
This is logged in the vCO admin page under the vCenter.
Exception, 'java.net.ConnectException: Connection refused'
I see this in the logs on the vCO appliance configuration cataliana.out.
com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.ConnectException: Connection refused
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:224)
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:131)
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:533)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:514)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:302)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeFetch(MethodInvocationHandlerImpl.java:294)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:165)
at com.sun.proxy.$Proxy62.getContent(Unknown Source)
at com.vmware.vmo.plugin.vi4.config.VlsiHelper.getServiceInstanceContent(VlsiHelper.java:294)
at com.vmware.vmo.plugin.vi4.config.VlsiHelper.login(VlsiHelper.java:223)
at com.vmware.vmo.plugin.vi4.config.VlsiHelper.<init>(VlsiHelper.java:159)
at com.vmware.vmo.plugin.vi4.config.ConnectionTester.call(ConnectionTester.java:117)
at com.vmware.vmo.plugin.vi4.config.ConnectionTester.call(ConnectionTester.java:18)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:111)
... 16 more