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

    Xen Orchestra - Community Edition - Installing with Yarn

    Scheduled Pinned Locked Moved IT Discussion
    xen orchestra updaterubuntu 16.10xenorchestraxenserverxen orchestra communityxoxocexcp-ngdebianubuntu
    296 Posts 22 Posters 87.7k 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 @DustinB3403
      last edited by

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

      Can you create an issue on GH?

      I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:

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

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

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

        Can you create an issue on GH?

        I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:

        ....

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

          https://github.com/vatesfr/xen-orchestra/issues/3880

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

            I am seeing another issue with yarn repo signature, I assume the script would be impacted too, did not try to update as I see folks complaining about 5.33.

            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
            W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
            W: Some index files failed to download. They have been ignored, or old ones used instead.
            
            DanpD 1 Reply Last reply Reply Quote 0
            • DanpD
              Danp @geek-baba
              last edited by

              @shwetkprabhat I recently updated the script to deal with the expired repo key. Let us know if you run into any issues when you do update. :smiling_face:

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

                @Danp worked like a charm! Updated flawlessly and also repo signature is fixed now!

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

                  @DustinB3403 Got this running on my home lab box tonight. Worked great.

                  dbeatoD B 2 Replies Last reply Reply Quote 2
                  • dbeatoD
                    dbeato @travisdh1
                    last edited by

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

                    @DustinB3403 Got this running on my home lab box tonight. Worked great.

                    Let us know how your backups are working 🙂

                    travisdh1T DustinB3403D 2 Replies Last reply Reply Quote 0
                    • travisdh1T
                      travisdh1 @dbeato
                      last edited by

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

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

                      @DustinB3403 Got this running on my home lab box tonight. Worked great.

                      Let us know how your backups are working 🙂

                      Hah, I'll have to try hooking it to my B2 first. Might be "interesting" all around with the backups!

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

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

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

                        @DustinB3403 Got this running on my home lab box tonight. Worked great.

                        Let us know how your backups are working 🙂

                        There was an issue that was just patched yesterday that affected backups.

                        So you may need to update.

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

                          @travisdh1 Make sure you use 2 vcpu in your XOCE VM if you want to use Delta backups, I believe they won't merge otherwise.

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

                            @bnrstnr Actually, that should be fixed now as well.

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

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

                              @bnrstnr Actually, that should be fixed now as well.

                              Was that a bug? I was under the impression it was a new requirement.

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

                                @Danp As of last week it was still affecting me. If he wants to try with 1, it can easily be adjusted later and it just starts working.

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

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

                                  @Danp As of last week it was still affecting me. If he wants to try with 1, it can easily be adjusted later and it just starts working.

                                  We could likely create a check for 1 cpu and raise a flag for it with an optional "continue" during the installation script.

                                  Not sure if it's worthwhile.

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

                                    @DustinB3403 Yes, it was a bug in Jest library, which has since been fixed. They bumped the version requirements yesterday, so a rebuild should now require v24 (I think) or greater.

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

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

                                      We could likely create a check for 1 cpu and raise a flag for it with an optional "continue" during the installation script.

                                      Not sure if it's worthwhile.

                                      Not worth the effort IMO. You could add a comment to the troubleshooting section.

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

                                        I was thinking about adding the check because the XOA VM is built with 2 cpu, just to keep it consistent with the devs.

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

                                          I've updated the troubleshooting docs with the new dependencies and system performance and general troubleshooting.

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

                                            This command would tell the user (us) how many CPU's the host has.

                                            cat /proc/cpuinfo | grep siblings | uniq

                                            But again, not sure if we want to start requiring more than 1 vCPU for this since the system does work with just the 1. Maybe leaving this to the troubleshooting documentation is best.

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