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
    81.9k
    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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Even if not included, apt-get should go and find it.

      1 Reply Last reply Reply Quote 0
      • momurdaM
        momurda
        last edited by

        Fixed by ditching ubuntu, my SOP today with ubuntu based installers and setups.
        First try on debian, works with one warning about optional fsevents component.
        This component only seems to be for osx so not sure why it is being triggered here during the install.

        scottalanmillerS B 2 Replies Last reply Reply Quote 2
        • scottalanmillerS
          scottalanmiller @momurda
          last edited by

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

          Fixed by ditching ubuntu, my SOP today with ubuntu based installers and setups.
          First try on debian, works with one warning about optional fsevents component.
          This component only seems to be for osx so not sure why it is being triggered here during the install.

          Very odd since most of the testing is Ubuntu.

          1 Reply Last reply Reply Quote 0
          • B
            bnrstnr @momurda
            last edited by

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

            First try on debian, works with one warning about optional fsevents component.

            This happens with Ubuntu, too. Not sure what it's supposed to do, but none of the installs I've done ever have it.

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

              @momurda for what it's worth with the ISO you provided I'm seeing the same error messages.

              Jul 31 18:35:45 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:45 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:45 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:45 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:45 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:45 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:45 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:45 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:46 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:46 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:46 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:46 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:46 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:46 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:46 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:46 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:47 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:47 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:47 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:47 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:49 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:49 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:49 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:49 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:52 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:52 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:52 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:52 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:35:56 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:35:56 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:35:56 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:35:56 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:36:05 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:36:05 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:36:05 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:36:05 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:36:19 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:36:19 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:36:19 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:36:19 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:36:42 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:36:42 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:36:42 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:36:42 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:37:23 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:37:23 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:37:23 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:37:23 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              Jul 31 18:38:31 xoce xo-server[5052]: [Warn] Unhandled error event: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
              Jul 31 18:38:31 xoce xo-server[5052]:     at Object._errnoException (util.js:992:11)
              Jul 31 18:38:31 xoce xo-server[5052]:     at _exceptionWithHostPort (util.js:1014:20)
              Jul 31 18:38:31 xoce xo-server[5052]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)
              

              The ISO is missing the minimal requirements to make the install work.

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

                @dustinb3403 The new 18.04.1 live-server ISO even directly from the ubuntu site doesn't include the universe repos anymore. I was in the process of posting an issue in your github but got distracted.

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

                  @bnrstnr It's likely the same ISO just hosted from multiple sources. I'll have to see what repo's are missing.

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

                    @dustinb3403 here is all that's in the new version sources.list

                    deb http://archive.ubuntu.com/ubuntu bionic main
                    deb http://archive.ubuntu.com/ubuntu bionic-security main
                    deb http://archive.ubuntu.com/ubuntu bionic-updates main
                    
                    DustinB3403D 1 Reply Last reply Reply Quote 0
                    • momurdaM
                      momurda
                      last edited by momurda

                      Yes it is something Canonical has done to their server iso. Cant even install glances at the moment with it due to missing the software repos. Just doesnt make much sense why they would do that.

                      B 1 Reply Last reply Reply Quote 1
                      • B
                        bnrstnr @momurda
                        last edited by

                        @momurda It's super weird, I tried looking around a little this morning and couldn't find any explanation. The mini.iso choosing basic server even includes the usual repos. I'm assuming somebody messed up somewhere. There aren't even comments in the sources.list file anymore, which I've definitely never seen before.

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

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

                          @dustinb3403 here is all that's in the new version sources.list

                          deb http://archive.ubuntu.com/ubuntu bionic main
                          deb http://archive.ubuntu.com/ubuntu bionic-security main
                          deb http://archive.ubuntu.com/ubuntu bionic-updates main
                          

                          Yeah. . that is definitely a Ubuntu Fup there. . . unless they are pulling something fishy.

                          1 Reply Last reply Reply Quote 0
                          • black3dynamiteB
                            black3dynamite
                            last edited by

                            The new Ubuntu installer is meant to be lean and fast install.
                            It should work like it use to be using the alternate installer.

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

                              Someone else has already reported this as an issue, the LIVE distro is slimmed down so much that it doesn't have these repo's included, but you can install them.

                              https://ubuntuforums.org/showthread.php?t=2397273

                              Edit: Adding the multiverse repo with sudo add-apt-repository multiverse allows the install to work without issue.

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

                                I'm testing now with a possible patch for this, even though this is insane that Canonical would remove the multiverse repo from their mainline distro. . .

                                FFS.

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

                                  I've added a repo addition to the start of the script, literally it just adds the multiverse repository and updates and upgrades the system while it's at it.

                                  Of course this could cause issues with other issues so please test it with multiple distro's for me. If it causes issues, I'll simply add it as a troubleshooting step to make sure that the repo's are manually added prior to attempting the installation . . .

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

                                    I've even made an issue on my own GH to find better ways of checking for and adding the repo if it's required.

                                    https://github.com/Jarli01/xenorchestra_installer/issues/25

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

                                      @dustinb3403 See the first answer here for how to check for the pre-existence of the repository.

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

                                        Ok I have a patch made besides that really ugly one that will check for the multiverse repo and add it, please test it on other distro's and let me know of any issues.

                                        https://github.com/Jarli01/xenorchestra_installer/pull/26

                                        For now I'm going to back out the previous changes since this is a better approach.

                                        Edit: It might fail if multiverse is already there. . . need to confirm more. But for now, going home to see my daughter!

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

                                          Can others test this patch for me and let me know what issues you might encounter. I get the expected results here, but I've only been able to test with the mini 18.04.1-live Ubuntu iso so far.

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

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

                                            https://github.com/Jarli01/xenorchestra_installer/pull/26

                                            I was able to install on 18.04.1, its says successfully installed but for whatever reason not able to access it via the browser. Ran the updated script as well, that was successful too, still not able to access via web browser. Its a fresh install. Very weird...

                                            DustinB3403D 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 14
                                            • 15
                                            • 1 / 15
                                            • First post
                                              Last post