worker exited with code 1 and signal null

utopianfish

Hi Have a 2 node cluster with local ssd storage and have one host as master the other is used as a replication host.. they are directlymconnected via 10gb nics.. has been working perfectly the last few days since setting it up but last night i'm getting the above error.... no idea how to troubleshoot this... i'm on Xen Orchestra, commit c3905...hosts did 29 patch updates last night...

cheers

olivierlambert

Do you have the entire log?

utopianfish

@olivierlambert

{
  "data": {
    "mode": "delta",
    "reportWhen": "always"
  },
  "id": "1756806348037",
  "jobId": "184411ba-b5db-41b4-8915-9b35d731ac77",
  "jobName": "Replication to HOST147",
  "message": "backup",
  "scheduleId": "28eb38ca-41b4-403e-b34e-92015d51207c",
  "start": 1756806348037,
  "status": "failure",
  "end": 1756806348278,
  "result": {
    "message": "worker exited with code 1 and signal null",
    "name": "Error",
    "stack": "Error: worker exited with code 1 and signal null\n    at ChildProcess.<anonymous> (file:///opt/xo/xo-builds/xen-orchestra-202509011824/@xen-orchestra/backups/runBackupWorker.mjs:24:48)\n    at ChildProcess.emit (node:events:519:28)\n    at ChildProcess.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202509011824/@xen-orchestra/log/configure.js:52:17)\n    at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)\n    at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }
}

olivierlambert

Do you have enough memory in your XO? It's hard to answer because it's from the sources.

Double check the resources available.

utopianfish

@olivierlambert 4gb mem on XO on debian VM.... host have 64 gb each... is it worth bumping it up and giving it a reboot and try again.. as i say was working great for the last few days....

olivierlambert

4GiB for XO might be enough, but it seems a worker is crashing or failing. I am not sure I've already seen that message myself. I will ask around.

utopianfish

ran it thru chatgpt.. and got this.. Perfect — now we have the real error.

The crash is because libfuse.so.2 is missing. XO (specifically the fuse-native module) depends on the FUSE library, but Debian 13 only ships libfuse3, not the older libfuse2 that XO wants.

i did bump the mem up to 8 as well and the repliaction job is now running...

olivierlambert

Libfuse is not used at all during replication, so I'm afraid ChatGPT is hallucinating.

john.c

Sometimes it when asking questions as well as hallucinating ChatGPT, can respond with results based on old versions (not updated for an up to date code base).

So if any past in development or experimental code branch, had its code and was mistakenly released. Then the mistake was found and fixed, it can have found its way into the training data set.

Can also be an example of training data set poisoning, forcing it to give misleading or mistaken responses, due to it hallucinating as a result.