Mirror Incremental Bkp - Error Maximum call stack size exceeded
-
bkp_log.txt
Here are the log.My mirror incremental bkp always get stuck with one specific vm.
"result": { "message": "Maximum call stack size exceeded", "name": "RangeError", "stack": "RangeError: Maximum call stack size exceeded\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:418:7)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)\n at getUsedChildChainOrDelete (file:///opt/xo/xo-builds/xen-orchestra-202401192117/@xen-orchestra/backups/_cleanVm.mjs:433:23)" =============
-
Hi,
Can you provide a bit more information on your setup, the XO version you use and such
-
Xen Orchestra commit ec166
XCP-NG 8.2.1 (only one host)
Let me know what specific information you need if I'm missing some.
-
commit
ec1669a32
is almost 3 months old. You can't report an issue without being on the latest commit in our repo, as per our doc:https://xen-orchestra.com/docs/community.html#current-version
Please upgrade/rebuild and if you reproduce, we'll take a look
-
@olivierlambert Perfect, I will work on this and come back to you.
-
@olivierlambert I did the update and I'm getting the same error.
Herer are the log 2024-04-11T11_47_11.366Z - backup NG.txt
Sense my mirror incremental backup take a while to do the copy because of internet speed. I had to do update to another commit this morning. I will retest de backup job but still getting the error on the latest commit from last week.
-
What Node version are you using?
-
@olivierlambert Node v18.20.2
-
@olivierlambert any news on this ? Thank You.
-
Sorry I don't know what's the issue, anyone else can reproduce?