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

    xo-server/bin doesn't exist after updating with yarn build.

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    25 Posts 5 Posters 5.7k Views 1 Watching
    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.
    • DanpD Online
      Danp Pro Support Team
      last edited by

      There was a recent change that resulted in the launched module being renamed. You need to redo your service so that it loads ./dist/cli.mjs instead of ./bin/xo-server

      R 1 Reply Last reply Reply Quote 2
      • R Offline
        runevn @Danp
        last edited by

        @danp Thanks for your reply. Now I have run (based on these instructions )

        However, I can't still reach the web UI of XO

        yarn global add forever
        yarn global add forever-service
        # Be sure to edit the path below to where your install is located!
        cd /home/username/xen-orchestra/packages/xo-server/
        # Change the username below to the user owning XO
        forever-service install orchestra -r username -s dist/cli.mjs
        

        Or should I redo my service in another way?

        Now the output of systemctl status orchestra is:

        mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
        ● orchestra.service - LSB: forever-service startup script for orchestra
           Loaded: loaded (/etc/init.d/orchestra; generated)
           Active: active (exited) since Tue 2021-06-29 09:01:08 CEST; 4s ago
             Docs: man:systemd-sysv-generator(8)
          Process: 1857 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
        
        Jun 29 09:01:08 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
        Jun 29 09:01:08 xo-community orchestra[1857]: (node:1861) Warning: Accessing non-existent property 'padLevels' of module exports inside c
        Jun 29 09:01:08 xo-community orchestra[1857]: (Use `node --trace-warnings ...` to show where the warning was created)
        Jun 29 09:01:08 xo-community orchestra[1857]: (node:1861) Warning: Accessing non-existent property 'padLevels' of module exports inside c
        Jun 29 09:01:08 xo-community orchestra[1857]: Service orchestra already running
        Jun 29 09:01:08 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
        
        DanpD 1 Reply Last reply Reply Quote 0
        • DanpD Online
          Danp Pro Support Team @runevn
          last edited by

          @runevn Is the web interface now accessible? FWIW I'm not familiar with forever, so I can't help any further on this.

          R 2 Replies Last reply Reply Quote 0
          • R Offline
            runevn @Danp
            last edited by

            @danp unfortunately no.

            1 Reply Last reply Reply Quote 0
            • R Offline
              runevn @Danp
              last edited by

              @danp said in xo-server/bin doesn't exist after updating with yarn build.:

              I'm not familiar with forever, so I can't help any further on this.

              May I ask, if you do not use forever how would you then redo the service?

              Thanks for your help.

              DanpD 1 Reply Last reply Reply Quote 0
              • DanpD Online
                Danp Pro Support Team @runevn
                last edited by

                @runevn Try deleting the service and then recreating it. From here, this should handle the deletion portion ---

                forever-service delete orchestra

                R 1 Reply Last reply Reply Quote 0
                • R Offline
                  runevn @Danp
                  last edited by

                  @danp I have just deleted the forever-service and reinstalled it but it didn't help. I can't still access the Web UI.

                  I still get this status message

                  mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
                  ● orchestra.service - LSB: forever-service startup script for orchestra
                     Loaded: loaded (/etc/init.d/orchestra; generated)
                     Active: active (exited) since Tue 2021-06-29 11:52:21 CEST; 3s ago
                       Docs: man:systemd-sysv-generator(8)
                    Process: 30529 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
                  
                  Jun 29 11:52:21 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
                  Jun 29 11:52:21 xo-community orchestra[30529]: (node:30533) Warning: Accessing non-existent property 'padLevels' of module exports inside
                  Jun 29 11:52:21 xo-community orchestra[30529]: (Use `node --trace-warnings ...` to show where the warning was created)
                  Jun 29 11:52:21 xo-community orchestra[30529]: (node:30533) Warning: Accessing non-existent property 'padLevels' of module exports inside
                  Jun 29 11:52:21 xo-community orchestra[30529]: Starting orchestra
                  Jun 29 11:52:21 xo-community orchestra[30529]: (node:30550) Warning: Accessing non-existent property 'padLevels' of module exports inside
                  Jun 29 11:52:21 xo-community orchestra[30529]: (Use `node --trace-warnings ...` to show where the warning was created)
                  Jun 29 11:52:21 xo-community orchestra[30529]: (node:30550) Warning: Accessing non-existent property 'padLevels' of module exports inside
                  Jun 29 11:52:21 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
                  
                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD Online
                    Danp Pro Support Team @runevn
                    last edited by

                    What's your Node version? Post the output of node -v. You should be on v14.17.1.

                    R 1 Reply Last reply Reply Quote 0
                    • R Offline
                      runevn @Danp
                      last edited by

                      @danp said in xo-server/bin doesn't exist after updating with yarn build.:

                      What's your Node version? Post the output of node -v. You should be on v14.17.1.

                      Yes

                      mex@xo-community:~/xen-orchestra/packages/xo-server$ node -v
                      v14.17.1
                      

                      Again, thanks for your replies.

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

                        @runevn said in xo-server/bin doesn't exist after updating with yarn build.:

                        Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency

                        https://github.com/foreversd/forever/issues/1077

                        SwapnilSoni1999 created this issue in foreversd/forever

                        open [node v14.x+] Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency #1077

                        R 1 Reply Last reply Reply Quote 1
                        • R Offline
                          runevn @Danp
                          last edited by

                          @danp

                          Does this means that XO can't find its own module or is it node's module?

                          mex@xo-community:~$ node --trace-warnings ...
                          internal/modules/cjs/loader.js:905
                            throw err;
                            ^
                          
                          Error: Cannot find module '/home/mex/...'
                              at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                              at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                              at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
                              at internal/main/run_main_module.js:17:47 {
                            code: 'MODULE_NOT_FOUND',
                            requireStack: []
                          }
                          
                          DanpD 1 Reply Last reply Reply Quote 0
                          • DanpD Online
                            Danp Pro Support Team @runevn
                            last edited by

                            @runevn IDK. Maybe @julien-f can suggest a solution for this.

                            R 1 Reply Last reply Reply Quote 1
                            • R Offline
                              runevn @Danp
                              last edited by

                              @danp said in xo-server/bin doesn't exist after updating with yarn build.:

                              @runevn IDK. Maybe @julien-f can suggest a solution for this.

                              But thank you for your effort! I really appreciate it.

                              julien-fJ 1 Reply Last reply Reply Quote 0
                              • julien-fJ Offline
                                julien-f Vates 🪐 Co-Founder XO Team @runevn
                                last edited by

                                @runevn Don't know much about forever, in the meantime, you can try to run xo-server manually:

                                > cd packages/xo-server
                                > ./dist/cli.mjs
                                
                                R DanpD 2 Replies Last reply Reply Quote 1
                                • R Offline
                                  runevn @julien-f
                                  last edited by

                                  @julien-f said in xo-server/bin doesn't exist after updating with yarn build.:

                                  @runevn Don't know much about forever, in the meantime, you can try to run xo-server manually:

                                  > cd packages/xo-server
                                  > ./dist/cli.mjs
                                  

                                  Thanks for your reply @julien-f . When I manually run xo-server it still doesn't work. Here is the output

                                  mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo ./dist/cli.mjs
                                  (node:65352) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
                                  (Use `node --trace-warnings ...` to show where the warning was created)
                                  /home/mex/xen-orchestra/packages/xo-server/dist/xapi/mixins/index.js:2
                                  import _gpu, * as __gpu from "./gpu";
                                  ^^^^^^
                                  
                                  SyntaxError: Cannot use import statement outside a module
                                      at wrapSafe (internal/modules/cjs/loader.js:1001:16)
                                      at Module._compile (internal/modules/cjs/loader.js:1049:27)
                                      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
                                      at Module.load (internal/modules/cjs/loader.js:950:32)
                                      at Function.Module._load (internal/modules/cjs/loader.js:790:14)
                                      at ModuleWrap.<anonymous> (internal/modules/esm/translators.js:199:29)
                                      at ModuleJob.run (internal/modules/esm/module_job.js:169:25)
                                      at async Loader.import (internal/modules/esm/loader.js:177:24)
                                      at async Object.loadESM (internal/process/esm_loader.js:68:5)
                                  mex@xo-community:~/xen-orchestra/packages/xo-server$
                                  

                                  Is there any other information that I can provide?

                                  julien-fJ 1 Reply Last reply Reply Quote 0
                                  • julien-fJ Offline
                                    julien-f Vates 🪐 Co-Founder XO Team @runevn
                                    last edited by

                                    @runevn https://xcp-ng.org/forum/post/39787

                                    DanpD 1 Reply Last reply Reply Quote 1
                                    • DanpD Online
                                      Danp Pro Support Team @julien-f
                                      last edited by

                                      git clean -d -f should work to remove any untracked files.

                                      1 Reply Last reply Reply Quote 1
                                      • DanpD Online
                                        Danp Pro Support Team @julien-f
                                        last edited by

                                        @julien-f Do we know what leads to these untracked files? Could it be file renaming such as here?

                                        julien-fJ 1 Reply Last reply Reply Quote 1
                                        • julien-fJ Offline
                                          julien-f Vates 🪐 Co-Founder XO Team @Danp
                                          last edited by

                                          @danp No, those are generated files.

                                          Unfortunately they are not cleaned-up automatically but hopefully this won't happen too often 🙂

                                          R 1 Reply Last reply Reply Quote 1
                                          • R Offline
                                            runevn @julien-f
                                            last edited by

                                            @julien-f and @Danp thanks a lot for your help! Now it works if I manually run cli.mjs

                                            mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo ./dist/cli.mjs
                                            2021-06-30T06:21:41.457Z xo:main INFO Configuration loaded.
                                            2021-06-30T06:21:41.478Z xo:main INFO Web server listening on http://[::]:80
                                            2021-06-30T06:21:41.924Z xo:main INFO Setting up / → /home/mex/xen-orchestra/packages/xo-web/dist
                                            

                                            However, what should I do to recreate the service to start on boot. When setting up and using forever as described here. I'm still not able to load the web interface.

                                            It seems that the service starts and is active

                                            mex@xo-community:~/xen-orchestra/packages/xo-server$ sudo service orchestra status
                                            ● orchestra.service - LSB: forever-service startup script for orchestra
                                               Loaded: loaded (/etc/init.d/orchestra; generated)
                                               Active: active (exited) since Wed 2021-06-30 08:28:05 CEST; 3min 15s ago
                                                 Docs: man:systemd-sysv-generator(8)
                                              Process: 1141 ExecStart=/etc/init.d/orchestra start (code=exited, status=0/SUCCESS)
                                            
                                            Jun 30 08:28:04 xo-community systemd[1]: Starting LSB: forever-service startup script for orchestra...
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (node:1145) Warning: Accessing non-existent property 'padLevels' of module exports inside c
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (Use `node --trace-warnings ...` to show where the warning was created)
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (node:1145) Warning: Accessing non-existent property 'padLevels' of module exports inside c
                                            Jun 30 08:28:05 xo-community orchestra[1141]: Starting orchestra
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (node:1162) Warning: Accessing non-existent property 'padLevels' of module exports inside c
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (Use `node --trace-warnings ...` to show where the warning was created)
                                            Jun 30 08:28:05 xo-community orchestra[1141]: (node:1162) Warning: Accessing non-existent property 'padLevels' of module exports inside c
                                            Jun 30 08:28:05 xo-community systemd[1]: Started LSB: forever-service startup script for orchestra.
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post