XenCenter 7 connection to Server Pools failed

[Mitch Vega]

I have a XenCenter 7 host that seems to have lost connection to all Server Pools, though the VMs do not seem to have gone down. The log shows the following

 

2021-11-03 16:40:12,156 ERROR XenAdmin.Network.Heartbeat [Heartbeat for 10.45.0.41] - System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---

 

No problem with reconnecting to server pools. Just curious what would have caused this and how to avoid it in the future. Does not seem to be more than an annoyance at this point. 

 

Reading up on it, it seems Xen didnt send the correct API request but I would like to know what to do to avoid this in the future. Thanks for any input. 

https://support.citrix.com/article/CTX234070

[Tobias Kreidl]

See the following article, which appears to require TLS 1.2 to avoid this condition: https://support.citrix.com/article/CTX245765

 

-=Tobias

[Boby John1709155536]

• Start by making sure you are on a supported version like 7.1CU2 or CH 8.2 with all hotfixes  ( the XAPI hotfixes can make a difference to your problem)
• Make sure you are running the latest XenCenter 8.2.3 
• If you see the problem continuously  , start by running XenCenter on a VM inside the Citrix HyperVisor ( A VM using the same Management Network ) and see if you see the problem there too.
• Run a continuous ping to the host and see if you see it dropping any time during the problem.
• Check /var/log/kern.log to see any possible status change for the NICs. 
• since you know the exact time frame , look at /var/log/xensource.log as well and see if you see anything suspicious.