XO (from source): backup error (to Wasabi)

Danp

@fatek Check the output from journalctl --

journalctl -u xo-server -f -n 50

fatek

journalctl does not return any entries.

Danp

@fatek Try running it as sudo.

fatek

@Danp I did try as sudo... still no output.

olivierlambert

In the failed backup log, you have a button to download the whole message.

fatek

@olivierlambert
Since "show logs" does not generate any logs, there is no log to download?

olivierlambert

I'm not sure to understand, at which point this error appears?

fatek

The error happens when you click on the Create button in Backup.

olivierlambert

Okay, can you reproduce on XOA latest?

geogak

Having the Same issue, not in logs same error.

When creating the backup I get the error

Link to screen recording of process to make error occur
https://youtu.be/mPqZD-Rx_Ao

Browser Information

Microsoft Edge for Business
Learn more about Microsoft Edge for Business
Version 128.0.2739.79 (Official build) (64-bit)

olivierlambert

@geogak you showed it with XO from the sources, I was asking to see if you have the issue with XOA "latest" channel. Don't mix XO from the sources and XOA. See https://xen-orchestra.com/docs/installation.html for more details.

geogak

@olivierlambert Ah, very well slight oversight on my part. Works as expected in XOA. I made a scheduled backup there no issue just now.

Lhoust

Yesterday I was receiving the same Error Message: XO from Sources with TrueNAS CORE as my Remote [Xen Orchestra, commit 63a88 --- Master, commit 21bd7].

Log also Empty...

NOTE: Yesterday my XCP-ng 8.3 RC2 had stopped responding, therefore had to reinstall, restoring the VMs and XO Config from a August 30th Backups, if that might be relevant?

Backups are a Paid Feature, therefore I am unable to verify whether Backups work under XO...

olivierlambert

@Lhoust you can always trigger a trial and test on XOA Latest. If you already had a trial, I'll be happy to renew it.

geogak

@Lhoust try updating to the latest commit, it looks like it was fixed in b62e803.

Here is the github link if youre intrested in then change (I am)
https://github.com/vatesfr/xen-orchestra/commit/b62e8035fca4e8cefcb2d1465d585342c720b45d#diff-7c35aaf9805ed05fd9c00b9a5ab3ac8a82f479d03331f0bc771002e302763a39R275

0

MelissaFrncJrg committed to vatesfr/xen-orchestra

fix(xo-web/backup): fix `r[''] is undefined` when creating a backup job

Introduced by 8a9a67c
Fixes #7990

fatek

Thanks to the Vates team for the fix.

Lhoust

@geogak said in XO (from source): backup error (to Wasabi):

@Lhoust try updating to the latest commit, it looks like it was fixed in b62e803.

Here is the github link if youre intrested in then change (I am)
https://github.com/vatesfr/xen-orchestra/commit/b62e8035fca4e8cefcb2d1465d585342c720b45d#diff-7c35aaf9805ed05fd9c00b9a5ab3ac8a82f479d03331f0bc771002e302763a39R275

Yesterday with Xen Orchestra, commit 63a88: I was receiving the Error Message when either attempting to Modify my "Restored" Backup Jobs or trying to re-Create New Backup Jobs

Rolling back to my previous builds from August 30: Xen Orchestra, commit f1780
September 9: Xen Orchestra, commit 6c8d4
and running today's "Current" build Xen Orchestra, commit 21bd7

I have been able to re-Create (and Run) my "Broken" Restored Backup Jobs (which I had deleted yesterday)!

olivierlambert

So we can consider this issue fixed. Thanks everybody for your feedback!

Lhoust

@olivierlambert said in XO (from source): backup error (to Wasabi):

@Lhoust you can always trigger a trial and test on XOA Latest. If you already had a trial, I'll be happy to renew it.

For me Today's XO Build from Sources [Xen Orchestra, commit 21bd7] is working correctly, therefore I have been able move past yesterday's problem and update the Backups of all VMs...

You have already been quite generous and provided me with Two Trials...
If it would be of any benefit to Vates, I would be willing for a Third XOA Trail...

Although for me it appears Vates has already fixed this bug with [Xen Orchestra, commit 21bd7], therefore I should be fine...

olivierlambert

If you need another trial, no problem. To me, the problem is not in XOA (the broken commit was done after the monthly release) and fixed today, so it means it would be never shipped in XOA.