Problems building from source

olivierlambert

Okay keep us posted

Danp

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

commit 4dc4b635f2f44dbde02d2671bcfd5cecb1b3df4f
2021-10-29 15:50:42 +0200

olivierlambert

Adding @julien-f in the loop.

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

Danp

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

olivierlambert

@julien-f will come back here when he can

julien-f

@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?

Danp

This post is deleted!

Danp

@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-f

@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.

Danp

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

julien-f

@danp Great, thanks for your help

Danp

@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-f

@danp I'm on it

Danp

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

julien-f

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

Danp

@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-f

@danp Should be fixed as well!

Danp

@julien-f Disposable issue is resolved, but still getting VDI_IO_ERROR error that didn't occur in prior release --

 "message": "VDI_IO_ERROR(Device I/O errors)",
  "name": "XapiError",
  "stack": "XapiError: VDI_IO_ERROR(Device I/O errors)
    at Function.wrap (/opt/xen-orchestra/packages/xen-api/src/_XapiError.js:16:12)
    at _default (/opt/xen-orchestra/packages/xen-api/src/_getTaskResult.js:11:29)
    at Xapi._addRecordToCache (/opt/xen-orchestra/packages/xen-api/src/index.js:898:24)
    at forEach (/opt/xen-orchestra/packages/xen-api/src/index.js:932:14)
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:922:12)
    at Xapi._watchEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:1087:14)"

Full log attached
log.txt

olivierlambert

Weird, why are we seeing VMDK format in the log? @Danp what kind of backup are you restoring? Delta?

Danp

@olivierlambert Yes, it's a delta backup. I think the VMDK is just a byproduct from importing that disk. Here's another log for review.

2021-12-01T12_50_06.933Z - XO.txt