Bizarre Error during backup process (from the sources, 20.04)

xo-g

After a few other issues, I'm now running as root, I've enjoyed the confusion of watching my xcp-ng controller try and unmount my / partition and I'm trying to get backups working.

No errors in the command line:

2021-02-19T11:50:26.905Z xo:main INFO + WebSocket connection (::ffff:172.16.32.167)
2021-02-19T11:50:55.654Z xo:xapi DEBUG Snapshotting VM wpwtj as [XO Backup barber backup test] wpwtj
2021-02-19T11:51:03.693Z xo:xapi DEBUG exporting VDI wpwtj

but the web interface gives the following:

Error: The "path" argument must be of type string. Received an instance of IncomingMessage

This is node 12 straight from the nodesource repos, yarn run v1.22.10 straight from their repos, and latest XO from the vates repos - on Ubuntu 12.04 with latest patches. Hosts are running XCP-ng 8.2LTS also with the latest patches.

I've been accessing XO through an nginx reverse proxy (nginx 18, straight from their repos), but in order to reduce possible failure points I'm now connecting directly to the xo web interface with no tls, running on port 2080. The backup is the first of a backup of type Delta, VM manually selected, to an NFS remote. The same remote is working fine for a metadata backup.

As an experiment, I tried switching from a Delta Backup to a Backup, which changed the error to:

Error: The "path" argument must be of type string. Received an instance of Transform

Any ideas?

Many thanks to all!

carlosfrederico

I am also having this problem

Help us please .

olivierlambert

Hi,

Before opening a new thread, don't forget to take a look at XO Github repo in the existing issues.

It's already reported here: https://github.com/vatesfr/xen-orchestra/issues/5588

@julien-f even suggested a workaround.

Note that it can happen sometimes on master (despite we review all PR before merging on it), on the sources you won't have the level of QA you can enjoy on XOA. Which is the point, if you are using it into production, and it's "urgent", you'd better have support guys

bogikornel created this issue in vatesfr/xen-orchestra

closed Backup job failed #5588

xo-g

@olivierlambert Thanks Olivier,

That report wasn't up yet when I ran into this yesterday, and I confess to not having looked this morning since I continued.

My assumptions were:

It's 99% likely to be my config and not a code issue.
Github support requests for source builds tend to be told to use the community forum instead

Hence posting here. Wasn't expecting a staff response, but appreciate it! I'll have a look at reverting to the suggested commit as @julien-f proposes. Commercial XOA isn't in the budget, but I appreciate the suggestion for that, too!

olivierlambert

No worries, just leaving the message for others too It wasn't criticism

carlosfrederico

@olivierlambert said in Bizarre Error during backup process (from the sources, 20.04):

https://github.com/vatesfr/xen-orchestra/issues/5588

Thanks @olivierlambert and @julien-f !

I use the script https://github.com/Jarli01/xenorchestra_updater , so executing sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -b 350b0c1 solved the problem.

Thanks!

xo-g

@olivierlambert

Appreciate that! Don't suppose you're up for tagging or branching this commit as a defined release, are you?

But more seriously - I can also confirm that backups now work on my installation by reverting to commit 350b0c1e3cf600ecb7c75f76daeae93d44a37121.

olivierlambert

No, it's meant like that As a community user, that's a useful contribution you can do to provide feedback when something is broken.

In exchange, you have the whole software for free, and we have a review process so master branch doesn't break a lot. And if it's does, you can rollback to a previous commit to solve it

xo-g

@olivierlambert It's a fair trade.

cyrus104

@carlosfrederico said in Bizarre Error during backup process (from the sources, 20.04):

@olivierlambert said in Bizarre Error during backup process (from the sources, 20.04):

https://github.com/vatesfr/xen-orchestra/issues/5588

Thanks @olivierlambert and @julien-f !

I use the script https://github.com/Jarli01/xenorchestra_updater , so executing sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -b 350b0c1 solved the problem.

Thanks!

Thank you all too. I ran into this issue last night, found this, changed to the alternative branch and boom it's working now.

When a merge makes it's way into XO source, is there a way to highlight this issue so I can move back to mainline?

Thanks again!

olivierlambert

Just subscribe to the Github issue so you'll know when it's closed.

Danp

Yesterday I updated to the latest sources and my backup ran successfully, so it appears that this issue is resolved.

@carlosfrederico You'll need to switch back to the master branch before your normal update routine will work.