XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XOA unable to connect to server EHOSTUNREACH

    Scheduled Pinned Locked Moved Solved Management
    10 Posts 3 Posters 139 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kmgallo
      last edited by

      Looking for som assistance please, and I'm new to this group.

      I'm running 8.2.1 with XOA running on the same hardware as XCP-NG. First this was all working until a power outage this weekend. Hence something has not come back after that outage and I have rebooted the host / XOA VM.

      Post the reboot I'm only seeing the VM's on XEN-2 shown in the image below, XEN-1 will not connect and gives this generic error EHOSTUNREACH.

      I've tried to rebuild that connection and installed a second XOA on XEN-2 which gets the same error message. Hence I do not think the issue is with XOA so much as the XCP-NG install at this point (perhaps I should have posted this elsewhere)

      Has anyone seen this error or have a direction I can move in to recover from whatever the power hit has done? The server boots and the VM's are running. I have network access to both instances.
      94d531b9-7a83-4c38-9c34-d40296a4ee3d-image.png

      Any help much appreciated!

      DanpD 1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team @kmgallo
        last edited by

        @kmgallo From your description, it sounds like these hosts were in separate pools. Is that correct? Are you able to SSH into the host and check its status from within xsconsole?

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          kmgallo @Danp
          last edited by

          @Danp yes different pools, and yes xsconsole works fine in an ssh session

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            From your browser, does https://10.1.10.30 works?

            K 1 Reply Last reply Reply Quote 0
            • K Offline
              kmgallo @olivierlambert
              last edited by

              @olivierlambert yes we can see the page works correctly:

              2a9b96b7-40e1-4de3-ba9f-61a6efd2b10d-image.png

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Okay so the question is why it cannot work from XO. Can you wget https://10.1.10.30 from your XO VM?

                K 1 Reply Last reply Reply Quote 0
                • K Offline
                  kmgallo @olivierlambert
                  last edited by

                  @olivierlambert said in XOA unable to connect to server EHOSTUNREACH:

                  wget https://10.1.10.30

                  Interestingly I can not, I ssh'd into XO and rand the get command and here is the result:

                  xo@xo-ce:~$ wget https://10.1.10.30
                  --2025-06-03 00:49:18-- https://10.1.10.30/
                  Connecting to 10.1.10.30:443... failed: No route to host.

                  Mind you XO is running on this host.

                  I then switched to the XO I installed on the other pool today and got the same result.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    You have a networking configuration issue, check your routes in XO operating system, that explains why XO cannot connect 🙂

                    K 1 Reply Last reply Reply Quote 0
                    • K Offline
                      kmgallo @olivierlambert
                      last edited by olivierlambert

                      @olivierlambert Thanks for the help, when I run ip route I get the below:

                      xo@xo-ce:~$ ip route
                      default via 10.1.10.1 dev eth0 onlink
                      10.1.10.0/24 dev eth0 proto kernel scope link src 10.1.10.31
                      xo@xo-ce:~$

                      Note that XO is able to connect to the other pool which is on the same network (10.1.10.32)

                      While looking into this I looked at the network settings for Xen-1 Vs. Xen-2, please see below, this seems incorrect on Xen-1 as it should be showing two different IP address ranges on two different bridges yet somehow they are showing the same IP range

                      Xen-1 (one having issues):

                      [07:29 xen-1 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether ec:f4:bb:e6:63:7c brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether ec:f4:bb:e6:63:7d brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master ovs-system state DOWN group default qlen 1000
    link/ether ec:f4:bb:e6:63:78 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether ec:f4:bb:e6:63:7a brd ff:ff:ff:ff:ff:ff
6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 76:33:23:1c:bc:b6 brd ff:ff:ff:ff:ff:ff
7: xenbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ec:f4:bb:e6:63:7d brd ff:ff:ff:ff:ff:ff
8: xenbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ec:f4:bb:e6:63:78 brd ff:ff:ff:ff:ff:ff
**9: xenbr3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ec:f4:bb:e6:63:7a brd ff:ff:ff:ff:ff:ff
    inet ******10.1.10.30/24 brd 10.1.10.255****** scope global xenbr3
       valid_lft forever preferred_lft forever
10: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether ec:f4:bb:e6:63:7c brd ff:ff:ff:ff:ff:ff
    inet ******10.1.10.30/24 brd 10.1.10.255****** scope global xenbr0
       valid_lft forever preferred_lft forever**
11: vif1.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
13: vif2.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
14: vif2.1: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
17: vif3.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
19: vif4.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
21: vif5.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
23: vif6.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
25: vif7.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
27: vif8.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
29: vif9.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
30: vif9.1: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
33: vif10.1: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

                      XEN-2 (working as expected):

                      [07:31 xen-2 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 24:6e:96:38:8c:0c brd ff:ff:ff:ff:ff:ff
3: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master ovs-system state DOWN group default qlen 1000
    link/ether 24:6e:96:38:8c:0d brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 24:6e:96:38:8c:08 brd ff:ff:ff:ff:ff:ff
5: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether 24:6e:96:38:8c:0a brd ff:ff:ff:ff:ff:ff
6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 42:d3:4c:3f:f6:98 brd ff:ff:ff:ff:ff:ff
**7: xenbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 24:6e:96:38:8c:0a brd ff:ff:ff:ff:ff:ff
    inet ******10.1.10.32/24 brd 10.1.10.255****** scope global xenbr1
       valid_lft forever preferred_lft forever
8: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 24:6e:96:38:8c:08 brd ff:ff:ff:ff:ff:ff
    inet ******10.10.10.116/24 brd 10.10.10.255****** scope global dynamic xenbr0**
       valid_lft 559065sec preferred_lft 559065sec
9: xenbr3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 24:6e:96:38:8c:0d brd ff:ff:ff:ff:ff:ff
10: xenbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 24:6e:96:38:8c:0c brd ff:ff:ff:ff:ff:ff
11: vif1.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
13: vif2.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
15: vif3.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
17: vif4.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
19: vif5.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
21: vif6.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
23: vif7.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
25: vif8.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
27: vif9.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
29: vif10.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
31: vif11.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
36: vif13.0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

                      This duplication of IP's on the two bridge interfaces I think is likely the issue but I'm uncertain how to modify xenbr3 at this point as it was all setup in XO and using xsconsole only seems to allow me to configure the management interface which I've already reset.

                      K 1 Reply Last reply Reply Quote 0
                      • K Offline
                        kmgallo @kmgallo
                        last edited by

                        UPDATE, Its FIXED! I downloaded XCP-NG Center and it was able to connect to Xen-1 and I was then able to change xenbr3 to DHCP instead of the static IP that was the same as xenbr0. No idea how a power hit may have caused this but doing that allowed XO to immediately connect.

                        Much appreciate the assistance, I think it would have taken much longer to figure out if I didn't have the support!

                        1 Reply Last reply Reply Quote 1
                        • olivierlambertO olivierlambert marked this topic as a question
                        • olivierlambertO olivierlambert has marked this topic as solved
                        • First post
                          Last post