@julien-f Thank you very much I've updated to the latest commit and can confirm the behaviour has stopped, the prompt fix is much appreciated.
Best posts made by AlexQuorum
-
RE: Issues With Audit Log
Latest posts made by AlexQuorum
-
RE: Performance Alerts Fail when Turning on All Running Hosts / All Running VM's etc
@Bastien-Nollet Thank you for your help, purging the config then readding it seemed to fix the problem, appreciate the support.
-
RE: Performance Alerts Fail when Turning on All Running Hosts / All Running VM's etc
@olivierlambert Hi Olivier,
See attached (never realised you could just download these! Would have been handy a few times in the past...)
Apologises for the large size, the full error message was too large so snipped out a load of the UUID's.
plugin.configure { "id": "perf-alert", "configuration": { "hostMonitors": [ { "smartMode": false, "uuids": [ ], "alarmTriggerLevel": 90, "excludeUuids": false } ], "vmMonitors": [ { "uuids": [ "5f7e0255-4946-9399-f3b4-124cf668138e", "6dcfd1b6-f380-a6b5-7307-40be4af070bb", ], "smartMode": true, "alarmTriggerLevel": 90, "alarmTriggerPeriod": 600, "excludeUuids": false }, { "smartMode": false, "variableName": "memoryUsage", "alarmTriggerLevel": 90, "uuids": [ "5f7e0255-4946-9399-f3b4-124cf668138e", "6dcfd1b6-f380-a6b5-7307-40be4af070bb", ], "excludeUuids": false, "alarmTriggerPeriod": 600 } ], "srMonitors": [ { "smartMode": false, "uuids": [ "af7de4c2-9afd-e25e-21c3-adec82597c88", "9fdaeedd-0ffa-221e-aba0-d66637f89492", ], "alarmTriggerLevel": 90, "excludeUuids": false } ], "toEmails": [ "blanked@blank" ], "baseUrl": "http://xoa.blank.com" } } { "code": 10, "data": { "errors": [ { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/0/not", "keyword": "not", "params": {}, "message": "must NOT be valid" }, { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf/1/const", "keyword": "const", "params": { "allowedValue": false }, "message": "must be equal to constant" }, { "instancePath": "/vmMonitors/0/smartMode", "schemaPath": "#/properties/vmMonitors/items/oneOf/0/properties/smartMode/anyOf", "keyword": "anyOf", "params": {}, "message": "must match a schema in anyOf" }, { "instancePath": "/vmMonitors/0/uuids", "schemaPath": "#/properties/vmMonitors/items/oneOf/1/properties/uuids/not", "keyword": "not", "params": {}, "message": "must NOT be valid" }, { "instancePath": "/vmMonitors/0/excludeUuids", "schemaPath": "#/properties/vmMonitors/items/oneOf/2/properties/excludeUuids/const", "keyword": "const", "params": { "allowedValue": true }, "message": "must be equal to constant" }, { "instancePath": "/vmMonitors/0", "schemaPath": "#/properties/vmMonitors/items/oneOf", "keyword": "oneOf", "params": { "passingSchemas": null }, "message": "must match exactly one schema in oneOf" } ] }, "message": "invalid parameters", "name": "XoError", "stack": "XoError: invalid parameters at invalidParameters (/opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-common/api-errors.js:26:11) at default._configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/plugins.mjs:175:13) at default.configurePlugin (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/plugins.mjs:199:16) at Xo.configure (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/api/plugin.mjs:12:3) at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202505011024/@vates/task/index.js:175:22) at Task.run (/opt/xo/xo-builds/xen-orchestra-202505011024/@vates/task/index.js:159:20) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202505011024/packages/xo-server/src/xo-mixins/api.mjs:469:18)" }
-
Performance Alerts Fail when Turning on All Running Hosts / All Running VM's etc
Hi All,
Just configured performance alerts and I wanted only my running VM's to be selected so I added all my infrastructure and ticked:
All Running Hosts
All Running VM's
All SR'sI then got an error:
If I untick, all Running Hosts, All Running VM's or All Running SR's the alerts work fine I just get an email with Errors when it scans the offline VM's?
Any Ideas? There was a much bigger piece of JSON as well in an error message above it but I cant seem to find that it was mainly saying bad parameters.
-
RE: Audit Log being Filled with API calls
@Danp Thank you, I've updated to latest build and seems to have sorted it.
-
Audit Log being Filled with API calls
HI There,
I raised this before but for a different call but the audit log is being spammed by api calls for:
host.getMdadmHealthIdeally this should be excluded from being logged as it makes the audit log useless due to how often this is being called.
Thanks for the hard work on XOA either way guys!
Thanks,
Alex -
RE: Commit Number Not Updating?
@Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.
-
RE: Commit Number Not Updating?
@Danp I just tried doing the web package but it's not made any difference it's not a big deal as I know the actual packages are getting updated but just something I noticed and wanted to share. Makes sense if no commits to the XO-WEB service have been made as you say.
-
Commit Number Not Updating?
Hi Everyone,
Just recently updated to the latest commit and noticed the commit number in XOA hasn't changed:
If I go to about I see the below:
I thought my script may have just failed so I reran it but I'm on the (as of writing) current commit:
Any ideas, is this just broken? I restarted the service manually just to be sure.
-
RE: Issues With Audit Log
@julien-f Thank you very much I've updated to the latest commit and can confirm the behaviour has stopped, the prompt fix is much appreciated.
-
RE: Issues With Audit Log
@peder Hi Peder,
Yes it returns 2048 and I also ran the reset XAPI command (the hosts have been physically rebooted since I did it as well).
The little error icon warning about having a short pubkey is also gone since I updated the certificates.