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

    Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

    IT Discussion
    how to xen orchestra ubuntu 15.10 debian xen open source ubuntu linux xenserver
    24
    609
    281.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.
    • travisdh1T
      travisdh1 @brandon
      last edited by

      @brandon Is xo-web installed directly in /opt? Looks like you might be trying to start it from the wrong place to me.

      B DustinB3403D 2 Replies Last reply Reply Quote 0
      • B
        brandon @travisdh1
        last edited by

        @travisdh1 Cant go to xo-web...

        root@xenorc:/opt# ls
        node_modules npm-debug.log xo-server

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

          @travisdh1 the installer script should create the directories and install into them without any user intervention.

          @brandon are the folders xo-web and xo-server under /opt/ ?

          B 1 Reply Last reply Reply Quote 0
          • B
            brandon @DustinB3403
            last edited by

            @DustinB3403 No it didnt clone from git... Should we try to fix the Debian one since it is 90 % done?

            1 Reply Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @brandon
              last edited by

              @brandon said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

              @travisdh1 Cant go to xo-web...

              root@xenorc:/opt# ls
              node_modules npm-debug.log xo-server

              Ah, well, something didn't work right in the script then. You should have an xo-web directory as well.

              B 2 Replies Last reply Reply Quote 0
              • B
                brandon @travisdh1
                last edited by

                @travisdh1 I have been trying for days...

                1 Reply Last reply Reply Quote 0
                • B
                  brandon @travisdh1
                  last edited by

                  @travisdh1

                  Cloning into 'xo-server'...
                  remote: Counting objects: 10478, done.
                  remote: Compressing objects: 100% (59/59), done.
                  remote: Total 10478 (delta 31), reused 0 (delta 0), pack-reused 10419
                  Receiving objects: 100% (10478/10478), 2.71 MiB | 1.11 MiB/s, done.
                  Resolving deltas: 100% (7503/7503), done.
                  Checking connectivity... done.
                  Cloning into 'xo-web'...
                  remote: Counting objects: 26050, done.
                  remote: Compressing objects: 100% (11/11), done.
                  error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
                  fatal: The remote end hung up unexpectedly
                  fatal: early EOF
                  fatal: index-pack failed

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

                    Need to determine why git clone -b stable https://github.com/vatesfr/xo-web is failing.

                    B 1 Reply Last reply Reply Quote 1
                    • B
                      brandon @Danp
                      last edited by

                      @Danp I am going to run :

                      git clone -b stable https://github.com/vatesfr/xo-web
                      sudo cp sample.config.yaml .xo-server.yaml
                      sudo sed -i /mounts/a\" '/': '/opt/xo-web/dist'" .xo-server.yaml
                      cd /opt/xo-web
                      sudo npm install
                      sudo npm run build

                      since that is where it stopped?

                      travisdh1T 1 Reply Last reply Reply Quote 1
                      • travisdh1T
                        travisdh1 @brandon
                        last edited by

                        @brandon Yes, should get the web interface working.

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

                          This happened after getting to npm install

                          root@xenorc:/opt/xo-web# sudo npm install
                          npm ERR! git fetch -a origin (git://github.com/fizzed/font-mfizz.git)
                          npm ERR! git fetch -a origin (git://github.com/gulpjs/gulp.git)
                          npm WARN addRemoteGit Error: Command failed: git config --get remote.origin.url
                          npm WARN addRemoteGit
                          npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12)
                          npm WARN addRemoteGit at emitTwo (events.js:106:13)
                          npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7)
                          npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16)
                          npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11)
                          npm WARN addRemoteGit at emitOne (events.js:96:13)
                          npm WARN addRemoteGit at Socket.emit (events.js:188:7)
                          npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12)
                          npm WARN addRemoteGit fizzed/font-mfizz resetting remote /root/.npm/_git-remotes/git-https-github-com-fizzed-font-mfizz-git-b15d96d5 because of error: { Error: Command failed: git config --get remote.origin.url
                          npm WARN addRemoteGit
                          npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12)
                          npm WARN addRemoteGit at emitTwo (events.js:106:13)
                          npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7)
                          npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16)
                          npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11)
                          npm WARN addRemoteGit at emitOne (events.js:96:13)
                          npm WARN addRemoteGit at Socket.emit (events.js:188:7)
                          npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12)
                          npm WARN addRemoteGit killed: false,
                          npm WARN addRemoteGit code: 1,
                          npm WARN addRemoteGit signal: null,
                          npm WARN addRemoteGit cmd: 'git config --get remote.origin.url' }
                          Killed

                          root@xenorc:/opt/xo-web#

                          travisdh1T 1 Reply Last reply Reply Quote 0
                          • travisdh1T
                            travisdh1 @brandon
                            last edited by

                            @olivier Any reason the first two lines error out on your end?

                            @brandon This looks like another git problem. The npm install script wants to download a couple things from git, which fail and cause the rest of the script to fail.

                            B 1 Reply Last reply Reply Quote 0
                            • B
                              brandon @travisdh1
                              last edited by

                              @travisdh1 I have no idea.... network connection is fine...

                              1 Reply Last reply Reply Quote 0
                              • DashrenderD
                                Dashrender
                                last edited by

                                can you manually fetch those two gits that fail?

                                B 1 Reply Last reply Reply Quote 0
                                • B
                                  brandon @Dashrender
                                  last edited by

                                  @Dashrender Okay must I run:
                                  git fetch -a origin (git://github.com/fizzed/font-mfizz.git)
                                  git fetch -a origin (git://github.com/gulpjs/gulp.git)

                                  but after that I need to rerun npm install then it will bomb out again?

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

                                    @brandon May want to read this thread for some possible solutions.

                                    DashrenderD 1 Reply Last reply Reply Quote 0
                                    • DashrenderD
                                      Dashrender @Danp
                                      last edited by

                                      @Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

                                      @brandon May want to read this thread for some possible solutions.

                                      Interesting - so he possibly has an application filtering firewall that is blocking git calls.

                                      See @BRRABill, a change of git: to https: gets around the filtering in this case - application filtering, rarely worth the expense.

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

                                        I wonder if it would be easier for "us" to simply build an appliance version of XO and offer that as a direct download.

                                        Maybe XOS?

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

                                          @DustinB3403 No thanks. I'll leave that to @olivier and crew. 😉

                                          1 Reply Last reply Reply Quote 0
                                          • olivierO
                                            olivier
                                            last edited by olivier

                                            In any case, you'll hit the same issues: you can't guess what's inside the user network. Believe me, you don't want to spend your non-working time making support for free because someone forgot there is a proxy between their Xen Orchestra installation and outside.

                                            edit: I think I have roughly some stats on support, at least half of the time is related to user configuration issues.

                                            edit2 : my 2 cents on the current issue: not enough RAM to build npm packages.

                                            DustinB3403D DashrenderD B 3 Replies Last reply Reply Quote 3
                                            • 1
                                            • 2
                                            • 27
                                            • 28
                                            • 29
                                            • 30
                                            • 31
                                            • 30 / 31
                                            • First post
                                              Last post