ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra - Community Edition - Installing with Yarn

    IT Discussion
    xen orchestra updater ubuntu 16.10 xenorchestra xenserver xen orchestra community xo xoce xcp-ng debian ubuntu
    22
    296
    72.2k
    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.
    • KjuK
      Kju
      last edited by

      how can i update to 5.18 ?
      the script for updating
      sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
      stays on 5.17

      DanpD 1 Reply Last reply Reply Quote 0
      • hobbit666H
        hobbit666
        last edited by

        Can't you update through the web gui?

        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD
          Danp @hobbit666
          last edited by

          @hobbit666 said in Xen Orchestra - Community Edition - Installing with Yarn:

          Can't you update through the web gui?

          Only if you are running the pre-built appliance (XOA). There isn't an updater available in the GUI when built from source.

          hobbit666H 1 Reply Last reply Reply Quote 0
          • DanpD
            Danp @Kju
            last edited by

            @kju said in Xen Orchestra - Community Edition - Installing with Yarn:

            how can i update to 5.18 ?
            the script for updating
            sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
            stays on 5.17

            Not enough details here to know how to help. You could post the output from the console window showing the results from running the above command.

            Also, show us the contents of the /opt directory.

            1 Reply Last reply Reply Quote 1
            • hobbit666H
              hobbit666 @Danp
              last edited by

              @danp ah ok

              1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403
                last edited by

                Are you being prompted to identify yourself to git?

                git config --global user.email "[email protected]"
git config --global user.name "Your Name"
                DanpD KjuK B 3 Replies Last reply Reply Quote 3
                • DanpD
                  Danp @DustinB3403
                  last edited by

                  @dustinb3403 Good call... I had forgotten about that issue.

                  1 Reply Last reply Reply Quote 1
                  • KjuK
                    Kju @DustinB3403
                    last edited by

                    @dustinb3403 thx, this solved my problem :thumbs_up: 😄

                    DustinB3403D 2 Replies Last reply Reply Quote 1
                    • DustinB3403D
                      DustinB3403 @Kju
                      last edited by

                      @kju said in Xen Orchestra - Community Edition - Installing with Yarn:

                      @dustinb3403 thx, this solved my problem :thumbs_up: 😄

                      You're welcome.

                      1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403 @Kju
                        last edited by

                        @kju And welcome to the party.

                        1 Reply Last reply Reply Quote 0
                        • B
                          Barnseh
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • noelwestonN
                            noelweston
                            last edited by

                            Hope someone can point me in the right direction - I thought it was a good idea to run the update today, and I now have a non-functioning Xen Orchestra instance.

                            I did get some warnings about node versions, so re-ran the updater with a node version change.

                            The only error I can identify at the moment is this one in syslog:
                            xo-server.service: Failed at step CHDIR spawning /usr/local/bin/node: No such file or directory

                            I've tried re-running the updater with -n stable and -n lts with no joy.

                            systemctl status xo-server.service shows:
                            xo-server.service - XO Server Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Mon 2018-06-25 13:11:32 BST; 4min 23s ago Process: 1141 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=200/CHDIR) Main PID: 1141 (code=exited, status=200/CHDIR)

                            Where do I start?

                            Thanks

                            Noel Weston

                            DustinB3403D 1 Reply Last reply Reply Quote 0
                            • DustinB3403D
                              DustinB3403 @noelweston
                              last edited by

                              @noelweston Start by providing the output of journalctl -u xo-server -f -n 50

                              1 Reply Last reply Reply Quote 0
                              • noelwestonN
                                noelweston
                                last edited by 

                                -- Logs begin at Mon 2018-06-25 13:11:23 BST. --
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:11:31 xoa systemd[1]: Stopped XO Server.
Jun 25 13:11:31 xoa systemd[1]: Started XO Server.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:11:31 xoa systemd[1]: Stopped XO Server.
Jun 25 13:11:31 xoa systemd[1]: Started XO Server.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:11:32 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:11:32 xoa systemd[1]: Stopped XO Server.
Jun 25 13:11:32 xoa systemd[1]: xo-server.service: Start request repeated too quickly.
Jun 25 13:11:32 xoa systemd[1]: Failed to start XO Server.
Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:23 xoa systemd[1]: Started XO Server.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:23 xoa systemd[1]: Started XO Server.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:23 xoa systemd[1]: Started XO Server.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:23 xoa systemd[1]: Started XO Server.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:16:23 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:23 xoa systemd[1]: Started XO Server.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:16:23 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jun 25 13:16:24 xoa systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Jun 25 13:16:24 xoa systemd[1]: Stopped XO Server.
Jun 25 13:16:24 xoa systemd[1]: xo-server.service: Start request repeated too quickly.
Jun 25 13:16:24 xoa systemd[1]: Failed to start XO Server.
                                1 Reply Last reply Reply Quote 0
                                • DustinB3403D
                                  DustinB3403
                                  last edited by

                                  Another great place to start with is the troubleshooting template: https://github.com/Jarli01/xenorchestra_installer/blob/master/Troubleshooting.md

                                  1 Reply Last reply Reply Quote 0
                                  • DustinB3403D
                                    DustinB3403
                                    last edited by DustinB3403

                                    Post that last 200 lines, as that error is just repeating. (change 50 to 200)

                                    1 Reply Last reply Reply Quote 0
                                    • DustinB3403D
                                      DustinB3403
                                      last edited by

                                      As another option, you could just restore your snapshop (assuming you made one) and then download the config file and build a new instance and then import the config file.

                                      1 Reply Last reply Reply Quote 0
                                      • noelwestonN
                                        noelweston
                                        last edited by

                                        Hi Dustin -

                                        That's all that journalctl gives me - I assume this is since the last reboot?

                                        The troubleshooting info is pretty much what I've already got - service status is above, I did the git configs after the first update attempt.

                                        /var/log/syslog has this:

                                        Jun 25 13:11:31 xoa systemd[1]: Started Hold until boot process finishes up.
Jun 25 13:11:31 xoa systemd[1141]: xo-server.service: Failed at step CHDIR spawning /usr/local/bin/node: No such file or directory
Jun 25 13:11:31 xoa systemd[1]: Started Terminate Plymouth Boot Screen.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.

                                        Unfortunately no snapshot - I've never had an issue with the updates before, so didn't even think to do so.

                                        DustinB3403D 1 Reply Last reply Reply Quote 0
                                        • DustinB3403D
                                          DustinB3403 @noelweston
                                          last edited by

                                          @noelweston said in Xen Orchestra - Community Edition - Installing with Yarn:

                                          Hi Dustin -

                                          That's all that journalctl gives me - I assume this is since the last reboot?

                                          Yes, that is correct.

                                          The troubleshooting info is pretty much what I've already got - service status is above, I did the git configs after the first update attempt.

                                          /var/log/syslog has this:

                                          Jun 25 13:11:31 xoa systemd[1]: Started Hold until boot process finishes up.
Jun 25 13:11:31 xoa systemd[1141]: xo-server.service: Failed at step CHDIR spawning /usr/local/bin/node: No such file or directory
Jun 25 13:11:31 xoa systemd[1]: Started Terminate Plymouth Boot Screen.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Main process exited, code=exited, status=200/CHDIR
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Unit entered failed state.
Jun 25 13:11:31 xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.

                                          Unfortunately no snapshot - I've never had an issue with the updates before, so didn't even think to do so.

                                          So your only options are to either restore from backup (assuming you were at least making backups) or to build a new instance.

                                          @noelweston do you have your configuration backed up?

                                          1 Reply Last reply Reply Quote 0
                                          • noelwestonN
                                            noelweston
                                            last edited by

                                            Yes, I do have a backup... not that recent, but it will do.

                                            Any idea what went wrong?

                                            DustinB3403D 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 11
                                            • 12
                                            • 13
                                            • 14
                                            • 15
                                            • 13 / 15
                                            • First post
                                              Last post