XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Problems building from source

    Scheduled Pinned Locked Moved Xen Orchestra
    30 Posts 3 Posters 12.2k Views 1 Watching
    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 Online
      Danp Pro Support Team
      last edited by

      FWIW, I encountered some issues today when attempting to update my Ubuntu-based XO VM to the latest source --

      • LTS Node is now v16.13.0. When I try to build with this version, I received a warning --
      warning url-loader@1.1.2: Invalid bin field for "url-loader".
      

      Dropping Node back to v14.18.2 seems to have solved this issue, so it may simply be an issue with the latest version of Node.

      • I received additional warnings even with the earlier Node version --
      warning "lint-staged > listr2@3.13.3" has unmet peer dependency "enquirer@>= 2.3.0 < 3".
      
      warning package.json: "dependencies" has dependency "promise-toolbox" with range "^0.20.0" that collides with a dependency in "devDependencies" of the same name with version "^0.19.2"
      

      Anyone else? Suggestions on how to resolve?

      julien-fJ 1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Pinging @florent

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Is that just a warning?

          1 Reply Last reply Reply Quote 0
          • DanpD Online
            Danp Pro Support Team
            last edited by

            Yes. I have XO up and running. Seeing some odd behavior (such as duplicate entries in restore picklist) and VDI_IO_ERROR on test restore. Going to revert to earlier snapshot and retest.

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Okay keep us posted 🙂

              DanpD 1 Reply Last reply Reply Quote 0
              • DanpD Online
                Danp Pro Support Team @olivierlambert
                last edited by

                @olivierlambert VM restore working correctly now that I reverted to earlier commit --

                commit 4dc4b635f2f44dbde02d2671bcfd5cecb1b3df4f
                2021-10-29 15:50:42 +0200
                
                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  Adding @julien-f in the loop.

                  So @Danp you were on latest master commit, right?

                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD Online
                    Danp Pro Support Team @olivierlambert
                    last edited by

                    @olivierlambert Yes... as of an hour ago. Let me know how I can help to diagnose the issue.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      @julien-f will come back here when he can 🙂

                      1 Reply Last reply Reply Quote 0
                      • julien-fJ Offline
                        julien-f Vates 🪐 Co-Founder XO Team @Danp
                        last edited by

                        @danp Could not reproduce the issue with Node LTS, at what step do you get the error? When installing dependencies? Or during the build of a specific package?

                        DanpD 2 Replies Last reply Reply Quote 0
                        • DanpD Online
                          Danp Pro Support Team @julien-f
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • DanpD Online
                            Danp Pro Support Team @julien-f
                            last edited by

                            @julien-f When it is fetching packages --

                            # n lts
                               installed : v16.13.0 (with npm 8.1.0)
                            
                            # yarn
                            yarn install v1.22.15
                            [1/5] Validating package.json...
                            [2/5] Resolving packages...
                            [3/5] Fetching packages...
                            warning url-loader@1.1.2: Invalid bin field for "url-loader".
                            info fsevents@2.3.2: The platform "linux" is incompatible with this module.
                            info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
                            info fsevents@1.2.13: The platform "linux" is incompatible with this module.
                            info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
                            [4/5] Linking dependencies...
                            [5/5] Building fresh packages...
                            Done in 82.13s.
                            
                            julien-fJ 1 Reply Last reply Reply Quote 0
                            • julien-fJ Offline
                              julien-f Vates 🪐 Co-Founder XO Team @Danp
                              last edited by

                              @danp I don't have the url-loader issue, can you check after my latest fixes?

                              yarn install v1.22.15
                              [1/5] Validating package.json...
                              [2/5] Resolving packages...
                              [3/5] Fetching packages...
                              info fsevents@2.3.2: The platform "linux" is incompatible with this module.
                              info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
                              info fsevents@1.2.13: The platform "linux" is incompatible with this module.
                              info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
                              [4/5] Linking dependencies...
                              [5/5] Building fresh packages...
                              success Saved lockfile.
                              Done in 12.29s.
                              
                              DanpD 2 Replies Last reply Reply Quote 0
                              • DanpD Online
                                Danp Pro Support Team @julien-f
                                last edited by

                                @julien-f Ok.. now it appears to be working with the latest changes. 🙂

                                julien-fJ 1 Reply Last reply Reply Quote 0
                                • julien-fJ Offline
                                  julien-f Vates 🪐 Co-Founder XO Team @Danp
                                  last edited by

                                  @danp Great, thanks for your help 🙂

                                  DanpD 1 Reply Last reply Reply Quote 0
                                  • DanpD Online
                                    Danp Pro Support Team @julien-f
                                    last edited by

                                    @julien-f Now seeing the following when I try to restore any VM --

                                    backupNg.importVmBackup
                                    {
                                      "id": "remote-2//xo-vm-backups/1cd1077d-08ff-3947-2a2e-25b93cf4cc95/20211201T061100Z.json",
                                      "settings": {
                                        "newMacAddresses": false
                                      },
                                      "sr": "d556b0f0-b9b8-0ead-ab33-85ac3f5eb02d"
                                    }
                                    {
                                      "generatedMessage": true,
                                      "code": "ERR_ASSERTION",
                                      "actual": {
                                        "type": "Buffer",
                                        "data": [
                                          140,
                                          250,
                                          157,
                                          216,
                                          113,
                                          162,
                                          67,
                                          132,
                                          156,
                                          230,
                                          188,
                                          249,
                                          162,
                                          110,
                                          40,
                                          93
                                        ]
                                      },
                                      "expected": {
                                        "type": "Buffer",
                                        "data": [
                                          140,
                                          250,
                                          157,
                                          216,
                                          113,
                                          162,
                                          67,
                                          132,
                                          156,
                                          230,
                                          188,
                                          249,
                                          162,
                                          110,
                                          40,
                                          93
                                        ]
                                      },
                                      "operator": "strictEqual",
                                      "message": "Values have same structure but are not reference-equal:
                                    
                                    Buffer(16) [Uint8Array] [
                                      140,
                                      250,
                                      157,
                                      216,
                                      113,
                                      162,
                                      67,
                                      132,
                                      156,
                                      230,
                                      188,
                                      249,
                                      162,
                                      110,
                                      40,
                                      93
                                    ]
                                    ",
                                      "name": "AssertionError",
                                      "stack": "AssertionError [ERR_ASSERTION]: Values have same structure but are not reference-equal:
                                    
                                    Buffer(16) [Uint8Array] [
                                      140,
                                      250,
                                      157,
                                      216,
                                      113,
                                      162,
                                      67,
                                      132,
                                      156,
                                      230,
                                      188,
                                      249,
                                      162,
                                      110,
                                      40,
                                      93
                                    ]
                                    
                                        at VhdSynthetic.readHeaderAndFooter (/opt/xen-orchestra/packages/vhd-lib/src/Vhd/VhdSynthetic.js:79:14)
                                        at RemoteAdapter._createSyntheticStream (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:523:5)
                                        at Array.<anonymous> (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:539:30)"
                                    }
                                    
                                    julien-fJ 1 Reply Last reply Reply Quote 0
                                    • julien-fJ Offline
                                      julien-f Vates 🪐 Co-Founder XO Team @Danp
                                      last edited by

                                      @danp I'm on it 🙂

                                      DanpD 1 Reply Last reply Reply Quote 0
                                      • DanpD Online
                                        Danp Pro Support Team @julien-f
                                        last edited by

                                        @julien-f FWIW, I rebuilt with the new yarn.lock and now I'm getting VDI_IO_ERROR again.

                                        julien-fJ 1 Reply Last reply Reply Quote 0
                                        • julien-fJ Offline
                                          julien-f Vates 🪐 Co-Founder XO Team @Danp
                                          last edited by

                                          @danp Assertion error fixed, I have not investigated the VDI_IO_ERROR yet.

                                          DanpD 1 Reply Last reply Reply Quote 0
                                          • DanpD Online
                                            Danp Pro Support Team @julien-f
                                            last edited by

                                            @julien-f From the system logs --

                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]: 2021-12-01T12:09:48.669Z xo:xo-server ERROR uncaught exception {
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:   error: TypeError: this disposable has already been disposed
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Disposable.dispose (/opt/xen-orchestra/node_modules/promise-toolbox/Disposable.js:35:13)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.<anonymous> (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:527:42)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.emit (node:events:402:35)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.emit (node:domain:475:12)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:118:17)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at emitCloseNT (/opt/xen-orchestra/node_modules/async-iterator-to-stream/node_modules/readable-stream/lib/internal/streams/destroy.js:64:8)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at emitErrorAndCloseNT (/opt/xen-orchestra/node_modules/async-iterator-to-stream/node_modules/readable-stream/lib/internal/streams/destroy.js:58:3)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at processTicksAndRejections (node:internal/process/task_queues:83:21)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]: }
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]: 2021-12-01T12:09:48.673Z xo:xo-server ERROR uncaught exception {
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:   error: TypeError: this disposable has already been disposed
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Disposable.dispose (/opt/xen-orchestra/node_modules/promise-toolbox/Disposable.js:35:13)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.<anonymous> (/opt/xen-orchestra/@xen-orchestra/backups/RemoteAdapter.js:526:40)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.emit (node:events:402:35)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.emit (node:domain:475:12)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at Readable.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:118:17)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at endReadableNT (/opt/xen-orchestra/node_modules/async-iterator-to-stream/node_modules/readable-stream/lib/_stream_readable.js:1094:12)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]:       at processTicksAndRejections (node:internal/process/task_queues:83:21)
                                            Dec 01 06:09:48 ubuntuxo xo-server[29198]: }
                                            Dec 01 06:09:49 ubuntuxo xo-server[29198]: 2021-12-01T12:09:49.184Z xo:api WARN dan@xxx | backupNg.importVmBackup(...) [2s] =!> XapiError: VDI_IO_ERROR(Device I/O errors)
                                            
                                            julien-fJ 1 Reply Last reply Reply Quote 0

                                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                            With your input, this post could be even better 💗

                                            Register Login
                                            • First post
                                              Last post