XO Community Edition Update Error - XO-Web
-
My noob is showing - why do we need to do this? What's broken that requires this change?
What's the difference between npm and yarn?
-
@Dashrender said in XO Community Edition Update Error - XO-Web:
My noob is showing - why do we need to do this? What's broken that requires this change?
What's the difference between npm and yarn?
It is now the preferred dependency manager that XO is using. So in an effort to be as close to XOA as possible, we try to use the same solution as they do.
It reduces our troubleshooting if everything is identical.
-
@Dashrender Yarn apparently does a better job to maintaining packages and updating dependencies.
-
@Danp said in XO Community Edition Update Error - XO-Web:
@Dashrender Yarn apparently does a better job to maintaining packages and updating dependencies.
So it was necessary to make a whole new thing, not just fix the old broken thing?
-
It's not a whole new thing. Yarn replaces the command
npm i
which previously handles the dependency installation. -
@Danp said in XO Community Edition Update Error - XO-Web:
It's not a whole new thing. Yarn replaces the command
npm i
which previously handles the dependency installation.But it is new, it's a new thing you have to install. It's not like you just upgraded npm and the new version does what you want, you installed a whole new program to handle this. Which also required you changing their update script to use the new dependency manager.
-
@Dashrender said in XO Community Edition Update Error - XO-Web:
@Danp said in XO Community Edition Update Error - XO-Web:
It's not a whole new thing. Yarn replaces the command
npm i
which previously handles the dependency installation.But it is new, it's a new thing you have to install. It's not like you just upgraded npm and the new version does what you want, you installed a whole new program to handle this. Which also required you changing
theirthe update script to use the new dependency manager.Corrected.
-
xoadmin@ubuntu:/opt/xo-web$ sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_updater/master/xo-update.sh | bash -s -- -f % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1906 100 1906 0 0 4702 0 --:--:-- --:--:-- --:--:-- 4694 Please run as root (sudo bash) xoadmin@ubuntu:/opt/xo-web$ sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_updater/master/xo-update.sh | sudo bash -s -- -f % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1906 100 1906 0 0 5989 0 --:--:-- --:--:-- --:--:-- 5993 Stopping xo-server... Checking xo-server... Current branch next-release Current version v5.6.4 0 updates available Updating from source... No local changes to save Already up-to-date. Clearing directories... Installing... yarn install v0.21.3 [1/4] Resolving packages... success Already up-to-date. $ npm run build > [email protected] prebuild /opt/xo-server > index-modules src/api src/xapi/mixins src/xo-mixins sh: 1: index-modules: not found npm ERR! Linux 4.8.0-39-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build" npm ERR! node v7.2.1 npm ERR! npm v3.10.10 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! [email protected] prebuild: `index-modules src/api src/xapi/mixins src/xo-mixins` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the [email protected] prebuild script 'index-modules src/api src/xapi/mixins src/xo-mixins'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the xo-server package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! index-modules src/api src/xapi/mixins src/xo-mixins npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs xo-server npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls xo-server npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/xo-server/npm-debug.log error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. Updated version v5.6.4 Checking xo-web... Current branch stable Current version v5.6.2 0 updates available Updating from source... Saved working directory and index state WIP on stable: e8d2b32 5.6.2 HEAD is now at e8d2b32 5.6.2 Already up-to-date. Clearing directories... Installing... yarn install v0.21.3 [1/4] Resolving packages... â is-arrayish@^0.2.1 success Already up-to-date. $ npm run build > [email protected] build /opt/xo-web > npm run build-indexes && NODE_ENV=production gulp build > [email protected] build-indexes /opt/xo-web > index-modules --auto src sh: 1: index-modules: not found npm ERR! Linux 4.8.0-39-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build-indexes" npm ERR! node v7.2.1 npm ERR! npm v3.10.10 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! [email protected] build-indexes: `index-modules --auto src` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the [email protected] build-indexes script 'index-modules --auto src'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the xo-web package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! index-modules --auto src npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs xo-web npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls xo-web npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/xo-web/npm-debug.log npm ERR! Linux 4.8.0-39-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build" npm ERR! node v7.2.1 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! [email protected] build: `npm run build-indexes && NODE_ENV=production gulp build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] build script 'npm run build-indexes && NODE_ENV=production gulp build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the xo-web package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run build-indexes && NODE_ENV=production gulp build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs xo-web npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls xo-web npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/xo-web/npm-debug.log error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. Updated version v5.6.2 Restarting xo-server...
-
@DustinB3403 said in XO Community Edition Update Error - XO-Web:
@Dashrender said in XO Community Edition Update Error - XO-Web:
@Danp said in XO Community Edition Update Error - XO-Web:
It's not a whole new thing. Yarn replaces the command
npm i
which previously handles the dependency installation.But it is new, it's a new thing you have to install. It's not like you just upgraded npm and the new version does what you want, you installed a whole new program to handle this. Which also required you changing
theirthe update script to use the new dependency manager.Corrected.
oh yeah.. my bad.
-
@Dashrender said in XO Community Edition Update Error - XO-Web:
@DustinB3403 said in XO Community Edition Update Error - XO-Web:
@Dashrender said in XO Community Edition Update Error - XO-Web:
@Danp said in XO Community Edition Update Error - XO-Web:
It's not a whole new thing. Yarn replaces the command
npm i
which previously handles the dependency installation.But it is new, it's a new thing you have to install. It's not like you just upgraded npm and the new version does what you want, you installed a whole new program to handle this. Which also required you changing
theirthe update script to use the new dependency manager.Corrected.
oh yeah.. my bad.
-
On trying the clean installation this is what I'm getting.
[15:48:59] 'buildScripts' errored after 1.3 min [15:48:59] GulpUglifyError: unable to minify JavaScript Caused by: SyntaxError: Unexpected character '`' (line: 98370, col: 13, pos: 3117237) Error at new JS_Parse_Error (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:1547:18) at js_error (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:1555:11) at parse_error (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:1679:9) at Object.next_token [as input] (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:1951:9) at next (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2080:25) at eval (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2210:42) at eval (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2141:24) at block_ (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2434:20) at eval (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2406:25) at function_ (eval at <anonymous> (/opt/xo-web/node_modules/gulp-uglify/node_modules/uglify-js/tools/node.js:1:1), <anonymous>:2412:15) [15:48:59] 'build' errored after 1.3 min npm ERR! Linux 4.8.0-39-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build" npm ERR! node v7.6.0 npm ERR! npm v4.1.2 npm ERR! code ELIFECYCLE npm ERR! [email protected] build: `npm run build-indexes && NODE_ENV=production gulp build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] build script 'npm run build-indexes && NODE_ENV=production gulp build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the xo-web package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm run build-indexes && NODE_ENV=production gulp build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs xo-web npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls xo-web npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /opt/xo-web/npm-debug.log
-
@DustinB3403 That was the original issue that I ran into prior to introducing yarn.
-
@Danp yeah... it's weird... why would yarn disappear from the system when it's installed separately...
-
I wonder if we'll have to add the yarn installation as a part of the install script, and from there install it, and then begin the installation.
-
@DustinB3403 Yarn hasn't disappeared. It's just that something is causing the update process to fail.
-
@Danp yeah I know, but the error is identical to the error we had before. So as far as the reporting is listed, it's like yarn or some dependency has disappeared.
-
OK so I just updated my lab copy of XO, and it worked without issue. I'm gonna snapshot, and try the update again and see if it breaks.
-
Paging @hobbit666, use putty and post the output here so we can dissect your installation.
-
OK so I got Yarn installed do I still use Scott's script to install or clone first and run yarn from the directories?
-
Download the installation script to
/
thenchmod +x xo-install.sh
then run it.You could also use the bash version of it.