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

    BRRABill's Field Report With XenServer

    IT Discussion
    20
    750
    359.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.
    • scottalanmillerS
      scottalanmiller @BRRABill
      last edited by

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

      Not in /var/log

      Maybe another XO user with chime in, or eventually @olivier will come to the rescue! 🙂

      Have you modified the logs?

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

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

        @scottalanmiller said

        Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.

        That answers my question.

        That most logs are supposed to be in /var/log

        Yes, that is the standard log location.

        RomoR 1 Reply Last reply Reply Quote 0
        • RomoR
          Romo @scottalanmiller
          last edited by

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

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

          @scottalanmiller said

          Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.

          That answers my question.

          That most logs are supposed to be in /var/log

          Yes, that is the standard log location.

          Wouldn't XO logs be in /var/log/syslog, since it is normally installed in ubuntu?

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

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

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

            Not in /var/log

            Maybe another XO user with chime in, or eventually @olivier will come to the rescue! 🙂

            Have you modified the logs?

            Noooooooooooooooooooooooooo

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

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

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

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

              @scottalanmiller said

              Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.

              That answers my question.

              That most logs are supposed to be in /var/log

              Yes, that is the standard log location.

              Wouldn't XO logs be in /var/log/syslog, since it is normally installed in ubuntu?

              Hey, there is xo-server stuff in there!!!

              So, do all apps write to that one file?

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

                This is what is appearing over and over and over and over again...

                Aug 18 06:26:58 ubuntu systemd[1]: Started XO Server.
Aug 18 06:27:01 ubuntu xo-server[26354]: (node:26354) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Aug 18 06:27:01 ubuntu xo-server[26354]: /opt/xo-server/node_modules/bindings/bindings.js:83
Aug 18 06:27:01 ubuntu xo-server[26354]:         throw e
Aug 18 06:27:01 ubuntu xo-server[26354]:         ^
Aug 18 06:27:01 ubuntu xo-server[26354]: Error: Module version mismatch. Expected 48, got 47.
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at bindings (/opt/xo-server/node_modules/bindings/bindings.js:76:44)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/opt/xo-server/node_modules/leveldown/leveldown.js:4:46)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/opt/xo-server/node_modules/level/level.js:1:44)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/opt/xo-server/node_modules/level-party/index.js:1:13)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/source/xo-mixins/store.js:2)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/source/xo-mixins/index.js:46)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/source/xo.js:7)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/source/index.js:28)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at require (internal/module.js:20:19)
Aug 18 06:27:01 ubuntu xo-server[26354]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 06:27:02 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 06:27:02 ubuntu systemd[1]: Stopped XO Server.
Aug 18 06:27:02 ubuntu systemd[1]: Started XO Server.
                RomoR 1 Reply Last reply Reply Quote 0
                • RomoR
                  Romo @BRRABill
                  last edited by

                  @BRRABill try journalctl -u xo-server -f -n 50

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

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

                    That I do not know.

                    Like I said, I've done nothing but install XO and use apt-get update and upgrade.

                    The latest version of the update script does perform an update to the latest stable version of Node. I haven't found this to be a problem thus far, and I updated within the last day or so.

                    BRRABillB 2 Replies Last reply Reply Quote 0
                    • momurdaM
                      momurda
                      last edited by

                      It looks like your apt-get update and upgrade upgraded something to too new a version.
                      I cant remember what repos xo uses.
                      Can you roll back or reinstall then try using the upgrade button in xo web?

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

                        @Danp said

                        The latest version of the update script does perform an update to the latest stable version of Node. I haven't found this to be a problem thus far, and I updated within the last day or so.

                        What update script?

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

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

                          journalctl -u xo-server -f -n 50

                          journalctl -u xo-server -f -n 50
-- Logs begin at Thu 2016-08-18 16:57:07 EDT. --
Aug 18 17:05:26 ubuntu xo-server[4846]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:26 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:26 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:26 ubuntu xo-server[4854]: module.js:442
Aug 18 17:05:26 ubuntu xo-server[4854]:     throw err;
Aug 18 17:05:26 ubuntu xo-server[4854]:     ^
Aug 18 17:05:26 ubuntu xo-server[4854]: Error: Cannot find module './dist'
Aug 18 17:05:26 ubuntu xo-server[4854]:     at require (internal/module.js:20:19)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at require (internal/module.js:20:19)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:26 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:26 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:27 ubuntu xo-server[4862]: module.js:442
Aug 18 17:05:27 ubuntu xo-server[4862]:     throw err;
Aug 18 17:05:27 ubuntu xo-server[4862]:     ^
Aug 18 17:05:27 ubuntu xo-server[4862]: Error: Cannot find module './dist'
Aug 18 17:05:27 ubuntu xo-server[4862]:     at require (internal/module.js:20:19)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at require (internal/module.js:20:19)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:27 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:27 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:28 ubuntu xo-server[4870]: module.js:442
Aug 18 17:05:28 ubuntu xo-server[4870]:     throw err;
Aug 18 17:05:28 ubuntu xo-server[4870]:     ^
Aug 18 17:05:28 ubuntu xo-server[4870]: Error: Cannot find module './dist'
Aug 18 17:05:28 ubuntu xo-server[4870]:     at require (internal/module.js:20:19)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at require (internal/module.js:20:19)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:28 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Start request repeated too quickly.
Aug 18 17:05:28 ubuntu systemd[1]: Failed to start XO Server.
                          1 Reply Last reply Reply Quote 0
                          • BRRABillB
                            BRRABill @Danp
                            last edited by

                            @Danp said

                            The latest version of the update script does perform an update to the latest stable version of Node. I haven't found this to be a problem thus far, and I updated within the last day or so.

                            Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

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

                              @BRRABill The same one that was mentioned earlier here.

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

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

                                @BRRABill The same one that was mentioned earlier here.

                                Yeah, I tried running that last week, and it failed on me.

                                I didn't think anything of it, but I haven't been back into XO since then. So apparently that could be what broke my stuff. 🙂

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

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

                                  Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

                                  Failed how? Did you run it as root (sudo bash)? Details please.

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

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

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

                                    Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

                                    Failed how? Did you run it as root (sudo bash)? Details please.

                                    I honestly do no remember.

                                    It just didn't work.

                                    Want me to try running it now?

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

                                      @BRRABill Sure... here's the commands:

                                      sudo bash
<password>
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash
                                      BRRABillB 1 Reply Last reply Reply Quote 0
                                      • BRRABillB
                                        BRRABill
                                        last edited by 

                                        sudo bash xo-update.sh
Stopping xo-server...
Updating Node.js to latest stable version...

     install : node-v6.4.0
       mkdir : /usr/local/n/versions/node/6.4.0
       fetch : https://nodejs.org/dist/v6.4.0/node-v6.4.0-linux-x64.tar.gz
######################################################################## 100.0%
   installed : v6.4.0

Checking xo-server...
xo-update.sh: line 38: updateFromSource: command not found
Checking xo-web...
xo-update.sh: line 42: updateFromSource: command not found
Please manually restart xo-server
                                        1 Reply Last reply Reply Quote 0
                                        • BRRABillB
                                          BRRABill @Danp
                                          last edited by

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

                                          @BRRABill Sure... here's the commands:

                                          sudo bash
<password>
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash

                                          Oh, that's not what I did. I downloaded the file, and then ran it.

                                          This command made it work.

                                          Still not running xo-server though

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

                                            @BRRABill Does it start with sudo systemctl start xo-server?

                                            BRRABillB 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 34
                                            • 35
                                            • 36
                                            • 37
                                            • 38
                                            • 38 / 38
                                            • First post
                                              Last post