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

    Updating XenOrchestra to 5.11

    Scheduled Pinned Locked Moved IT Discussion
    xenxenserverxenorchestra
    40 Posts 5 Posters 5.8k Views
    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.
    • DanpD
      Danp @geek-baba
      last edited by

      @shwetkprabhat First step would be to remove the node_modules subdirectory from both xo-server and xo-web directories and then try rebuilding --

       rm -rf node_modules
       yarn
      
      geek-babaG 1 Reply Last reply Reply Quote 0
      • geek-babaG
        geek-baba @Danp
        last edited by

        @danp same result 😞

        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD
          Danp @geek-baba
          last edited by

          @shwetkprabhat Look for the file yarn-error.log and post its contents if it exists.

          geek-babaG 1 Reply Last reply Reply Quote 0
          • geek-babaG
            geek-baba @Danp
            last edited by

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

            yarn-error.log

            Arguments: 
              /usr/local/bin/node /usr/share/yarn/bin/yarn.js
            
            PATH: 
              /home/xoa/bin:/home/xoa/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
            
            Yarn version: 
              0.27.5
            
            Node version: 
              8.0.0
            
            Platform: 
              linux x64
            
            npm manifest: 
              No manifest
            
            yarn manifest: 
              No manifest
            
            Lockfile: 
              No lockfile
            
            Trace: 
              Error: EACCES: permission denied, mkdir '/home/xoa/.config/yarn/global'
            
            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD
              Danp @geek-baba
              last edited by

              @shwetkprabhat This was in the xo-server directory? With a modification date of today?

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

                Also, were you running as superuser when you reissued the yarn command?

                geek-babaG 1 Reply Last reply Reply Quote 0
                • geek-babaG
                  geek-baba @Danp
                  last edited by

                  @danp It was in home directory with todays modify date.

                  yarn gave error so I did sudo yarn and it showed success.

                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD
                    Danp @geek-baba
                    last edited by

                    @shwetkprabhat So is XO working now? FYI, you'll need to issue sudo bash before the yarn command.

                    geek-babaG 1 Reply Last reply Reply Quote 0
                    • geek-babaG
                      geek-baba @Danp
                      last edited by

                      @danp no not working, I meant the yarn command was successful but XOC still not starting

                      DanpD 1 Reply Last reply Reply Quote 0
                      • DanpD
                        Danp @geek-baba
                        last edited by

                        @shwetkprabhat Post the output from the following --

                        sudo bash
                        cd /opt/xo-server
                         rm -rf node_modules
                         yarn
                        
                        geek-babaG 1 Reply Last reply Reply Quote 0
                        • geek-babaG
                          geek-baba @Danp
                          last edited by

                          @danp

                          xoa@xo:~$ sudo bash
                          [sudo] password for xoa: 
                          root@xo:~# cd /opt/xo-server
                          root@xo:/opt/xo-server# rm -rf node_modules
                          root@xo:/opt/xo-server# yarn
                          yarn install v0.27.5
                          [1/4] Resolving packages...
                          [2/4] Fetching packages...
                          error Command failed.
                          Exit code: 128
                          Command: git
                          Arguments: pull
                          Directory: /usr/local/share/.cache/yarn/v1/.tmp/9c352cb3d905b22933aca1779127b89c
                          Output:
                          error: Pull is not possible because you have unmerged files.
                          hint: Fix them up in the work tree, and then use 'git add/rm <file>'
                          hint: as appropriate to mark resolution and make a commit.
                          fatal: Exiting because of an unresolved conflict.
                          info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
                          root@xo:/opt/xo-server# 
                          
                          1 Reply Last reply Reply Quote 0
                          • DanpD
                            Danp
                            last edited by

                            Does it help if you enter yarn cache clear before hand?

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

                              Why not simply build a new installation? Do you have your configuration backed up?

                              scottalanmillerS 1 Reply Last reply Reply Quote 2
                              • scottalanmillerS
                                scottalanmiller @DustinB3403
                                last edited by

                                @dustinb3403 said in Updating XenOrchestra to 5.11:

                                Why not simply build a new installation? Do you have your configuration backed up?

                                Good idea, do it the DevOps "burn it down" way. Save the headache of pupates.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller
                                  last edited by

                                  Updates, damn autocorrect.

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

                                    As much as it's taken to get to this point. I would've already had a new clean instance built. I know @Danp will get you sorted, but if this is production can you afford this amount of down time?

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

                                      Agreed that it would be simpler to just build a new VM. Still, it would be nice to know why it is failing. 😉

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

                                        @danp said in Updating XenOrchestra to 5.11:

                                        Agreed that it would be simpler to just build a new VM. Still, it would be nice to know why it is failing. 😉

                                        Avoiding going down the rabbit hole is nice too... 🙂

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

                                          FWIW, xo-server updated to 5.11.1 without issue.

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