@jr-m4 you can export the heap memory of the nodeJS process by doing kill -SIGUSER2 <xoserverpid>
onte that this will increase a lot the memory consumed by the xo process even when its done exporting the memory . This will help us know what xo is doing at the moment
@acebmxer we are far more explicit on the real usage of NBD, paing the way to mark a failed NBD connexion as an error in a few month
also working on a diagnostic tool to be more efficient on the checks
thank you all for your time
@probain the first checkc to do are network one :
is there a default backup network on he pool ? if yes the xo will only look at this network
check if :
fix is here https://github.com/vatesfr/xen-orchestra/pull/10346 , it works on @flakpyro proxies
the root cause is a timing condition between compression buffering data silently and timeout watching any stall connection
@acebmxer can you give me the support tunnel number by chat ? patch is ready
@acebmxer Hi am testing an hypothesis where removing an old library introduced a implicit compression and buffering between the proxy and the how.
Can I provide a branch to test, or can I deploy a fix through a support tunnel ?
@acebmxer Hi, I just checked your infra. It seems there was a connection error on the proxy around 2h ago: "Xen Orchestra Server could not be reached. Please check your connection."
Can you retry a backup whenever it is possible for you?
Edit: for this part, "error": "Having multiple authentication methods is not supported, please choose one"
It is because you are connecting with two connections in parallel (one with a token and one basic).
@tmk Confirmed bug on our side; thanks for the report.
The plugin declared its secret with a random default in the config schema. That expression runs when the module is imported, so every xo-server process computes a different one, and xo-server never writes back the values ajv fills in from schema defaults. So if you copied the secret out of the plugin form without saving the configuration, scraping worked until the next restart, and Prometheus started getting 401s.
Fix is here: https://github.com/vatesfr/xen-orchestra/pull/10290. The random default is gone. The secret is generated once on the first load and saved through the plugin configuration, so it survives a restart. If you already have one saved, it's left alone.
Once it's merged it'll be on master for people building from sources, and it'll reach XOA in the next release.
@pedro_udifar Hi,
Do you still have errors 500 when you are talking about general errors?
|
4
Posts
5
Reputation
|
|
87
Posts
59
Reputation
|
|
70
Posts
30
Reputation
|
