Xen Orchestra - Community Edition - Installing with Yarn

dbeato

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@dbeato said in Xen Orchestra - Community Edition - Installing with Yarn:

@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

Can you provide a link?

It's not like their forum is so busy that you couldn't find it on your own. :face_with_stuck-out_tongue:

https://xen-orchestra.com/forum/topic/1244/backups-failing-after-recent-update

Having that issue for a while.

Which issue, the backup issue or their forums activity? If the forum, I think the biggest issue is they have two distinct platforms.

One for XO and another for XCP-ng. They need to consolidate their platforms into one and drive all of that traffic to the same place.

Lol both, but I am more interested on the backup issue. I posted there now.

DustinB3403

I've specifically made duplicate posts on both of their forms 1 and 2.

Not yet has anyone seemed to comment but I feel like they should know this issue exists and is a big issue as an ecosystem.

notverypunny

So backups seem to be an issue on 5.33

Digging a bit deeper to see what's what, but the web interface shows the following:

Error: ENOENT: no such file or directory, open '/var/nfsmounts/--nfsServerMountName--/xo-vm-backups/ff56004a-8730-52cd-195a-27af82106e30/vdis/d8b24ab1-2bdf-484d-bd59-ea23bc4d2e9d/2c4dcf82-910a-4d8b-8657-f2ff3e413665/20190112T060003Z.vhd'

DustinB3403

@notverypunny there is a GH issue open for this already.

DustinB3403

@notverypunny also it's an upstream issue.

notverypunny

@DustinB3403 Do you know if there's anything to be done apart from rolling back? I've got retention set at 3 days and it's looking for the backup from 4 days ago....

Danp

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@notverypunny there is a GH issue open for this already.

Link?

DustinB3403

@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@notverypunny there is a GH issue open for this already.

Link?

Correction, no GH issue, just your post @Danp

Someone should probably make an issue.

notverypunny

@Danp @DustinB3403 Any easy way to roll back with the updater script?

DustinB3403

@notverypunny The easy thing would be to roll back with a snapshot.

notverypunny

@DustinB3403 Wishful thinking.... I had already deleted the snapshot by the time that @Danp flagged the potential problem with backups

DustinB3403

@notverypunny OKay, no worries.

Export your config file. ~~Build a new XO installation and import the config file.~~ Actually no. That won't work. God im tired.

Just restore your VM from 4 days ago. Assuming you are backing up XO.

It's a 10 minute process.

DustinB3403

Although to ask the question, why haven't you made a GH issue?

Could be affecting way more people than has been noticed here (and on the XO forums).

DustinB3403

@notverypunny and @Danp please provide any reports to this GH issue. https://github.com/vatesfr/xen-orchestra/issues/3873

DustinB3403

Problem solved.

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

Please look at the information posted here for an answer.

notverypunny

@DustinB3403 The github issue was closed out before I could interject... I added to the thread and they seem to be saying that it might be something else... still going to try creating a new job, might be simpler than redoing the XO install

DustinB3403

@notverypunny Post details here.

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

notverypunny

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@notverypunny Post details here.

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

Done.... I'll be interested to see if there's a solution beyond re-creating the jobs.... not the end of the world, but not exactly elegant

Danp

I had to roll back to 5.32, because I was still receiving errors after recreating the job. Here's one example --

Jan 17 14:36:31 ubuntu xo-server[19796]: 2019-01-17T20:36:31.133Z - xo:xapi - [DEBUG] exporting VDI xxxxxxx
Jan 17 14:36:31 ubuntu xo-server[19796]: 2019-01-17T20:36:31.349Z - xo:xo-server - [WARN] possibly unhandled rejection
Jan 17 14:36:31 ubuntu xo-server[19796]: { error:
Jan 17 14:36:31 ubuntu xo-server[19796]:    { TypeError: Cannot read property 'join' of undefined
Jan 17 14:36:31 ubuntu xo-server[19796]:     at new XapiError (/opt/xen-orchestra/packages/xen-api/src/index.js:92:28)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at wrapError (/opt/xen-orchestra/packages/xen-api/src/index.js:113:9)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at _call.catch.error (/opt/xen-orchestra/packages/xen-api/src/index.js:1129:18)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at tryCatcher (/opt/xen-orchestra/node_modules/bluebird/js/release/util.js:16:23)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Promise._settlePromiseFromHandler (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:512:31)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Promise._settlePromise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:569:18)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Promise._settlePromise0 (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:614:10)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Promise._settlePromises (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:690:18)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at _drainQueueStep (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:138:12)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at _drainQueue (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:131:9)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Async._drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:147:5)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at Immediate.Async.drainQueues (/opt/xen-orchestra/node_modules/bluebird/js/release/async.js:17:14)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at runCallback (timers.js:810:20)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at tryOnImmediate (timers.js:768:5)
Jan 17 14:36:31 ubuntu xo-server[19796]:     at processImmediate [as _immediateCallback] (timers.js:745:5)
Jan 17 14:36:31 ubuntu xo-server[19796]:      [Symbol(originalCallSite)]:
Jan 17 14:36:31 ubuntu xo-server[19796]:       [ CallSite {},
Jan 17 14:36:31 ubuntu xo-server[19796]:         CallSite {},
Jan 17 14:36:31 ubuntu xo-server[19796]:         CallSite {} ],
Jan 17 14:36:31 ubuntu xo-server[19796]:      [Symbol(mutatedCallSite)]:
Jan 17 14:36:31 ubuntu xo-server[19796]:       [ [Object],
Jan 17 14:36:31 ubuntu xo-server[19796]:         [Object],
Jan 17 14:36:31 ubuntu xo-server[19796]:         CallSite {},
Jan 17 14:36:31 ubuntu xo-server[19796]:         CallSite {} ] } }

Retesting now with 5.32

DustinB3403

@Danp Julien thinks he knows what it is and plans to fix it tomorrow if you can wait.

Or keep a copy of this installation around for testing.