XO Team group | XCP-ng and XO forum

pierrebrunet

@JB @christopher-petzel Thanks for your patience! We are glad it works well!

florent

@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

florent

@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

florent

@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 :

the xo can access network(s) with nbd enabled
the host have an ip on those networks
are you on ipv4 or v6 ?
xo can access the ip of the host on the nbd newtork

pdonias

Hello everyone! We need you!

We're currently designing the XO 6 UI for non-admin users, and some choices are genuinely hard to make. If you'd like to give us your opinion, here's a 30-second survey with 2 questions we couldn't settle ourselves: https://survey.vates.tech/s/cms4nrqb4005wrw01021ru6dy

Thanks!

florent

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

florent

@acebmxer can you give me the support tunnel number by chat ? patch is ready

florent

@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 ?

pierrebrunet

@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).

pierrebrunet

@acebmxer @flakpyro Hi, there was a patch release this morning for a few issues. Can you update your XO and check if it still happen?

XO Team

Posts

Member List