VMware Cloud Community
Andrew800
Enthusiast
Enthusiast

vCenter Service Status and Hardware Status plugin errors in vSphere 5.1 - Plug-In Manager not working

When I tried to enable the VUM for vSphere 5.1 (another issue I'll address in a different thread but if anyone has information on that, by all means chime in here), I also noticed there were 2 other errors displayed in the Plug-in manager:

The following error occurred while downloading the script plugin from https://x.x.x.x:8443/cim-ui/scriptConfig.xml: The client could not send a complete request to the server.  (The underlying connection was closed: An unexpected error occurred on a send.)

The following error occurred while downloading the script plugin from https://x.x.x.x:8443/health-ui/scriptConfig.xml: The client could not send a complete request to the server.  (The underlying connection was closed: An unexpected error occurred on a send.)

I'm not even sure what this is nor how to correct this issue but this is a new install of vCenter on a Windows machine and I don't like to see errors.  Is this a firewall issue?  Something else?  Where do I start?

13 Replies
JCMorrissey
Expert
Expert

Hi,

Might be worth first checking the webservices service to see if its started (see - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103904...)

Please consider marking as "helpful", if you find this post useful. Thanks!... http://johncmorrissey.wordpress.com/
Andrew800
Enthusiast
Enthusiast

As it turns out, this had something to do with the fact that I am logged in via a VPN to the vSphere environment using the a PC where the vSphere Client is installed to access it.  I installed the vSphere Client on a machine (a VM) within the vSphere environment and was THEN able to install the VUM plug-in and enable it, and also the vCenter Service Status & vCenter Hardware Status were displayed normally as 'Enabled'.  So somehow, there is a resolution issue accross the VPN I need to look into since it still shows locally as 'Disabled'.

UPDATE:  I tried 2 different PCs connected via VPN to that network and then I changed the DNS for that remote network connection across the VPN to the DNS server address within the vSphere environment and that seemed to do the trick.  One local machine with the vSphere Client is still giving me errors about the vCenter Service Status and Hardware Status, but the VUM installed properly and is enabled... and another local PC with the vSphere Client installed seems to be fine with all three plug-ins (VUM, Service Status & Hardware Status).  Must be a local issue with that PC.

Reply
0 Kudos
NickA99
Contributor
Contributor

Let me guess, you are using a proxy or Windows XP?  VMware will tell you its an OS issue and to refer you to http://support.microsoft.com/kb/948963.

My fix was restoring the original Tomcat server config, comparing what changed, and putting it back.  I take no responsibility if this breaks something else, but it fixed my problem (which is exactly the same error you seem to be having -- missing hardware status tab / 2 errors in the plug-in).

Backup and edit this file:  C:\Program Files\VMware\Infrastructure\tomcat\conf\server.xml

Locate this line:

<Connector SSLEnabled="true" acceptCount="100" ciphers="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>

Replace it with this:

<Connector SSLEnabled="true" acceptCount="100" ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DH_RSA_WITH_AES_256_CBC_SHA, TLS_DH_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DH_RSA_WITH_AES_128_CBC_SHA, TLS_DH_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA" connectionTimeout="20000" executor="tomcatThreadPool" keystoreFile="${bio-vmssl.keyFile.name}" keystorePass="${bio-vmssl.SSL.password}" keystoreType="PKCS12" maxKeepAliveRequests="15" port="${bio-vmssl.https.port}" protocol="HTTP/1.1" redirectPort="${bio-vmssl.https.port}" scheme="https" secure="true"></Connector>

Restart the WebManagement service to take effect.

I basically restored the missing ciphers (RC4/SSL/3DES) that were present in VCenter 5.0.  It's probably less secure, but it fixes the issue.  To the VM developers who though SSO was a brilliant idea and the QA testers who made 5.1 possible... I really really hate you.

Fidiwan
Contributor
Contributor

Thanks NickA99

It happened to me after upgrading from vCenter 4.1U3 to 5.1U1. And "yes" my vSphere Client is in a Windows XP x64 Machine.

I was going to install Microsoft Knowledge Base article 948963. as VMware say

But Then I saw your post.

So if I don't misunderstand you, Microsoft KB doesn't fix anything, and it's necesary to do your hack to do the work ?

Reply
0 Kudos
NickA99
Contributor
Contributor

If you have the x64 bit version of XP then it will probably work.  But if you are running XP 32bit then that KB fix doesn't apply and the only way I was able to overcome the issue was to add the compatible ciphers back into Tomcat.

Reply
0 Kudos
SGHORVATH
Contributor
Contributor

NickA99     Thank You, Thank You, Thank You.....   I've been working on this one for a while now...  Just set up vmware cluster on a new HP C3000 - that went well, but then I put vCenter on an older DL380 Gen7 that was running Windows 2003 x64 SP2 and kept getting those stupid error messages.. and I was running locally on the server, no RDP or VPN..  As soon as I applied your fix and restarted the service -- problem solved!!!   Great job, Thanks again.

Reply
0 Kudos
ACarrasqueiro
Contributor
Contributor

NickA99,

thanks for the great tip.

Changing the server.xml file fix the problem.

I'm finishing tests in lab and will implement in production.

Reply
0 Kudos
Andrew800
Enthusiast
Enthusiast

Thanks for your input Nick.  I discovered that on my Windows 7 machine (64-bit), all the plugins did work properly but on my XP machine they still do not.  However, I went looking for that XML file on that XP PC but there is no directory inside of C:\Program Files\VMware\Infrastructure named '\tomcat'.  Just '\Virtual Infrastructure Client'.  I did a search and there is no file named 'server.xml' in the VMware folder or subfolders.  This is XP 32-bit SP3 running vSphere Client 5.1.

Reply
0 Kudos
Paul_Sprague
Contributor
Contributor

Thank you NickA99!  I just finished a vCenter 4.1 to 5.1 upgrade and this fixed my problem too.

Reply
0 Kudos
NickA99
Contributor
Contributor

This change has to be done from the Vcenter server (that path should be present on the server).  There is nothing to change on the client side.

Reply
0 Kudos
WBSHOPPEN
Contributor
Contributor

NickA99: THANK YOU!

I had an unclearable "Host IPMI System Event Log status" alarm on a Fujitsu Primergy RX200 S7.  Clearing its IPMI SEL content via the iRMC S3 (lights-out management) card did nothing, and I couldn't see a Hardware Status tab.  And using an XP VM as a thick client.  I'm also using vCSA for vCenter, so I made a backup of /usr/lib/vmware-vpx/tomcat/conf/server.xml into /root and modified the cipher line with your text.  After rebooting, HARDWARE STATUS!

Edit: just to follow up for those Googling, I eventually cleared the alert - which I knew to be bogus - by disabling the alarm trigger in the vCenter root, then re-enabling it.

Reply
0 Kudos
kgibb01
Contributor
Contributor

Thanks.

The modification to the server.xml file worked for me.

VMWare Client on Windows XP 32bit running IE 7. The hardware status plugin would not display, I was getting the following error.

vCenter Service Status

VMware, Inc.

5.1

Disabled

Displays the health status of vCenter services

The following error occured while downloading the script plugin from https://<host>:8443/health-ui/scriptConfig.xml:

The client could not send a complete request to the server.

(The underlying connection was closed: An unexpected error occurred on a send.)

Reply
0 Kudos
a_galassi
Contributor
Contributor

Hi, what kind of upgrade did you make when you experienced this issue? In-place or on a different machine? Thanks

Reply
0 Kudos