XO Community Edition Update Error - XO-Web

DustinB3403

@Danp yeah... it's weird... why would yarn disappear from the system when it's installed separately...

DustinB3403

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.

Danp

@DustinB3403 Yarn hasn't disappeared. It's just that something is causing the update process to fail.

DustinB3403

@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.

DustinB3403

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.

DustinB3403

Paging @hobbit666, use putty and post the output here so we can dissect your installation.

hobbit666

OK so I got Yarn installed do I still use Scott's script to install or clone first and run yarn from the directories?

DustinB3403

Download the installation script to / then chmod +x xo-install.sh then run it.

You could also use the bash version of it.

hobbit666

@DustinB3403 said in XO Community Edition Update Error - XO-Web:

Download the installation script to / then chmod +x xo-install.sh then run it.

You could also use the bash version of it.

Scotts script or someone else's

DustinB3403

scotts

hobbit666

Seems to be working thanks for the help @DustinB3403

Danp

In some cases, the yarn command is failing when it gets to the "build" process --

root@xo-5:/opt/xo-server# yarn
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-40-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
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.
root@xo-5:/opt/xo-server#

Danp

Works as expected if I do an npm i first. So it appears that the index files aren't being built by yarn. Does that sound correct?

Danp

Appears to work better for me with the optional upgrade parameter, ie:
yarn upgrade

Danp

Except that doesn't appear to generate the dist directory

Danp

yarn install --force works correctly for me on multiple rebuild attempts.

DustinB3403

@Danp Is that from the script, or in each directory?

/opt/xo-server and ../xo-web

?

Danp

Both.

DustinB3403

@Danp, Testing in my lab now with the finalized changes.

DustinB3403

Seems functional using the updated script.

I've applied the change to the update script.