Team - XO Backend group | XCP-ng and XO forum

florent

@MajorP93 I am not sure of which branch.
can you switch to https://github.com/vatesfr/xen-orchestra/pull/9725

then

when running this branch :

wait for the memory to fill
find the process running xo ( dist/cli.mjs )
send signal : kill -SIGUSR2
a file is created in `/tmp/xo-server-${process.pid}-${Date.now()}.heapsnapshot`

Note that these exports can contain sensitive data. This will freeze you xo from a few seconds to 2 minutes, and the memory consumption after will be higher after, but this will be very usefull to identify exactly what is leaking

The file will be a few hundred MB

fbeauchamp opened this pull request in vatesfr/xen-orchestra

open Fix(xo-server): TLSSocket memory leak — stoppable + http-server-plus incompatibility #9725

florent

@acebmxer did you enabled NBD on the network ( in the pool view ? ) is it a network accessible by the xo ?

florent

@acebmxer you need to enable NBD on the backup to ensure ti works with qcow2

we 'll check for the progress bar

florent

maybe a good news ?

is completely stable since yesterday's patch

florent

@MajorP93 I think there are multiple issue for memory . Pillow and acebmxer uses proxy , so the backup memory is handled differently

are you using XO from source or a xoa ? would you be ok to export a memory heap ?

florent

that's better but it still grew during the night

(and the process did an aout of memory when I asked for a memory dump)

I reduced the memory allocated to the rest api and will continue monitoring

florent

@ph7

let's call it a day

@acebmxer after 3 hours the consumption was slightly rising, so we also deployed the latest rest api patch which is already on master : https://github.com/vatesfr/xen-orchestra/commit/0fef765ce6b4bc96b28e6af9be3d3dba3fa7dc1e

0

MathieuRA committed to vatesfr/xen-orchestra

fix(rest-api): fix memory-leak on subscription (#9707)

florent

@acebmxer said:

@florent

This is from when patch was applied today.

I am exactly on the same screen, but I won't jinx it and emit a hope before at least a few more hours

florent

@Pilow said:

@florent http 401 error on the pull odd

can you retry ?

florent

@acebmxer thanks to you we have discove a new class of candidates for the fix : the TLS session that stayed behind each connection.

the branch is here https://github.com/vatesfr/xen-orchestra/pull/9725 , as soon as we are done on a QA we will patch your xoa

fbeauchamp opened this pull request in vatesfr/xen-orchestra

Team - XO Backend

Posts

open Fix(xo-server): TLSSocket memory leak — stoppable + http-server-plus incompatibility #9725

open Fix(xo-server): TLSSocket memory leak — stoppable + http-server-plus incompatibility #9725

Member List