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

    Pools don't appear then disappear on custom XO but are fine on XOA

    Scheduled Pinned Locked Moved Management
    18 Posts 4 Posters 950 Views 3 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.
    • H Offline
      Hibikisayo @olivierlambert
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • H Offline
        Hibikisayo @Hibikisayo
        last edited by

        @Hibikisayo and now there broken again, and I can't seem to load logs to find the issue.

        1 Reply Last reply Reply Quote 0
        • H Offline
          Hibikisayo
          last edited by

          Test remote

          unknown error from the peer
          SHOW LOGS

          but when I look at logs, it just spins forever. I let it run over night for 9 hours.

          any thoughts? I tried to find the logs manually but could not find them VIA cli.
          the folder /var/log/syslog no syslog folder.

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

            The logs are the output of xo-server

            1 Reply Last reply Reply Quote 0
            • JamfoFLJ Offline
              JamfoFL
              last edited by

              I had that exact, same issue when trying to run Node 20. Rolling back to an older version of Node did fix the issue for me.

              @olivierlambert In @Hibikisayo's defense, the Packages and Pre-requisites page only specifies the use of the latest Node LTS:
              e665ce3c-75b8-42d6-abb9-32a2ec485fc2-image.png

              Following the "this page" link takes you to an instructional page where you follow yet another link to be taken to the page with instructions on how to install Node depending on which OS you are running. That page is very confusing, however, and you have to dig even further in order to find out which version is the latest LTS version. A cursory look and you would think that Node 20 is the most current (which it is), but you have to dig and interpret charts to figure out which version is the latest LTS version. This would surprise people to find out it's not Node 20, or even Node 19, which is the latest LTS version.

              Of course, none of this is on Vates or Xen Orchestra, since it's the NodeSource site itself that is so darned confusing... but I can see how anyone would think they are installing the correct version when they are accidentally two versions ahead.

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

                It's hard to make the documentation dynamic pointing automatically to the latest LTS. I don't know how we can improve this, but it's a small impediment to carefully read the doc to enjoy it 🙂

                JamfoFLJ H 3 Replies Last reply Reply Quote 0
                • JamfoFLJ Offline
                  JamfoFL @olivierlambert
                  last edited by

                  @olivierlambert Agreed... it's definitely an issue on the NodeSource side and nothing to do with Vates and your documentation! You'd think with that nice chart they have showing each individual version and its compatibility, they could put one more box indicating which is the LTS at any given time.

                  1 Reply Last reply Reply Quote 0
                  • H Offline
                    Hibikisayo @olivierlambert
                    last edited by

                    @olivierlambert I guess I made an assumption, cause most guides out there, especially for linux, there pictures are not up to date on what version to use.

                    Looking back I can see where I missed it.

                    as for my issue, I did roll it back to node 16.20.2 ( when I reinstalled node using NODE_MAJOR 16 this is what got installed, doesn't match your version exactly) and it still won't load the logs or join my SMB share.

                    How can I view the logs and upload them here?

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

                      The doc gives an example, it's the latest Node LTS you should use (so right now it's Node 18).

                      H 1 Reply Last reply Reply Quote 0
                      • H Offline
                        Hibikisayo @olivierlambert
                        last edited by

                        @olivierlambert I don't do documentation, so I'm not 100% sure how easy something like just adding what version XO uses.

                        1 Reply Last reply Reply Quote 0
                        • H Offline
                          Hibikisayo @olivierlambert
                          last edited by

                          @olivierlambert switched to node 18.18 and still no logs, or remote server connect 😞

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

                            It's hard to assist without much information. Can you check the IP of the host is correct? (if you navigate to it).

                            1 Reply Last reply Reply Quote 0
                            • olivierlambertO olivierlambert moved this topic from Xen Orchestra on
                            • DanpD Online
                              Danp Pro Support Team
                              last edited by

                              FWIW, I just ran into this same issue with Node 20.9.0, which is the current LTS version. Reverting to Node 18.18.2 resolved the issue for me.

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