@DustinB3403 said in Windows 10 Defender Won't Start After Malware or Ransomware:
Also I highly recommend Cybereason RansomFree
Product is no longer developed or supported.
@DustinB3403 said in Windows 10 Defender Won't Start After Malware or Ransomware:
Also I highly recommend Cybereason RansomFree
Product is no longer developed or supported.
@scottalanmiller You did nothing but jump to an illogical conclusion. I believe it's more likely that this was a user error. We don't know because the OP hasn't provided enough details. What email address did he use? Did the email truly bounce or was it rejected for some other reason?
Do you always assume that a company is out of business when you read an unverified claim that an email bounced? Do you always jump to wild conclusions before performing any due diligence? I would hope not... because that isn't very professional.
@JaredBusch Yes... just trying to nicely call him out on his "bad behavior".
@scottalanmiller said in Building a Mail Server:
Maybe they went out of business?
Why jump to such an extreme conclusion? :frowning_face: Perhaps @Curtis used an incorrect email address.
I just emailed them at [email protected] and received an immediate response.
They also offer support via Slack.
How many users? I think the Veeam solution is free up to 10.
@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:
We could likely create a check for 1 cpu and raise a flag for it with an optional "continue" during the installation script.
Not sure if it's worthwhile.
Not worth the effort IMO. You could add a comment to the troubleshooting section.
@DustinB3403 Yes, it was a bug in Jest library, which has since been fixed. They bumped the version requirements yesterday, so a rebuild should now require v24 (I think) or greater.
@bnrstnr Actually, that should be fixed now as well.
@shwetkprabhat I recently updated the script to deal with the expired repo key. Let us know if you run into any issues when you do update. :smiling_face:
@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?