ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XO Community Edition Update Error - XO-Web

    IT Discussion
    xen orchestra community xen orchestra xo web error
    4
    44
    5.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403 @Dashrender
      last edited by

      @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 their the update script to use the new dependency manager.

      Corrected.

      oh yeah.. my bad.

      😉

      1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403
        last edited by

        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
        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD
          Danp @DustinB3403
          last edited by

          @DustinB3403 That was the original issue that I ran into prior to introducing yarn.

          1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

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

            DanpD 1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • DanpD
                Danp @DustinB3403
                last edited by

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

                DustinB3403D 1 Reply Last reply Reply Quote 0
                • DustinB3403D
                  DustinB3403 @Danp
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • DustinB3403D
                    DustinB3403
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 2
                    • DustinB3403D
                      DustinB3403
                      last edited by

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

                      1 Reply Last reply Reply Quote 2
                      • hobbit666H
                        hobbit666
                        last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • DustinB3403D
                          DustinB3403
                          last edited by

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

                          You could also use the bash version of it.

                          hobbit666H 1 Reply Last reply Reply Quote 0
                          • hobbit666H
                            hobbit666 @DustinB3403
                            last edited by

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

                            1 Reply Last reply Reply Quote 0
                            • DustinB3403D
                              DustinB3403
                              last edited by

                              scotts

                              1 Reply Last reply Reply Quote 0
                              • hobbit666H
                                hobbit666
                                last edited by

                                Seems to be working 🙂 thanks for the help @DustinB3403

                                1 Reply Last reply Reply Quote 0
                                • DanpD
                                  Danp
                                  last edited by

                                  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#
                                  1 Reply Last reply Reply Quote 0
                                  • DanpD
                                    Danp
                                    last edited by

                                    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?

                                    1 Reply Last reply Reply Quote 0
                                    • DanpD
                                      Danp
                                      last edited by

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

                                      DanpD 1 Reply Last reply Reply Quote 0
                                      • DanpD
                                        Danp @Danp
                                        last edited by

                                        Except that doesn't appear to generate the dist directory

                                        1 Reply Last reply Reply Quote 0
                                        • DanpD
                                          Danp
                                          last edited by

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

                                          DustinB3403D 1 Reply Last reply Reply Quote 1
                                          • DustinB3403D
                                            DustinB3403 @Danp
                                            last edited by

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

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

                                            ?

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post