VMware Cloud Community
ssvanberg
Contributor
Contributor

Error connecting using Infrastructure Client

When I'm trying to connect to one of my ESXi using Infrastructure client it fails. The Infrast.Client says "The server could not interpret the communication from the client."

I've had the same problem before, rebooted the ESXi, and then it worked again for a while. Then this comes back. Why? What is the problem? Can it be solved in any other way than rebooting the server?

The server and virtual machines seems to be running ok, it's just that I can't connect to it.

Reply
0 Kudos
6 Replies
Goodspd
Enthusiast
Enthusiast

What versions are you using ? Have you tried to update your ESXi and the VIC ?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Reply
0 Kudos
ssvanberg
Contributor
Contributor

I think I have the latest, it wasn't long ago since I run Infrastructure Update.. On the console it says v. 3,5,0 Build 130755 on the ESXi. VIC is v. 2,5,0 Build 103682.

Reply
0 Kudos
Flicka
Contributor
Contributor

When I got this error, re-starting the management agent from the console fixed it. No need to reboot the server...

I haven't found anything in the logs yet that I can pin directly to this problem. Another post suggests it might be a system memory allocation issue. I'll be watching that.

ESX 3i build 123629, VMIC v2.5.0 build 119801- server running on an IBM e325 with 8gb of memory and dual AMD Opteron chips- no VMs running at the moment. Uptime had been about 14 days when I noticed the issue.

UPDATE: the same server has now been running 166+ days. Everything is on 2 hotswap 73gb 15K drives running in RAID 1. VMs are currently Ubuntu v8.04 desktop (a dream) and Win 7 RC (flaky); more to come. I hate to take this thing down!

Message was edited by: Flicka

Reply
0 Kudos
ssvanberg
Contributor
Contributor

I know how to get to the console, but how do I restart the management agent?

Reply
0 Kudos
Dave_Mishchenko
Immortal
Immortal

At the DCUI press F2, login and then select Restart Management Networks.

You don't have to use the console for this, but the command would be /sbin/services.sh --restart

Reply
0 Kudos
Flicka
Contributor
Contributor

Dave- good point about using the CLI. Since this issue does not appear to have a fix yet (or I haven't found it), what is the safest way to restart the management agent remotely? I can think of several possibilities, but I don't understand the ESX security model well enough to pinpoint the safest. Would there, in fact, be harm in scripting a restart of the management agent on a regular basis? You do lose the management connection for a minute or two, but everything seems to come back OK.

Any thoughts?

Thanks!

Reply
0 Kudos