[R5.0 vcenter]with eam continious restarting of esxi servers lossing connection to vcenter
Bug #1791250 reported by
aswani kumar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Invalid
|
High
|
Sandip Dey | |||
Trunk |
Invalid
|
High
|
Sandip Dey |
Bug Description
Observed this issue twice till now
With clusters deployed with eam
if we do restart or stopping of esxi servers more times
Vcenter server losing connection to datacenters and
If we try to login it displaying error message
"could not connect to one or more vCenter Server Systems:https:/
As a workaround restart the vcenter-server
tags: | added: vmware |
description: | updated |
tags: |
added: vcenter-only removed: vmware |
To post a comment you must log in.
SR raise with VMware: #18932745309
Problem:
Vcenter server hangs, unable to connect to vsphere-client.
Symptom: /10.204. 217.246: 443/sdk" and hangs.
If we try to log into vsphere-client, it displays error message
"could not connect to one or more vCenter Server Systems:https:/
Workaround:
As a workaround vcenter-server needs to be restarted.
Details:
- Vcenter server 6.5
- user connected to ESX Agent Manager and created Agency and Agent VMs
- vpxd process shows stopped
- EAM log pasted below
eam.log
=======
2018-09- 19T08:55: 57.468- 07:00 | WARN | VLSI-client- connection- monitor- 1564 | HttpConfigurati onCompilerBase. java | 81 | Interrupted, no more connection pool cleanups will be performed.^M 19T08:56: 07.473- 07:00 | INFO | vim-monitor | VcConnection.java | 198 | Connecting to vCenter as com.vmware.vim.eam extension^M 19T08:56: 07.489- 07:00 | INFO | vim-monitor | VcConnection.java | 637 | Connecting to https:/ /bng-vc65. englab. juniper. net:8089/ sdk/vimService via vCenter proxy http:// localhost: 80^M 19T08:56: 09.501- 07:00 | ERROR | vim-monitor | VcConnection.java | 650 | Error communicating with the vCenter server.^M vim.vmomi. client. common. UnexpectedStatu sCodeException: Unexpected status code: 503^M vim.vmomi. client. common. Response$ Status. getStatus( Response. java:58) ^M vim.vmomi. client. http.impl. HttpExchangeBas e.parseResponse (HttpExchangeBa se.java: 150)^M vim.vmomi. client. http.impl. HttpExchange. run(HttpExchang e.java: 48)^M vim.vmomi. client. http.impl. HttpProtocolBin dingBase. executeRunnable (HttpProtocolBi ndingBase. java:226) ^M vim.vmomi. client. http.impl. HttpProtocolBin dingImpl. send(HttpProtoc olBindingImpl. java:110) ^M
2018-09-
2018-09-
2018-09-
com.vmware.
at com.vmware.
at com.vmware.
at com.vmware.
at com.vmware.
at com.vmware.
2018-09- 19T08:56: 09.502- 07:00 | WARN | vim-monitor | HttpConfigurati onCompilerBase. java | 89 | Shutting down the connection monitor.^M 19T08:56: 09.502- 07:00 | WARN | vim-monitor | VcListener.java | 110 | Trying to recover from error^M vim.vmomi. client. common. UnexpectedStatu sCodeException: Unexpected status code: 503^M vim.vmomi. client. common. Response$ Status. getStatus( Response. java:58) ^M vim.vmomi. client. http.impl. HttpExchangeBas e.parseResponse (HttpExchangeBa se.java: 150)^M vim.vmomi. client. http.impl. HttpExchange. run(HttpExchang e.java: 48)^M vim.vmomi. client. http.impl. HttpProtocolBin dingBase. executeRunnable (HttpProtocolBi ndingBase. java:226) ^M
2018-09-
com.vmware.
at com.vmware.
at com.vmware.
at com.vmware.
at com.vmware.