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

    Servers: connection failed, Invalid XML-RPC message / Error with plaintext password

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    17 Posts 4 Posters 3.3k Views 4 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.
    • D Offline
      dtree
      last edited by olivierlambert

      I am a newbie with XCP-ng and Orchestra. I installed Orchestra seemingly ok, but on the web page, Orchestra's Settings->Servers shows the red error triangle with exclamation point. The mouse over says Connection failed. Click for more information. When I click it says Invalid XML-RPC message.

      8d5c2507-5530-4421-9651-ae05fe176dfa-image.png

      QUESTIONS:

      1. What do I do to fix this error?

      2. Note that my PLAINTEXT password is actually reported in the error log (below). Is this a security issue that should be addressed?

      ERROR LOG

      server.enable
      {
        "id": "a488939a-4e6b-43e4-8b44-ad900022ce5e"
      }
      {
        "call": {
          "method": "session.login_with_password",
          "params": [
            "root",
            "<my plaintext password>"
          ]
        },
        "message": "Invalid XML-RPC message",
        "name": "Error",
        "stack": "Error: Invalid XML-RPC message
          at Deserializer.onDone (/usr/local/lib/node_modules/xo-server/node_modules/xmlrpc/lib/deserializer.js:79:21)
          at SAXStream.apply (events.js:310:20)
          at SAXStream.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/src/configure.js:94:17)
          at SAXParser.SAXStream._parser.onend (/usr/local/lib/node_modules/xo-server/node_modules/sax/lib/sax.js:190:10)
          at emit (/usr/local/lib/node_modules/xo-server/node_modules/sax/lib/sax.js:624:35)
          at end (/usr/local/lib/node_modules/xo-server/node_modules/sax/lib/sax.js:667:5)
          at SAXParser.end (/usr/local/lib/node_modules/xo-server/node_modules/sax/lib/sax.js:154:24)
          at SAXStream.end (/usr/local/lib/node_modules/xo-server/node_modules/sax/lib/sax.js:248:18)
          at IncomingMessage.onend (_stream_readable.js:660:10)
          at Object.onceWrapper (events.js:416:28)
          at IncomingMessage.apply (events.js:322:22)
          at IncomingMessage.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/src/configure.js:94:17)
          at endReadableNT (_stream_readable.js:1187:12)
          at processTicksAndRejections (internal/process/task_queues.js:84:21)"
      }
      
      1 Reply Last reply Reply Quote 0
      • E Offline
        ebaker8571 @AtaxyaNetwork
        last edited by

        @AtaxyaNetwork

        Sorry, user error. I wasn't clicking and selecting the SR that was created for the ISO

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates πŸͺ Co-Founder CEO
          last edited by olivierlambert

          Are you sure you are entering the IP address of the pool master? This error means you aren't connecting to a XCP-nh host

          edit: regarding question 2, I think it's already fixed on latest channel

          1 Reply Last reply Reply Quote 0
          • D Offline
            dtree
            last edited by

            I'm kind of confused.

            I have XCP-ng installed on box with IP address 192.168.107.4. I thought the fact that the Xen Orchestra web site appears at all confirms that the 192.168.107.4 is responding and serving the web page so it means that the IP address is correct, right?

            I'm not sure how Servers differs from the Orchestra IP, or if it should. I think the XOA is installed on dom0 (or dom1??) of the box and I'm assuming the Servers should be talking to the XCP-ng dom0, right? But in any case, there's only one physical box, so the IP is 192.168.107.4. I'm not sure how I could have it wrong.

            I disconnected the Ethernet cable from the box and confirmed that it stopped pinging so I assume there is nothing else at that address.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates πŸͺ Co-Founder CEO
              last edited by

              No, XOA is running in a dedicated VM, so you need to have 2 different IPs: one for the host, one for XOA.

              D E 2 Replies Last reply Reply Quote 0
              • D Offline
                dtree @olivierlambert
                last edited by

                @olivierlambert
                Sorry, so how do I put them on different IP addresses? I had thought they were both using 192.168.107.4.

                If I try to ssh to 192.168.107.4, it says ssh_exchange_identification: read: Connection reset by peer.

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates πŸͺ Co-Founder CEO
                  last edited by olivierlambert

                  That's because you have an IP conflict. Just change the IP address of one of the two.

                  You can have any different addresses on the same host for your VMs, it's using a bridge.

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    dtree
                    last edited by

                    Thanks! That worked (changing the IP address of the XOA from the host). I was not aware that they were separate IP addresses. I'm still not sure how to change the XOA IP address, but that's ok.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Offline
                      olivierlambert Vates πŸͺ Co-Founder CEO
                      last edited by

                      By reading the documentation πŸ˜‰ https://xen-orchestra.com/docs/xoa.html#network-configuration

                      1 Reply Last reply Reply Quote 0
                      • DanpD Danp referenced this topic on
                      • E Offline
                        ebaker8571 @olivierlambert
                        last edited by

                        @olivierlambert

                        When you stated one for the host and one for the xoa... I presume you mean 1 for the physical machine and 1 for the xoa appliance install?

                        I have done this and am getting this same error rpc error.

                        I created machine .69, used the CLI to create the XOA appliance on .70 and logged in to xoa to add the server. when I use .70 it says it connects then gets the rpc error. if I attempt to use a different IP, it fails to connect.

                        olivierlambertO 1 Reply Last reply Reply Quote 0
                        • olivierlambertO Offline
                          olivierlambert Vates πŸͺ Co-Founder CEO @ebaker8571
                          last edited by olivierlambert

                          @ebaker8571 said in Servers: connection failed, Invalid XML-RPC message / Error with plaintext password:

                          @olivierlambert

                          When you stated one for the host and one for the xoa... I presume you mean 1 for the physical machine and 1 for the xoa appliance install?

                          That's a bit tricky in Xen world. What you call "the physical machine" (ie the host) is in fact already a VM. But yes, one for the Dom0 and one for XOA.

                          I have done this and am getting this same error rpc error.

                          I created machine .69, used the CLI to create the XOA appliance on .70 and logged in to xoa to add the server. when I use .70 it says it connects then gets the rpc error. if I attempt to use a different IP, it fails to connect.

                          Are you sure your Dom0 is the right IP? XOA must connect to the host/Dom0 IP address. If you visit this address with your browser, what do you see?

                          E 2 Replies Last reply Reply Quote 0
                          • E Offline
                            ebaker8571 @olivierlambert
                            last edited by

                            @olivierlambert

                            i get the screen that says connect server

                            Screenshot 2024-02-29 132708.png

                            1 Reply Last reply Reply Quote 0
                            • E Offline
                              ebaker8571 @olivierlambert
                              last edited by

                              @olivierlambert

                              I created the host on .69

                              i SSH in to .69 and used the CLI to create the xoa on .70

                              I log in to .70 and get the above screen shot that says add server.

                              I attempted to add the .70 server and get the RPC error

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Offline
                                olivierlambert Vates πŸͺ Co-Founder CEO
                                last edited by

                                The server to connect is 69 not 70.

                                E 2 Replies Last reply Reply Quote 0
                                • E Offline
                                  ebaker8571 @olivierlambert
                                  last edited by

                                  @olivierlambert

                                  OK thank you. when I attempted that it just seems to take me to xo-lite

                                  But the initial steps sound like I did correctly? Install xcp on .69, use cli to create xoa on .70 then when attempt to log in to .70 and get the connect server screen, connect .69 to it?

                                  Or am I totally as confused as I think I am.

                                  1 Reply Last reply Reply Quote 0
                                  • E Offline
                                    ebaker8571 @olivierlambert
                                    last edited by

                                    @olivierlambert

                                    I figured it out and got it working.

                                    The issue I'm running in to now though, when I log in to the xoa now and attempt to import an iso (disk) I don't have an option to import an ISO, it only gives me the options for VMDK or VHD.

                                    AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
                                    • AtaxyaNetworkA Offline
                                      AtaxyaNetwork Ambassador @ebaker8571
                                      last edited by

                                      @ebaker8571 Hi !

                                      You need to create an ISO SR first: https://docs.xcp-ng.org/storage/#-iso-sr

                                      E 1 Reply Last reply Reply Quote 0
                                      • E Offline
                                        ebaker8571 @AtaxyaNetwork
                                        last edited by

                                        @AtaxyaNetwork

                                        Sorry, user error. I wasn't clicking and selecting the SR that was created for the ISO

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