Backup job fails after restoring XO from Backup - ENOENT: no such file or directory, uv_cwd

[runevn]

I have just restored XO from a backup because I had some challenges after upgrading XO community edition.

However, now my scheduled backup jobs fails all with the following error: ENOENT: no such file or directory, uv_cwd

The full log error:

{
  "data": {
    "mode": "full",
    "reportWhen": "failure"
  },
  "id": "1625253198637",
  "jobId": "7c1a955d-40c5-4f84-8b1f-573911427001",
  "jobName": "Weekly Backup",
  "message": "backup",
  "scheduleId": "0bd28888-e278-4628-87e1-b0ba58c6f892",
  "start": 1625253198637,
  "status": "failure",
  "tasks": [
    {
      "data": {
        "type": "remote",
        "id": "7847ae41-54e0-4534-9790-a9c57ca6744a"
      },
      "id": "1625253199171",
      "message": "get remote adapter",
      "start": 1625253199171,
      "status": "failure",
      "end": 1625253199171,
      "result": {
        "errno": -2,
        "code": "ENOENT",
        "syscall": "uv_cwd",
        "message": "ENOENT: no such file or directory, uv_cwd",
        "name": "Error",
        "stack": "Error: ENOENT: no such file or directory, uv_cwd\n    at process.wrappedCwd (internal/bootstrap/switches/does_own_process_state.js:130:28)\n    at process.cwd (/home/mex/xen-orchestra/node_modules/graceful-fs/polyfills.js:10:19)\n    at handleArguments (/home/mex/xen-orchestra/node_modules/execa/index.js:39:36)\n    at NfsHandler.execa [as _execa] (/home/mex/xen-orchestra/node_modules/execa/index.js:75:17)\n    at NfsHandler._sync (/home/mex/xen-orchestra/@xen-orchestra/fs/dist/_mount.js:83:18)"
      }
    }
  ],
  "end": 1625253199172
}

As mentioned I restored the XO VM from a backup. I also made a snapshot that I also reverted back to. My Backup remote is working and tested.

Any help is highly appreciated.

[runevn]

Does anyone know if this is related to node or is it related to reverting the XO back to a previous snapshot?

[olivierlambert]

Smells like a rebuild problem. Try to follow the official doc on a fresh git clone and try again

[runevn]

@olivierlambert Thanks.