That was it you're awesome. You can mark it as solved.
Best posts made by mike.smith
-
RE: New install can't add remote NFS
Latest posts made by mike.smith
-
New install some people can't login
Hello, I did a fresh install to see if it would solve this issue and another but they persist. When a coworker goes to login he gets kicked right back out to the login page. below is the information shown in the console. I did some googling and found mention that it could be because of nodejs and some issues with macos Bigsur and chrome. Not sure how true that is because I am using macOS bigsur with chrome no problem and my boss is as well. However, my coworkers machine and others give the same message. Different browsers cause the same message as well.
2021-02-26T15:23:07.268Z xo:main INFO Setting up / → /home/localtech/xen-orchestra/packages/xo-web/dist 2021-02-26T15:23:18.812Z xo:main INFO + WebSocket connection (::ffff:10.0.57.217) 2021-02-26T15:23:18.978Z xo:xo-server ERROR unhandled error event { error: RangeError: Invalid WebSocket frame: invalid opcode 7 at Receiver.getInfo (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:226:14) at Receiver.startLoop (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:131:22) at Receiver._write (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:78:10) at writeOrBuffer (internal/streams/writable.js:358:12) at Receiver.Writable.write (internal/streams/writable.js:303:10) at Socket.socketOnData (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/websocket.js:900:35) at Socket.apply (events.js:315:20) at Socket.patchedEmit (/home/localtech/xen-orchestra/@xen-orchestra/log/src/configure.js:92:17) at Socket.EventEmitter.emit (domain.js:467:12) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) at Socket.Readable.push (internal/streams/readable.js:223:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) at TCP.callbackTrampoline (internal/async_hooks.js:131:14) { [Symbol(status-code)]: 1002 } } 2021-02-26T15:23:18.980Z xo:main INFO - WebSocket connection (::ffff:10.0.57.217) 2021-02-26T15:23:18.999Z xo:main INFO + WebSocket connection (::ffff:10.0.57.217) 2021-02-26T15:23:19.005Z xo:xo-server ERROR unhandled error event { error: RangeError: Invalid WebSocket frame: invalid opcode 7 at Receiver.getInfo (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:226:14) at Receiver.startLoop (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:131:22) at Receiver._write (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/receiver.js:78:10) at writeOrBuffer (internal/streams/writable.js:358:12) at Receiver.Writable.write (internal/streams/writable.js:303:10) at Socket.socketOnData (/home/localtech/xen-orchestra/packages/xo-server/node_modules/ws/lib/websocket.js:900:35) at Socket.apply (events.js:315:20) at Socket.patchedEmit (/home/localtech/xen-orchestra/@xen-orchestra/log/src/configure.js:92:17) at Socket.EventEmitter.emit (domain.js:467:12) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) at Socket.Readable.push (internal/streams/readable.js:223:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) at TCP.callbackTrampoline (internal/async_hooks.js:131:14) { [Symbol(status-code)]: 1002 } } 2021-02-26T15:23:19.007Z xo:main INFO - WebSocket connection (::ffff:10.0.57.217) 2021-02-26T15:23:30.793Z xo:main INFO + WebSocket connection (::ffff:10.0.57.221) 2021-02-26T15:23:39.430Z xo:main INFO + WebSocket connection (::ffff:10.0.63.129) 2021-02-26T15:23:39.437Z xo:authentification ERROR no such user 6831d1e8-be05-4cdf-9ca1-3e7a48b1499e { error: XoError: no such user 6831d1e8-be05-4cdf-9ca1-3e7a48b1499e at factory (/home/localtech/xen-orchestra/packages/xo-common/src/api-errors.js:21:32) at _default._getUser (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/subjects.js:177:13) at _default.getUser (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/subjects.js:186:19) at _default._authenticateUser (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/authentication.js:117:17) at _default.authenticateUser (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/authentication.js:152:20) at Object.signIn (/home/localtech/xen-orchestra/packages/xo-server/src/api/session.js:10:32) at Api.callApiMethod (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:304:20) { code: 1, data: { id: '6831d1e8-be05-4cdf-9ca1-3e7a48b1499e', type: 'user' } } } 2021-02-26T15:23:39.474Z xo:api WARN (unknown user) | session.signIn(...) [39ms] =!> XoError: invalid credentials 2021-02-26T15:23:39.671Z xo:main INFO - WebSocket connection (::ffff:10.0.63.129
-
RE: New install can't add remote NFS
That was it you're awesome. You can mark it as solved.
-
New install can't add remote NFS
Just finished a fresh install and when I go to add a NFS share I get the following message. I setup the yarn forever-service to run as Root.
remote.test { "id": "911a6d1a-30e0-49cd-9089-a9200a93812d" } { "shortMessage": "Command failed with exit code 32: mount -o vers=3 -t nfs 10.0.2.232:/volume1/NAKIVO_Repository /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d", "command": "mount -o vers=3 -t nfs 10.0.2.232:/volume1/NAKIVO_Repository /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d", "exitCode": 32, "stdout": "", "stderr": "mount: /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.", "failed": true, "timedOut": false, "isCanceled": false, "killed": false, "message": "Command failed with exit code 32: mount -o vers=3 -t nfs 10.0.2.232:/volume1/NAKIVO_Repository /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d mount: /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.", "name": "Error", "stack": "Error: Command failed with exit code 32: mount -o vers=3 -t nfs 10.0.2.232:/volume1/NAKIVO_Repository /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d mount: /run/xo-server/mounts/911a6d1a-30e0-49cd-9089-a9200a93812d: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program. at makeError (/home/localtech/xen-orchestra/node_modules/execa/lib/error.js:59:11) at handlePromise (/home/localtech/xen-orchestra/node_modules/execa/index.js:114:26) at NfsHandler._sync (/home/localtech/xen-orchestra/@xen-orchestra/fs/src/_mount.js:64:7) at NfsHandler.sync (/home/localtech/xen-orchestra/@xen-orchestra/fs/src/abstract.js:316:5) at _class2.getRemoteHandler (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.js:76:9) at _class2.testRemote (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.js:97:11) at Api.callApiMethod (/home/localtech/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:304:20)" }
-
RE: XOCE Yarn Start Error code 1
Again thanks everyone. you can mark this as solved. The step I was missing was the config step.
$ cd packages/xo-server $ mkdir -p ~/.config/xo-server $ cp sample.config.toml ~/.config/xo-server/config.toml
-
RE: XOCE Yarn Start Error code 1
you are right. I had so many tabs open. https://vates.gitbooks.io/xen-orchestra/content/from_the_sources.html is where I got it from. sorry about that.
-
RE: XOCE Yarn Start Error code 1
Looks like I got it working.
the instructions. threw me off$ cd packages/xo-server $ cp sample.config.yaml .xo-server.yaml
There are no .yaml files I instead did .toml and I did not touch the config.toml
-
RE: XOCE Yarn Start Error code 1
Destroyed the VM and started from scratch on Ubuntu 20.04LTS. I am still getting this error.
localtech@xoce:~/xen-orchestra/packages/xo-server$ yarn start yarn run v1.22.10 $ node bin/xo-server app-conf /home/localtech/xen-orchestra/packages/xo-server/config.toml +0ms 2021-02-25T21:03:37.047Z xo:main INFO Configuration loaded. ✖ Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. TypeError: Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. at main (/home/localtech/xen-orchestra/packages/xo-server/src/index.js:691:13) at processTicksAndRejections (internal/process/task_queues.js:93:5) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. localtech@xoce:~/xen-orchestra/packages/xo-server$ localtech@xoce:~/xen-orchestra/packages/xo-server$ node --version v14.16.0
-
RE: XOCE Yarn Start Error code 1
Thanks for working on this. still getting the same error. I removed the entire xen-orchestra folder and pulled down the git repository again. yes, I did yarn then yarn build in the xen-orchestra folder. changed directory to xo-server then copied the sample config to the config.toml. Then ran yarn start
localtech@xoce:~/xen-orchestra/packages/xo-server$ yarn start yarn run v1.22.10 $ node bin/xo-server app-conf /home/localtech/xen-orchestra/packages/xo-server/config.toml +0ms app-conf /home/localtech/.config/xo-server/config.z-auto.json +2ms 2021-02-25T19:34:50.814Z xo:main INFO Configuration loaded. ✖ Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. TypeError: Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. at main (/home/localtech/xen-orchestra/packages/xo-server/src/index.js:691:13) at processTicksAndRejections (internal/process/task_queues.js:93:5) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
-
RE: XOCE Yarn Start Error code 1
Did another pull and now I'm getting a little different error but with the same exit code.
localtech@xoce:~/xen-orchestra/packages/xo-server$ yarn start yarn run v1.22.10 $ node bin/xo-server app-conf /home/localtech/xen-orchestra/packages/xo-server/config.toml +0ms app-conf /home/localtech/.config/xo-server/config.z-auto.json +2ms 2021-02-25T19:05:55.402Z xo:main INFO Configuration loaded. ✖ Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. TypeError: Cannot destructure property 'enabled' of 'config.blockedAtOptions' as it is undefined. at main (/home/localtech/xen-orchestra/packages/xo-server/src/index.js:691:13) at processTicksAndRejections (internal/process/task_queues.js:93:5) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
-
RE: XOCE Yarn Start Error code 1
@danp Same exit code and error with some different stack information.
yarn run v1.22.10 $ node bin/xo-server internal/modules/cjs/loader.js:883 throw err; ^ Error: Cannot find module './dist/configure' Require stack: - /home/localtech/xen-orchestra/@xen-orchestra/log/configure.js - /home/localtech/xen-orchestra/packages/xo-server/bin/xo-server at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15) at Function.Module._load (internal/modules/cjs/loader.js:725:27) at Module.require (internal/modules/cjs/loader.js:952:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/localtech/xen-orchestra/@xen-orchestra/log/configure.js:1:18) at Module._compile (internal/modules/cjs/loader.js:1063:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) at Module.load (internal/modules/cjs/loader.js:928:32) at Function.Module._load (internal/modules/cjs/loader.js:769:14) at Module.require (internal/modules/cjs/loader.js:952:19) at require (internal/modules/cjs/helpers.js:88:18) at Object.<anonymous> (/home/localtech/xen-orchestra/packages/xo-server/bin/xo-server:23:1) at Module._compile (internal/modules/cjs/loader.js:1063:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) at Module.load (internal/modules/cjs/loader.js:928:32) at Function.Module._load (internal/modules/cjs/loader.js:769:14) { code: 'MODULE_NOT_FOUND', requireStack: [ '/home/localtech/xen-orchestra/@xen-orchestra/log/configure.js', '/home/localtech/xen-orchestra/packages/xo-server/bin/xo-server' ] } error Command failed with exit code 1.