XenServer not working
I cannot get a XenServer connection working. I tried to connect to our Pool Master servers, either on port 80, 22 and 443, but nothing seems to work.
I use RDM 8.0.5.
Below the Application Log:
[27-11-2012 8:22]ERROR XenServerManager::xenServerHost was null, it may be because the session was lost by the server, attempt to reconnect (connection to IP-address on Port 80)
[27-11-2012 8:22]ERROR XenServerManager::xenServerHost was null, it may be because the session was lost by the server, attempt to reconnect (connection to IP-address on Port 443)
[27-11-2012 8:22]ERROR XenServerManager::The underlying connection was closed: An unexpected error occurred on a send. (connection to IP-address on Port 22)
On the same desktop I can connect to the Xenservers through XenCenter and Putty (SSH 22) without any problems. There is no firewall etc between my desktop and the Xenservers.
Does anyone know how to solve this problem?
Peter
All Comments (8)
Hi
What kind of authentication are you using?
Maurice
Hi Maurice,
I use root authentication.
Peter
Thanks
How do you specify your credentials, are you using a certificate or sending the password?
Maurice
I am just sending the password, like I do when connecting through SSH. We do not use certificates
I will do some testing when I'm in the office, I'll come back to you tomorrow.
Maurice
Hi
Like XenCenter, we use xml-rpc to connect to the server. Although XenCenter does not use the XenServer SDK as was have to do, I cannot see a difference on the basic connection. We do not have a server pool so havent been able to test your scenario.
Being a web based protocol, it uses either HTTP or HTTPS. It will allow us to use HTTP for ports 80 or 8080, but for the others it switches to HTTPS.
Can you confirm the settings used by XenCenter?
If you cannot see in the interface, you can go in the XenCenter logs and look for something like this:
2012-11-28 09:20:06,931 DEBUG XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - IXenConnection: trying to connect to 192.168.1.231
2012-11-28 09:20:11,849 DEBUG XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - Getting server time for pool devolutions-xen (OpaqueRef:ce177569-7a7d-732b-fff9-b00a955e4ad3)...
2012-11-28 09:20:11,926 DEBUG XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - Time offset for 192.168.1.231 is now -00:00:02.1007283. It's now 2012-11-28T14:20:11.9052721Z UTC here, and 2012-11-28T14:20:14.0060004Z UTC on the server.
2012-11-28 09:20:12,213 INFO XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - Connected to devolutions-xen (192.168.1.231:443)
2012-11-28 09:20:12,214 INFO XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - Connecting to devolutions-xen (192.168.1.231) in progress.
2012-11-28 09:20:12,214 DEBUG XenAdmin.Actions.ActionBase [Connection to 192.168.1.231] - Connecting to devolutions-xen (192.168.1.231) in progress.
2012-11-28 09:20:12,919 DEBUG XenAdmin.Network.XenConnection [Connection to 192.168.1.231] - Completed connection phase for pool devolutions-xen (OpaqueRef:ce177569-7a7d-732b-fff9-b00a955e4ad3).
2012-11-28 09:20:13,082 DEBUG XenAdmin.Network.Heartbeat [Heartbeat for 192.168.1.231] - Heartbeat thread for connection to 192.168.1.231 started
2012-11-28 09:20:13,087 INFO XenAdmin.MainWindow [1352] - Connected to devolutions-xen (version 6.0.2, build 6.0.2.53456) with XenCenter 6.0.2 (build 53158)
2012-11-28 09:20:13,207 INFO XenAdmin.Network.XenConnection [1352] - Connection to 192.168.1.231 successful.
2012-11-28 09:20:13,208 DEBUG XenAdmin.Actions.ActionBase [1352] - Connection to 192.168.1.231 successful.
edited by mcote on 11/28/2012
edited by mcote on 11/28/2012
Maurice
I had the same problem. I think port 443 is the default for XenCenter, at least on version 6.0.
What fixed it for me was the combination of making sure that the port is set to 443, and choosing "embedded" for the credentials, then putting in your root login and password credentials there. Also it took a bit longer for it to connect, but once it did, all my servers are there.
Awesome!
thank you for your input, I hope that Peter got it to work.
Maurice