XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XO from the sources - Something in the pages is missing

    Scheduled Pinned Locked Moved
    Xen Orchestra
    5
    19
    1.2k
    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.
    • D
      dcstancu
      last edited by

      teste 3 ubuntu vm's , pages not working :

      1. Settings all submenus same error page not found
      2. Jobs all submenus same error page not found
      3. Backups all submenus same error page not found
      4. Backups NG all submenus same error page not found
      iseeu@xoa:~$ systemctl status xo-server.service
● xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset
   Active: active (running) since Tue 2019-05-21 16:02:41 UTC; 3min 44s ago
 Main PID: 854 (node)
    Tasks: 52 (limit: 4623)
   CGroup: /system.slice/xo-server.service
           ├─ 854 node /etc/xo/xo-server/bin/xo-server
           ├─1370 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           ├─1375 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           ├─1381 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           ├─1387 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           ├─1393 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           ├─1399 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod
           └─1405 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/nod

May 21 16:02:41 xoa systemd[1]: Started XO Server.
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.506Z - xo:main - [INFO]
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.518Z - xo:main - [INFO]
May 21 16:02:54 xoa xo-server[854]: Warning: connect.session() MemoryStore is no
May 21 16:02:54 xoa xo-server[854]: designed for a production environment, as it
May 21 16:02:54 xoa xo-server[854]: memory, and will not scale past a single pro
May 21 16:02:54 xoa xo-server[854]: 2019-05-21T16:02:54.165Z - xo:main - [INFO]
May 21 16:02:55 xoa xo-server[854]: 2019-05-21T16:02:55.600Z - xo:main - [INFO]
lines 1-23...skipping...
● xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-05-21 16:02:41 UTC; 3min 44s ago
 Main PID: 854 (node)
    Tasks: 52 (limit: 4623)
   CGroup: /system.slice/xo-server.service
           ├─ 854 node /etc/xo/xo-server/bin/xo-server
           ├─1370 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           ├─1375 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           ├─1381 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           ├─1387 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           ├─1393 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           ├─1399 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js
           └─1405 /usr/bin/node /etc/xo/xo-builds/xen-orchestra-201921051346/node_modules/jest-worker/build/workers/processChild.js

May 21 16:02:41 xoa systemd[1]: Started XO Server.
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.506Z - xo:main - [INFO] Configuration loaded.
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.518Z - xo:main - [INFO] Web server listening on http://[::]:80
May 21 16:02:54 xoa xo-server[854]: Warning: connect.session() MemoryStore is not
May 21 16:02:54 xoa xo-server[854]: designed for a production environment, as it will leak
May 21 16:02:54 xoa xo-server[854]: memory, and will not scale past a single process.
May 21 16:02:54 xoa xo-server[854]: 2019-05-21T16:02:54.165Z - xo:main - [INFO] Setting up / → /etc/xo/xo-builds/xen-orchestra-201921051346/packages/xo-web/dist
May 21 16:02:55 xoa xo-server[854]: 2019-05-21T16:02:55.600Z - xo:main - [INFO] + WebSocket connection (::ffff:10.0.0.200)
May 21 16:05:46 xoa xo-server[854]: 2019-05-21T16:05:46.869Z - xo:main - [INFO] - WebSocket connection (::ffff:10.0.0.200)
May 21 16:05:48 xoa xo-server[854]: 2019-05-21T16:05:48.142Z - xo:main - [INFO] + WebSocket connection (::ffff:10.0.0.200)


      May 21 16:02:41 xoa systemd[1]: Started XO Server.
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.506Z - xo:main - [INFO] Configuration loaded.
May 21 16:02:53 xoa xo-server[854]: 2019-05-21T16:02:53.518Z - xo:main - [INFO] Web server listening on http://[::]:80
May 21 16:02:54 xoa xo-server[854]: Warning: connect.session() MemoryStore is not
May 21 16:02:54 xoa xo-server[854]: designed for a production environment, as it will leak
May 21 16:02:54 xoa xo-server[854]: memory, and will not scale past a single process.
May 21 16:02:54 xoa xo-server[854]: 2019-05-21T16:02:54.165Z - xo:main - [INFO] Setting up / → /etc/xo/xo-builds/xen-orchestra-201921051346/packages/xo-web/dist
May 21 16:02:55 xoa xo-server[854]: 2019-05-21T16:02:55.600Z - xo:main - [INFO] + WebSocket connection (::ffff:10.0.0.200)
May 21 16:05:46 xoa xo-server[854]: 2019-05-21T16:05:46.869Z - xo:main - [INFO] - WebSocket connection (::ffff:10.0.0.200)
May 21 16:05:48 xoa xo-server[854]: 2019-05-21T16:05:48.142Z - xo:main - [INFO] + WebSocket connection (::ffff:10.0.0.200)

      Now i will deploy ( bash -c "$(curl -s http://xoa.io/deploy) )

      1 Reply Last reply Reply Quote 0
      • D
        dcstancu
        last edited by dcstancu

        ok.jpg ok2.jpg

        is ok from official install , onlu my free trial is expired

        1 Reply Last reply Reply Quote 0
        • olivierlambertO
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Okay so it's a problem either from:

          • the 3rd party install script
          • or current master branch state

          Double check your Node/npm versions and try to install following our official documentation: https://xen-orchestra.com/docs/from_the_sources.html

          1 Reply Last reply Reply Quote 0
          • P
            papaf76
            last edited by

            I'm sure you know, Olivier, but master is now 5.41 and there are some info about a change on admin detection in the new code that seem like the culprit. Is there a way to verify if XOA 5.41 maybe does the same?

            1 Reply Last reply Reply Quote 0
            • D
              dcstancu
              last edited by

              https://xen-orchestra.com/docs/from_the_sources.html

              install success !
              okok.jpg

              the 3rd party install script have some issues

              1 Reply Last reply Reply Quote 0
              • olivierlambertO
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by olivierlambert

                Okay so this is something I'm usually talking about (to be clear, it's not your fault, I just made a recap):

                1. the official way to install XO is in our official doc, you'll have community support from here
                2. if you have an issue with a 3rd party script, report to the 3rd party script (you did it 👍 )
                3. XOA is considered as the QA/verified way

                Just to check: did you know that you were installing from a 3rd party script or it was confusing? Did you find the official doc before?

                I'd like to improve the "path" for new comers and be sure they are using the software in a way that's not giving a bad impression 🙂 So if you didn't find the official way first, there is something we could do on our side (maybe updating the doc to be clear about 3rd party scripts?)

                D 1 Reply Last reply Reply Quote 0
                • D
                  dcstancu @olivierlambert
                  last edited by

                  yes a have know i have instaled from 3rd party ( more fast deploy )
                  the "path" is ok , no problems finding

                  10q for the support

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    Thanks for your feedback 🙂 We are also working on improving doc to get it more straightforward!

                    1 Reply Last reply Reply Quote 0
                    • DanpD
                      Danp Vates 🪐 Pro Support Team
                      last edited by

                      @dcstancu FWIW, I just ran the update script and everything is still functioning fine for my XO install. Granted... I'm using a newer version of Ubuntu than you.

                      Looking forward to your further input on the GH issue you opened earlier today.

                      1 Reply Last reply Reply Quote 0
                      • P
                        papaf76
                        last edited by

                        Olivier, did your team do something? Even the other script now works and yet Github doesn't report any activity...

                        1 Reply Last reply Reply Quote 0
                        • olivierlambertO
                          olivierlambert Vates 🪐 Co-Founder CEO
                          last edited by

                          I'm not aware of anything special on our side, I even didn't notify the dev team about this issue before knowing more on it (to avoid them switching to an issue that's not linked to XO code directly but the environment).

                          1 Reply Last reply Reply Quote 0
                          • pdoniasP
                            pdonias Vates 🪐 XO Team
                            last edited by

                            Hi! We introduced a bug in commit 59e6868 causing "Page not found"s and fixed it in commit 6e52794.

                            DanpD 1 Reply Last reply Reply Quote 2
                            • DanpD
                              Danp Vates 🪐 Pro Support Team @pdonias
                              last edited by

                              @pdonias Thanks for confirming that this issue wasn't caused by the use of a 3rd party script.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post