backup mail report says INTERRUPTED but it's not ?

[olivierlambert]

can you remind me the Node version you have, that is exhibiting the problem?

[MajorP93]

@olivierlambert Right now I am using Node JS version 20 as I saw that XOA uses that version aswell. I thought it might be best to use all dependencies at the versions that XOA uses.

I was having the issue with backup job "interrupted" status on Node JS 24 aswell as documented in this thread.

Actually since I downgraded to Node 20 total system RAM usage seems to have decreased by a fair bit which can be seen by comparing the 2 screenshots that I posted in this thread. On first screenshot I was using Node 24 und second screenshot Node 20.
Despite that the issue re-occurred after a few days of XO running.

I hope that --max-old-space-size Node parameter as suggested by @pilow solves my issue.
I will report back.

Best regards

[olivierlambert]

Okay weird, so having a very different RAM usage with Node 24 should be checked when we'll update XOA Node version.

[Pilow]

@MajorP93 this was found in the troubleshooting section of the documentation when i tried to optimise my xoa/xoproxies deployments

https://docs.xen-orchestra.com/troubleshooting#memory

[Pilow]

not looking better today. still not crashed.

but before the patches at 48h max, i topped the 8Gb and got the OOM killed process.

[Pilow]

before disruption, I prefer to patch/reboot my XOA
We got to the limit

still some memory leak somewhere guys !

[florent]

@Pilow we are still working on it, but for now we didn't find a solution

[MajorP93]

After implementing the --max-old-space-size Node parameter as recommended by @pilow it took longer time for the VM to hit the issue.
Still: backups went into interrupted status.
Memory leak seems to be still there.
With each subsequent backup run the memory usage rises and rises. After backup run the memory usage does not fully go back to "normal".

After adding the node parameter there was no heap size error on Node anymore since the heap size got increased. The system went into various OOM errors in kernel log (dmesg) despite not all RAM (8GB) being used.

This is what htop looks like with 3 backup jobs running:

[acebmxer]

While working last night i noticed one of my backups/pools did this. Got the email that it was interupted but when i looked the tasks were still running and moving data it untill it porcess all vms in that backup job.

Edit - note my backup job was run via proxy on the specific pool/job.

2026-02-19T03_00_00.028Z - backup NG.txt

Edit 2 - homelab same last backup was interupted.

2026-02-19T05_00_00.011Z - backup NG.txt

[MajorP93]

I wonder if this PR https://github.com/vatesfr/xen-orchestra/pull/9506 aims to solve the issue that was discussed in this thread.
To me it looks like it's the case as the issue seems to be related to RAM used by backup jobs not being freed correctly and the PR seems to add some garbage collection to backup jobs.
I hope that it will fix the issue and if needed I can test a branch.

b-Nollet opened this pull request in vatesfr/xen-orchestra

open Backup tasks gc #9506

[Bastien Nollet]

Hi @MajorP93,

This PR is only about changing the way we delete old logs (linked to a bigger work of making backups use XO tasks instead of their own task system), it won't fix the issue discussed in this topic.

[MajorP93]

Hi @Bastien-Nollet,

oh okay, thanks for clarifying!