mclark
Expert
Expert

Post-4.1 upgrade error in converter health status

I upgraded my vCenter 4.0 server to vCenter 4.1. After the upgrade I am seeing an error in the vCenter Service Status. The error is with com.vmware.converter, and the error is "Unable to retrieve health data from https://xxx.xxx.xxx.xxx/converter/health.xml". I rebooted after the upgrade. Anyone else seeing this, or know where I can look to find out what is wrong?

Thanks!

0 Kudos
30 Replies
mclark
Expert
Expert

I uninstalled and reinstalled the Converter piece and the error went away. FYI.

0 Kudos
MJChmiel
Contributor
Contributor

I'm having the same issue, uninstall/reinstall did not resolve.

I'm not too concerned however because converter works just fine.

0 Kudos
dougjkamp
Contributor
Contributor

I have the same problem. I reinstalled the converter component on the vCenter server but it still shows up as an error for the converter in the service status and my conversions fail.

Anyone else managed to resolve this?

Cheers,

Doug

0 Kudos
ABoeff
Contributor
Contributor

Me also have the same problem... Smiley Sad

0 Kudos
Krede
Enthusiast
Enthusiast

Same problem here!

0 Kudos
AllanKnudsen
Contributor
Contributor

I'm also seeing this problem after upgrade to 4.1 today.

If I check the address: https://xxx.xxx.xxx.xxx/converter/health.xml

1. I'm able to reach the health.xml

2. health.xml say status is green

0 Kudos
AllanKnudsen
Contributor
Contributor

The following I found in release notes for Converter 4.2 for vCenter Server 4.1

vCenter Service Status for com.vmware.converter shows error During the vCenter Converter installation process, if you specify a short server name for vCenter Converter to register with the vCenter Server, the vCenter Service Status might display the error Unable to retrieve health data from [https://servername|https://servername/] for com.vmware.converter. Workaround: Use fully qualified domain name or IP address to register vCenter Converter with vCenter Server.

I did try uninstall converter and reinstall it with fully qualified domain name. But it seems not much has changed - message is now: Unable to retrieve health data from

During installation, where I specify the FQDN a port is also specified - I was unable to set this to 443 as it was with my vCenter 4.0 installation. I have to set this to 80 before it is accepted and installation continues.

//Allan

0 Kudos
Krede
Enthusiast
Enthusiast

Allan: I tried the exact same thing - so now I also get the error from the FQDN instead.

0 Kudos
ABoeff
Contributor
Contributor

I also tried it with the full FQDN, shortname and the IP instead.

Problem is still the same...

0 Kudos
mclark
Expert
Expert

I marked this answered too quickly. I noticed the other day that the error is back again. This is still a problem for me, also.

0 Kudos
jasonboche
Immortal
Immortal

I'm also seeing this issue with Converter. I was also seeing an error message in Guided Consolidation under the Configuration Tab for vCenter Converter Server status but that seems to have gone away now. Originally I felt the two problems were directly related. I had originally installed Guided Consolidation before installing Converter - There is a dependency there where Guided Consolidation relies on Converter. I uninstalled both components and then installed Converter first, then Guided Consolidation.

Jas






[i]Jason Boche, VCDX #34, VCPx3, vExpert[/i]

[boche.net - VMware Virtualization Evangelist|http://www.boche.net/blog/][/i]

[VMware Communities User Moderator|http://www.vmware.com/communities/content/community_terms/][/i]

[Minneapolis Area VMware User Group Leader|http://communities.vmware.com/community/vmug/us-central/minneapolis][/i]

[vCalendar|http://www.boche.net/blog/index.php/vcalendar/] Author[/i]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
0 Kudos
asutosh
Enthusiast
Enthusiast

Yes, the functionality is working fine.

Just the UI reports alert.

0 Kudos
Zero70
Contributor
Contributor

Hi we have the exact same problem. Last night I updated the vcenter server to 4.1 and this morning I noticed the error

Vcenter server version

Error in vsphere Client

Actual Health status

So based on the actual Health status being greeen, I don't believe we really have a problem but it's messing up the alarms tab because it constantly shows an error Smiley Sad

0 Kudos
Samirang
Contributor
Contributor

Same problem after a fresh install and no solution

0 Kudos
Krede
Enthusiast
Enthusiast

autoreply

0 Kudos
scerazy
Enthusiast
Enthusiast

I believe all these strange errors are down to ADAM DB

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101748...

especially in current 4.1 version of vCenter, 4.2 converter etc

No idea yet how to fix it, when it is "broken"

Seb

0 Kudos
pcerda
Virtuoso
Virtuoso

I have the same problem!!!

At least i still can use Converter without problems.

have VMware said something about this issue? I've not found anything yet.






Regards / Saludos

-


Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-


Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

Regards / Saludos - Patricio Cerda - vExpert 2011 / 2012 / 2013
0 Kudos
asutosh
Enthusiast
Enthusiast

Things are working fine for me if we have VC and Converter in different machines.

With the case of VC and Converter on the same machine, seems like some issue with ssl certs.

0 Kudos
Gallwapa
Contributor
Contributor

Had this issue and it was resolved with this kb