@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
Can you create an issue on GH?
I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
Can you create an issue on GH?
I can. Not sure if I will. :face_with_stuck-out_tongue_closed_eyes:
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
These don't appear to be the same issues to me.
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 said in Xen Orchestra - Community Edition - Installing with Yarn:
@notverypunny there is a GH issue open for this already.
Link?
@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
@DustinB3403 I'm only using Delta backups, so that's the one that failed for me. I have not opened an issue on GH because I wasn't sure if this was something that was impacting everyone or just me.
I did start a thread on their forum.
FYI, my backups started failing under 5.33 and I had to revert to the prior version. Let us know if you run into any issues.
@JaredBusch said in Metered SIP calling:
@Danp that is not what it says. So I cannot.
Ok... so maybe I'm interpreting it incorrectly. What is incorrect about the following analysis?
In May, they used 9850 minutes (5000 base + 4850 overage). In July, their usage jumped to over 21,000 minutes and then has slowly declined to the pre-SIP levels.
@JaredBusch Can you explain why their usage doubled from May to July, but then has slowly returned to their normal levels?
Do they have a plan to replace this outdated tech with something current?
Must just be a coincidence that it occurred on the same day that pot became legal. 
From here --
the blocklist sources are no longer whitelisted by default
@wrx7m said in Looking at New Virtual Host Servers (ESXi):
SMB with around 25 VMs and 8TB of data . Currently have two R720XDs with OBR10 of 3.5" 7200 RPM NLSAS drives and two sockets with 128GB of RAM. I want to at least double the capabilities/capacities.
At what capacity are you currently operating? Do you need more RAM, storage, cores, or all of the above? 
@nerdydad said in Outlook 2016 Export to PST Missing a Lot of Data:
Install Veeam's O365v2 backup to a repository. Free for up to 10 users
I wasn't aware that they had a free options. Thanks for bringing this to my attention!
This issue is now resolved. I had to issue the command git checkout master before the standard upgrade process would work again.
JIC anyone needs help to get back up and running, this worked for me --
git checkout 0ad6c073ee1538887e13ebec7d3420fcace4d86e
yarn; yarn build
sudo systemctl restart xo-server.service
My production VM kept working as expected until I logged out. That's when I first encountered the issue with logging in.