Xen Orchestra from Sources unreachable after applying XCPng Patch updates
-
@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
@john.c How do I locate that specific path? And, this instance of Orchestra has been running flawlessly for almost two years now and nothing was changed other than applying the patches for XCPng.
Where do I look to make sure that the proper path is specified?
The xo-server.service file needs to be on the VM if that’s where you have Xen Orchestra. You can find out the appropriate location by querying where you have other working daemons by using systemctl or running a find for the chosen .service unit file. It needs to be other than the Orchestra.service and xo-server.service.
A good one to try if it’s enabled and running is sshd.service!
Are you sure that there hasn’t been anything done to the XO from the sources? Also have you tried rolling a fresh install of XO From the Sources in case something went fubar (Gang Aft Agley)?
-
@john.c Yes, the xo-server.service is on the exact, same VM where Xen Orchestra is running. It's actually in the same folder: /xen-orchestra/packages/xo-server.
When I run systemctl for the sshd.service as you recommended, I get the following:
Here's what's really, really weird, however. I have a second demo system: completely separate hardware, installations, the works... this second demo system is almost identical to the demo system on which I am having the issue and this system is working just fine. When I go to the host VM for Orchestra on that server it has the same message that it can't find the xo-server.service! And yet, just to reiterate, that version of Orchestra is working just fine.
I'm almost wondering if the updated XCPng patches broke something, as the only difference between the two setups is I haven't updated the XCPng patches on the second set of hardware, yet.
-
Hi,
No, there's no reason XCP-ng patches are doing issues like this (at least I'm not aware with our customers and our own install is also patched too: no issues).
This makes me believe it's a configuration/environment issue on your end. I know it doesn't help, but at least it's XCP-ng unrelated
-
@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
@john.c Yes, the xo-server.service is on the exact, same VM where Xen Orchestra is running. It's actually in the same folder: /xen-orchestra/packages/xo-server.
When I run systemctl for the sshd.service as you recommended, I get the following:
Here's what's really, really weird, however. I have a second demo system: completely separate hardware, installations, the works... this second demo system is almost identical to the demo system on which I am having the issue and this system is working just fine. When I go to the host VM for Orchestra on that server it has the same message that it can't find the xo-server.service! And yet, just to reiterate, that version of Orchestra is working just fine.
I'm almost wondering if the updated XCPng patches broke something, as the only difference between the two setups is I haven't updated the XCPng patches on the second set of hardware, yet.
Could you try relocating it to the sshd.service path location?
Though if it requires alterations to the xo-server.service to make it find the necessary executables, make them.
Don’t forget “systemctl daemon-reload” to reload service files.
Anyway that Orchestra.service file (Orchestra) file seems a bit odd! Did you create or use this to launch Xen Orchestra, in the past as a daemon automatically?
This maybe why Xen Orchestra is running without its working xo-server.service file!
If that still causes issues it maybe worth rolling a new instance of XO From Sources, but in an environment closer to the one used by Vates to build XOA appliance.
-
@olivierlambert said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
Hi,
No, there's no reason XCP-ng patches are doing issues like this (at least I'm not aware with our customers and our own install is also patched too: no issues).
This makes me believe it's a configuration/environment issue on your end. I know it doesn't help, but at least it's XCP-ng unrelated
If he didn’t have this issue before, but does now and it worked beforehand. While you and other customers don’t have the issue as well as possibly other XO from Sources users.
Could it be something in one of those patches, that’s interacting with his configuration and environment used by his infrastructure and/or XO From Sources VM, causing his issue?
Knowing what it it’s in his environment could be helpful as it can be documented for future reference by him and/or Vates. Both to warn people with similar configurations and also incase other surprises crop up in unexpected places!
-
@john.c Yeah, I'll probably have to suck it up and build a new one. However, it should be noted that I've in no way done any kind of odd customizations to Orchestra. When I installed it way back when I followed the explicit instructions right from the https://docs.xen-orchestra.com/installation#from-the-sources site and that was it. I think the instructions were slightly different back then, but I've never done anything other than what is in the instructions... I'm not "sophisticated" enough with Linux flavors to do any kind of tinkering on my own.
It may be a while till I get a chance to do a complete rebuild... but I'll update here once I've completed!
-
This post is deleted! -
@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
@john.c Yeah, I'll probably have to suck it up and build a new one. However, it should be noted that I've in no way done any kind of odd customizations to Orchestra. When I installed it way back when I followed the explicit instructions right from the https://docs.xen-orchestra.com/installation#from-the-sources site and that was it. I think the instructions were slightly different back then, but I've never done anything other than what is in the instructions... I'm not "sophisticated" enough with Linux flavors to do any kind of tinkering on my own.
It may be a while till I get a chance to do a complete rebuild... but I'll update here once I've completed!
How about to the XCP-ng hosts or their network connections?
-
@john.c I am able to PING the VM hosting Orchestra with no issues.
-
@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
@john.c I am able to PING the VM hosting Orchestra with no issues.
How about trace routing the tcp port using tcptraceroute (Linux) or tracetcp (Windows). Can you run this on the IP Address and port used by Xen Orchestra, from both local address (same machine) and another address (remote machine)?
Can help to see if there’s an issue in the path to that IP’s TCP Port!
