Unable to export OVA

olivierlambert

Yesterday, we found a bug due to a breaking change in NodeJS (in Node 18) which is fixed now in our master branch. If you still have the issue in latest, please open a ticket with a support tunnel so we can backport the fix to your XOA.

There's some chances it's related to your current issue.

atig

@olivierlambert Thank you for the update. Just a quick question, switching to latest (master branch) will we be pulling lot of unstable features that is being worked upon?

olivierlambert

So in XOA, there's no equivalent to latest commit of master. In short:

XOA got 2 release channel: stable and latest. Latest is "just" our monthly release available after our internal QA. Stable is the release from a month ago. Both are tested.
On the sources, there's no QA possible since we only test in a controlled environment (which is the point of XOA). And latest commit from master is only available on the sources.

However if you open a ticket with a support tunnel, we can patch your XOA in live for you, so you can test it and validate the fix

atig

@olivierlambert Okay thanks. Let me try the latest channel, and will bother support if I am still stuck.

atig

This post is deleted!

olivierlambert

Please do so, I think you will still have the issue for any export longer than 5 minutes, and if it's the case, create the ticket so we can try the fix on your XOA

atig

@olivierlambert Spot on. That is the case. Basically, I was able to go past my previous number of 180mb - where there is total disconnection and I got "Failed - Network Error".

Now, I was able to reach to about 235 MB in download but then, XOA became completely unresponsive although there was no "Failed - Network Error"
The export slowed down to a snail's pace and I am on a network is 10Gb network with XOA being a single hop away.

I waited for 15-20 minutes and finally the XOA was completely unresponsive but the upload still seemed to be going but eventually I had to cancel it as I couldn't access anything at all.

Danp

FWIW, I just tried an OVA export using the latest sources and it failed because the OS killed the process due to low memory (XO VM has 4GB of memory).

This is what appeared in the log --

Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: A process of this unit has been killed by the OOM killer.
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Main process exited, code=killed, status=9/KILL
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Failed with result 'oom-kill'.
Jan 12 08:41:54 ubuntuxo systemd[1]: xo-server.service: Consumed 8min 37.581s CPU time.
Jan 12 08:41:55 ubuntuxo systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 1.
Jan 12 08:41:55 ubuntuxo systemd[1]: Stopped XO Server.
Jan 12 08:41:55 ubuntuxo systemd[1]: xo-server.service: Consumed 8min 37.581s CPU time.
Jan 12 08:41:55 ubuntuxo systemd[1]: Started XO Server.
Jan 12 08:42:00 ubuntuxo xo-server[124628]: 2023-01-12T14:42:00.761Z xo:main INFO Configuration loaded.

There plenty of free memory prior to the export starting --

# free -h
               total        used        free      shared  buff/cache   available
Mem:           3.8Gi       580Mi       3.0Gi       2.0Mi       252Mi       3.0Gi

olivierlambert

atig

@Danp Which log is this?

Danp

@atig It's the output from the following command, which reads from the systemd logs in real time --
journalctl -u xo-server -f -n 50

atig

@olivierlambert seems like there is some issue - how should I proceed?

olivierlambert

We need more data to be sure it's a bug. We also did some fixes about a 5 minute timeout in NodeJS last week, so please -as asked in the doc- to rebuild everything from latest commit on master

atig

@olivierlambert Can I please confirm, do you mean upgrade the XOA from the latest channel?

olivierlambert

If you are on XOA, then open a ticket with a support tunnel so we can put you the fix so you can test again

cgrd_de

I think I have exactly the same issue here.
I saw, that xoa was using extremely much RAM memory and then finally crashed, after the disk was exported. wget showed me the message "Error decoding the received TLS packet" during the download. So I increased RAM of the XOA VM up to 22 GB, but still the same issue.

When I read, that there was some NodeJS under the hood, I had the idea, that it could be related to the name of the VM, which I was trying to export. My VM had the name "[XOA Export] Somename" because it had been previously exported from another pool and imported here.

After changing the name into just "Somename" I could successfully export in OVA format.

Maybe this helps you to find and fix the bug?

olivierlambert

Hi,

As usual, the same question: are you using XOA or XO from the sources, and which version exactly?

And thanks for the feedback

cgrd_de

@olivierlambert
I am using xoa
xo-server 5.107.3 Xen Orchestra server
xo-web 5.108.0 Xen Orchestra web client

olivierlambert

Anyone else with the issue could confirm by having a name without non-alphanum char is working?

Danp

@olivierlambert No. I am unable to export a VM without non-alphanum chars to OVA. I encountered the same issue with OOM Killer as shown above. Not sure if this helps, but XO stats for the XO VM showed RAM usage at around 1GB out of 4GB for the duration of the attempted export.