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

    What is xo-server-log?

    Scheduled Pinned Locked Moved
    Compute
    3
    18
    909
    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.
    • julien-fJ
      julien-f Vates đŸȘ Co-Founder XO Team @Ascar
      last edited by

      @Ascar If you installed XO yourself (following our documentation), you should know how to start XO.

      I cannot help you if you don't know how XO was installed on your machine.

      A 2 Replies Last reply Reply Quote 0
      • A
        Ascar @julien-f
        last edited by

        @julien-f I installed XO myself. The documentation you shared the link for is quite quite helpful. Reading. Thanks.

        1 Reply Last reply Reply Quote 0
        • A
          Ascar @julien-f
          last edited by

          @julien-f Well, I know how to start XO, in fact I don't need to start it as it is always running. I can access XO from browser and everything is good there.

          My original question was how to remove entries from backup logs and I did not (and still don't) understand how to issue the xo-server-logs --delete namespace=jobs command while I am in the shell. Can you guide me like I am 1st-grade student?

          julien-fJ 1 Reply Last reply Reply Quote 0
          • julien-fJ
            julien-f Vates đŸȘ Co-Founder XO Team @Ascar
            last edited by

            @Ascar Let me retry my previous question: how do you make xo-server start in your install?

            A 1 Reply Last reply Reply Quote 0
            • A
              Ascar @julien-f
              last edited by

              @julien-f Well, I made a Debian virtual machine, updated it and then followed the instructions on how to build XO from sources. After that I was accessing XO through browser and XO started automatically on VM boot. Until now there was no need for me do anything special in the command line on XO VM. After receiving your previous message I went to /opt/xo/xo-server and executed yarn start and I saw the message saying that the TCP port is already occupied which means that I basically invoked the startup procedure which happens automatically when my VM starts.

              julien-fJ 1 Reply Last reply Reply Quote 0
              • julien-fJ
                julien-f Vates đŸȘ Co-Founder XO Team @Ascar
                last edited by

                @Ascar Ok, this is not installing from the sources following the official documentation!! This information would have been useful sooner.

                xo-server-logs is available directly in the directory where xo-server is compiled under the name ./dist/logs-cli.mjs.

                For more information, please ask directly on the repo you linked.

                A 1 Reply Last reply Reply Quote 0
                • A
                  Ascar @julien-f
                  last edited by Ascar

                  @julien-f Alright, as far as I could understand I would not have gone through this puzzle solving if I had XO built following this guide.

                  Thank you clearing this out for me. Will make another machine and try again.

                  julien-fJ 1 Reply Last reply Reply Quote 0
                  • julien-fJ
                    julien-f Vates đŸȘ Co-Founder XO Team @Ascar
                    last edited by

                    @Ascar It should be working fine with the other install but the answer to your initial question depends of how you installed XO, therefore my question.

                    Maybe @ronivay can answer your question.

                    ronivayR 1 Reply Last reply Reply Quote 0
                    • ronivayR
                      ronivay Top contributor @julien-f
                      last edited by ronivay

                      Sure. @Ascar the executable you’re looking for is not called xo-server-logs for the installation done with XenOrchestraInstallerUpdater script. As mentioned above it’s installed beside xo-server as logs-cli.mjs and can be found here (assuming you didn’t change default install location).

                      $ sudo /opt/xo/xo-server/dist/logs-cli.mjs -h

xo-server-logs --help, -h



                      Help shows command examples as xo-server-logs, but you need to use above executable instead.

                      You can also easily make xo-server-logs command to work if you wish by running:

                      sudo ln -s /opt/xo/xo-server/dist/logs-cli.mjs /usr/local/bin/xo-server-logs

                      But i wouldn’t recommend it if this is needed only once.

                      A 1 Reply Last reply Reply Quote 1
                      • A
                        Ascar @ronivay
                        last edited by

                        @ronivay So happy to see you here. Thank you for clarifying my confusion. I did not modify installation paths and I found what I was looking for. logs-cli.mjs does not run by itself and needs node to be prepended. Is this correct? However I made a symlink as you explained and it runs as xo-server-logs directly.

                        ronivayR 1 Reply Last reply Reply Quote 0
                        • ronivayR
                          ronivay Top contributor @Ascar
                          last edited by

                          That script has a shebang pointing to node (first line), so no need to define it separately, just execute the script directly.

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