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

    XML-RPC Error and DNS lookup failed when adding new Server

    Scheduled Pinned Locked Moved
    Xen Orchestra
    2
    5
    673
    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.
    • B
      bradk
      last edited by

      I am seeing a weird problem when trying to add servers to create a new pool.

      Current version: 5.74.2

      I have a pool created and I go to "New>Server". Add the new host details/creds and click Connect. It connects fine.

      Now, I go to the pool add hosts to pool and it adds the host fine. That is all well and good.

      Now, I have another 40 hosts to add. So I go to New>Server and enter the details and click connect. And the next host connects fine.
      Then, rather than going and adding the host to the pool I continue on adding new hosts. However this is where the error occurs. As I click connect on the second host a triangle pops up and the error is: Invalid XML-RPC message

      It doesnt even think about it - it returns the error immediately.

      At this point, I have the first host that worked and a second host that failed.
      Now, I delete the hosts that failed. go to Home>Pools and select the pool. Add the host that worked to the pool and all is good. Go back to New>Server and attempt to add that host that failed again. It works!

      So, essentially, the New>Server section is only allowing me to add one server at a time, then I must add it to a pool and then go back and add a new server - rinse and repeat. I cannot add multiple hosts at once.

      syslog shows:

      Sep 8 10:41:52 xoa xo-server[39123]: XML-RPC Error: Invalid XML-RPC message (response status 503)
      Sep 8 10:41:52 xoa xo-server[39123]: DNS lookup failed

      Now.. I added a host, and then while adding the second host(to force the failure) I did a tcpdump on port 53. There was no DNS request sent out as the server failed to be added and errored with XML-RPC Error in the GUI and syslog again reported the above 2 error lines.

      I have confirmed the DNS server that is configured is responding correctly - but if its not sending out the DNS request then that point is moot.

      I have restarted xo-server, rebooted Xen Orchestra. No joy.

      Does anyone have any pointers?

      Cheers,
      Brad

      DanpD 1 Reply Last reply Reply Quote 0
      • DanpD
        Danp Vates 🪐 Pro Support Team @bradk
        last edited by

        @bradk said in XML-RPC Error and DNS lookup failed when adding new Server:

        Current version: 5.74.2

        That's really old. You should update and then retest.

        P.S. You should only be adding the pool masters to XO. How many different pools do you have?

        B 1 Reply Last reply Reply Quote 0
        • B
          bradk @Danp
          last edited by

          @Danp really old? Maybe I am not showng the correct thing..

          08/09/2022, 12:35:30: Start updating...
          08/09/2022, 12:35:31: latest channel selected
          08/09/2022, 12:35:31: All up to date

          Current version: 5.74.2

          • node: 16.14.2
          • npm: 8.12.1
          • xen-orchestra-upload-ova: 0.1.4
          • xo-cli-premium: 0.14.1
          • xo-server: 5.102.1
          • xo-server-audit-premium: 0.10.0
          • xo-server-auth-github-premium: 0.2.2
          • xo-server-auth-google-premium: 0.2.2
          • xo-server-auth-ldap-premium: 0.10.4
          • xo-server-auth-saml-premium: 0.10.0
          • xo-server-backup-reports-premium: 0.17.0
          • xo-server-load-balancer-premium: 0.7.0
          • xo-server-netbox-premium: 0.3.3
          • xo-server-netdata-premium: 0.2.0
          • xo-server-perf-alert-premium: 0.3.2
          • xo-server-sdn-controller-premium: 1.0.5
          • xo-server-telemetry: 0.5.0
          • xo-server-transport-email-premium: 0.6.0
          • xo-server-transport-icinga2-premium: 0.1.1
          • xo-server-transport-nagios-premium: 0.1.1
          • xo-server-transport-slack-premium: 0.0.0
          • xo-server-transport-xmpp-premium: 0.1.1
          • xo-server-usage-report-premium: 0.10.0
          • xo-server-web-hooks-premium: 0.3.0
          • xo-server-xoa: 0.15.0
          • xo-web-premium: 5.103.0
          • xoa-cli: 0.31.0
          • xoa-updater: 0.43.1

          I have 3 pools. They are not fully populated with hosts yet - hence why I am adding the hosts in XO and then assigning the hosts to the pool. Is there a more preferred way?

          DanpD 1 Reply Last reply Reply Quote 0
          • B
            bradk
            last edited by

            We seem to have found the issue.

            This occurs because we have a proxy configured under XOA>Updates>Proxy Settings. When we remove that proxy, everything is working as expected.

            1 Reply Last reply Reply Quote 0
            • DanpD
              Danp Vates 🪐 Pro Support Team @bradk
              last edited by

              @bradk Sorry for the confusion about the version number. 😊

              1 Reply Last reply Reply Quote 0
              • First post
                Last post