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

    Nos stats problem (but not the know one I guess)

    Scheduled Pinned Locked Moved Management
    12 Posts 2 Posters 33 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      @cgasser said in Nos stats problem (but not the know one I guess):

      connect ECONNREFUSED 127.0.0.1:443

      That's the issue. XO needs to have access to all hosts management IPs, not just the master. I assume you made a tunnel or something specific to make XO connecting to the master. It's not related to 8.2 or 8.3, it's an architecture thing on pools since XCP exists 🙂

      C 1 Reply Last reply Reply Quote 0
      • C Offline
        cgasser @olivierlambert
        last edited by

        @olivierlambert Hi! No, that is not the case. All servers are in the same rack. Connected to the same switch. Same network (VLAN, IP Range).

        XOA runs on the master server. No stats for that server. But stats for another server are ok (just one), all the others are not working.

        C

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

          Then, there is one machine thinking its management IP is 127.0.0.1

          C 1 Reply Last reply Reply Quote 0
          • C Offline
            cgasser @olivierlambert
            last edited by

            @olivierlambert Right. Any idea on how to check and change that? Management interfaces seems to be OK on the hosts. I can access and manage all servers. It seems it is just the stats that are not working. C

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

              I would print the result of the command xe host-param-list uuid=<problematic host UUID> to see where this localhost IP is set somlewhere.

              C 1 Reply Last reply Reply Quote 0
              • C Offline
                cgasser @olivierlambert
                last edited by

                @olivierlambert Nothing with 127.0.0.1. Also hostname ( RO): is set correct. I can find some localhost entries. But for license server, etc. C

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

                  Let's try to grep 127.0.0.1 in the XAPI DB file then 🤔

                  C 1 Reply Last reply Reply Quote 0
                  • C Offline
                    cgasser @olivierlambert
                    last edited by

                    @olivierlambert Would you mind giving me a hint on where to find that file? C

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      cgasser @cgasser
                      last edited by

                      Folder /var/lib/xcp/ file xapi? C

                      C 1 Reply Last reply Reply Quote 0
                      • C Offline
                        cgasser @cgasser
                        last edited by

                        If it is the state.db file, then there is no mention of 127.0.0.1.

                        grep "127.0.0.1" state.db brings nothing no result. C

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