invalid parameter when manually triggering a backup
-
Hi, Everyone.
I encounter a problem when I manually triggered a backup. The backup is a scheduled backup with a compression of zstd. The backup is known working backup because it has successfully ran the backup on the scheduled date. Below is the error message I am getting when run the backup manually:
backupNg.runJob { "id": "618f4813-ea37-405b-978c-6e4568fc7cd8", "schedule": "d81b09f4-645e-4b53-acea-206815603cd7" } { "code": 10, "data": { "errors": [ { "instancePath": "", "schemaPath": "#/required", "keyword": "required", "params": { "missingProperty": "settings" }, "message": "must have required property 'settings'" } ] }, "message": "invalid parameters", "name": "XoError", "stack": "XoError: invalid parameters at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202208311948/packages/xo-common/api-errors.js:26:11) at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202208311948/packages/xo-server/src/xo-mixins/api.mjs:64:20) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202208311948/packages/xo-server/src/xo-mixins/api.mjs:389:19)" }
I tried to interpret the error message, as I understand it is missing required parameters. I don't understand which parameter is missing. Hoping that the community be able to point what I have missed and learn from this.
-
Please update to the latest commit on
master
, rebuild and test again. If it persists, then we'll investigate -
Hi,
As usual for anyone asking for help, if you don't provide anything regarding your XO version, it's hard to assist. Have you read https://xen-orchestra.com/docs/community.html first?
-
My apologies for not providing that information. Here is commit hash: d7f29
-
Please update to the latest commit on
master
, rebuild and test again. If it persists, then we'll investigate -
Will do. Thanks.
-
You are right I should have checked first there is a newer version. Again thank you so much for big help.
-
Does it fix the issue?
-
Apologies for the late reply, yes it did.
-
Perfect, problem solved then!
-
-
-
Yes, thank you so much for the big help.