@MajorP93 said in backup mail report says INTERRUPTED but it's not ?:
Hey,
sadly issue seems to still exist...
[image: 1770121082042-bc57641e-1f02-4f0a-845e-88f59493048c-grafik.png]
[image: 1770121095604-42e53002-147e-4633-a368-dbfe3389174a-grafik.png]
[image: 1770121110651-117b793a-80f6-495d-bfcd-4fd95f787773-grafik.png]
I had 3 backup jobs running at the same time, all of them went into status "interrupted" at the exact same timestamp without me doing anything.
Xen Orchestra did not crash, XO VM has enough RAM, no OOM errors in log or similar.
Interestingly the XO VM seems to still send data to the backup remotes even though the jobs show status interrupted.
This exact same issue happened 1 more time in the past but I thought maybe it is only a one-time-hiccup which is why I did not report it here at that point.
Issue first occurred somewhere around the release of XO6, before the XO6 I never had this kind of issue.
Best regards
//EDIT:
maybe to add some relevant info here. I am using XO from sources on Debian 13, NodeJS 24,
Commit fa110ed9c92acf03447f5ee3f309ef6861a4a0d4 ("feat: release 6.1.0").
//EDIT2: Oh I just read in the initial post of this thread that on Pilow's end XO GUI reported success for the backup tasks but the emails indicated otherwise.
In my case the tasks also have status "interrupted" in XO GUI (and in the emails aswell as shown via screenshots).
//EDIT3: I checked Xen Orchestra logs at the timestamp the backup jobs went into "interrupted" status, please find the log file attached below.
xo-log.txt
Based on the log file it looks like the Node JS process went OOM?
This is really strange as my XO VM has quite a lot of resources (8 vCPU, 10GB RAM). I checked in htop on the XO VM and it never went above 5GB during backups...
It may be due to RSS memory requirements suddenly spiking, for NodeJS when it goes under load, running Xen Orchestra and backup operations (depending on where used can be particularly heavy).
@bastien-nollet Maybe worth looking into memory loads, for the NodeJS process when running heavy operations, for Xen Orchestra. Long term maybe necessary to switch what’s used to run the code, contribute fixes, optimisations and/or switch from NodeJS to something else.
