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

    BRRABill's Field Report With XenServer

    IT Discussion
    20
    750
    382.5k
    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.
    • olivierO
      olivier @Danp
      last edited by

      @Danp Well, so we don't have enough to draw any conclusion 😕

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

        @olivier Ok... I'm sure there will be more patches soon to test again. 😉

        1 Reply Last reply Reply Quote 0
        • BRRABillB
          BRRABill
          last edited by

          @olivier

          I used XO tonight to reboot a XS and it got stuck in maintenance mode.

          Think that was something strange on my end?

          (I ended up using XC to reboot it afterwards.)

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

            @BRRABill It's a bug. Here's the GH Issue.

            BRRABillB 1 Reply Last reply Reply Quote 0
            • BRRABillB
              BRRABill
              last edited by

              Stupid GitHub.

              Just. Don't. Get. It.

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

                @Danp said in BRRABill's Field Report With XenServer:

                @BRRABill It's a bug. Here's the GH Issue.

                So what causes that bug?

                I was just trying to reboot after a patch update.

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

                  @BRRABill My take is that there are multiple issues at work here --

                  1. Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.

                  2. XO's implementation of host reboot is very different from that found in XC

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

                    @Danp said in BRRABill's Field Report With XenServer:

                    @BRRABill My take is that there are multiple issues at work here --

                    1. Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.

                    2. XO's implementation of host reboot is very different from that found in XC

                    Yeah I went to the server room and was surprised the XS was just sitting there. Then XC said it was i maintenance mode. I right clicked in XC and rebooted again, and it went to maintenance mode for a second and rebooted.

                    Very strange.

                    1 Reply Last reply Reply Quote 0
                    • BRRABillB
                      BRRABill
                      last edited by

                      Anyone using XO...

                      When you run an update, do you have to reboot to get the next version to show up?

                      Or is there a service to restart?

                      xo-web always updates to the right version in the GUI. xo-server never does until I reboot.

                      1 Reply Last reply Reply Quote 0
                      • olivierO
                        olivier
                        last edited by

                        No need to reboot, you are not on Windows 😉 xo-server runs in memory, so to get last version, you need to restart the process. That's all.

                        BRRABillB 1 Reply Last reply Reply Quote 1
                        • BRRABillB
                          BRRABill @olivier
                          last edited by BRRABill

                          @olivier said in BRRABill's Field Report With XenServer:

                          No need to reboot, you are not on Windows 😉 xo-server runs in memory, so to get last version, you need to restart the process. That's all.

                          Thanks @olivier

                          I try not to ping you on these. You have better stuff to do than to educate me, which you always do a great job of anyway!

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

                            @BRRABill Are you updating manually or with the script? The script will stop and restart the service for you.

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

                              @Danp said in BRRABill's Field Report With XenServer:

                              @BRRABill Are you updating manually or with the script? The script will stop and restart the service for you.

                              Manually.

                              THOUGH ... I did just take a stab at writing my own script!

                              THOUGH THOUGH ... why not just use one already made. 🙂

                              1 Reply Last reply Reply Quote 0
                              • BRRABillB
                                BRRABill
                                last edited by

                                So, went to log into XO today, it's not accessible. I reboot the server, still not.

                                I figure, eh, I'll update the version.

                                xoserver updates fine, but xo-web fails with the below messages...

                                This is on Ubuntu 16.04

                                Is it possible some OS update broke something in my system?

                                
[16:15:17] 'buildStyles' errored after 1.56 s
[16:15:17] Error: The `libsass` binding was not found in /opt/xo-web/node_modules/node-sass/vendor/linux-x64-48/binding.node
This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.
    at Object.sass.getBinaryPath (/opt/xo-web/node_modules/node-sass/lib/extensions.js:158:11)
    at Object.<anonymous> (/opt/xo-web/node_modules/node-sass/lib/index.js:16:36)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/opt/xo-web/node_modules/gulp-sass/index.js:186:21)
[16:15:17] 'build' errored after 1.57 s
[16:15:17] The following tasks did not complete: buildPages, buildScripts, copyAssets
[16:15:17] Did you forget to signal async completion?

npm ERR! Linux 4.4.0-34-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.2.2
npm ERR! npm  v3.10.7
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
                                1 Reply Last reply Reply Quote 0
                                • T
                                  tiagom
                                  last edited by

                                  Has your node version changed?

                                  BRRABillB 1 Reply Last reply Reply Quote 0
                                  • BRRABillB
                                    BRRABill @tiagom
                                    last edited by

                                    @tiagom said in BRRABill's Field Report With XenServer:

                                    Has your node version changed?

                                    I didn't purposely change anything.

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      tiagom
                                      last edited by

                                      What version of node is installed?

                                      BRRABillB 1 Reply Last reply Reply Quote 0
                                      • BRRABillB
                                        BRRABill @tiagom
                                        last edited by

                                        @tiagom said in BRRABill's Field Report With XenServer:

                                        What version of node is installed?

                                        v6.2.2

                                        1 Reply Last reply Reply Quote 0
                                        • olivierO
                                          olivier
                                          last edited by 

                                          This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.

                                          Did you tried that?

                                          BRRABillB 1 Reply Last reply Reply Quote 1
                                          • BRRABillB
                                            BRRABill @olivier
                                            last edited by

                                            @olivier said in BRRABill's Field Report With XenServer:

                                            This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.

                                            Did you tried that?

                                            Yes. THat gives me an endless loop of:

                                            suring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 6.2.2
gyp verb ensuring nodedir is created /opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2
gyp WARN EACCES user "root" does not have permission to access the dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp/6.2.2"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/xo-web/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '6.2.2' ]
gyp verb install input version string "6.2.2"
gyp verb install installing version: 6.2.2
gyp
                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 37
                                            • 38
                                            • 3 / 38
                                            • First post
                                              Last post