XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. bern
    3. Posts
    B
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 14
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Shutting down "Protect from accidental shutdown" VMs from command line

      @Zevgeny Did you succeed to remove the protection with "xe vm-param-clear"?

      It didn't worked perfectly for me.

      Before I use xe vm-param-clear, I have the following:

      [18:28 xcpng02 ~]# xe vm-param-list uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 | grep block
                          blocked-operations (MRW): pause: true; hard_shutdown: true; (unknown operation): true; hard_reboot: true; clean_shutdown: true; suspend: true; clean_reboot: true
      [18:28 xcpng02 ~]# 
      

      Now I try to clean:

      [18:28 xcpng02 ~]# xe vm-param-clear uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 param-name=blocked-operations
      The value given is invalid
      field: blocked_operation
      value: (unknown operation)
      [18:28 xcpng02 ~]#
      

      After, "blocked-operations" looks like this:

      [18:28 xcpng02 ~]# xe vm-param-list uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 | grep block
                          blocked-operations (MRW): (unknown operation): true; hard_reboot: true; clean_shutdown: true; suspend: true; clean_reboot: true
      [18:30 xcpng02 ~]# 
      

      In the GUI of XOA, the "Protect from accidental shutdown" is removed but not on the command line.

      posted in Xen Orchestra
      B
      bern
    • RE: Pools don't appear under Settings > Servers on fresh build of XO

      I did use the master by using:
      git clone -b master https://github.com/vatesfr/xen-orchestra

      So I deleted my vm and started over. Everything works fine now. Maybe I did something wrong or a glitch occurred without being noticed.

      Thanks for our help!

      posted in Xen Orchestra
      B
      bern
    • RE: Pools don't appear under Settings > Servers on fresh build of XO

      My XOA is at the current version:

      • Current version: 5.80.2
      • node: 18.12.1
      • npm: 8.19.2
      • xen-orchestra-upload-ova: 0.1.4
      • xo-server: 5.110.1
      • xo-server-telemetry: 0.5.0
      • xo-server-xoa: 0.19.0
      • xo-web-free: 5.113.0
      • xoa-cli: 0.35.0
      • xoa-updater: 0.45.1

      I have no problem with my XOA. The pool are available under Settings -> Servers.

      Maybe I should consider erasing my XO VM and start over. Maybe a glitch occured somewhere šŸ˜•

      posted in Xen Orchestra
      B
      bern
    • RE: Pools don't appear under Settings > Servers on fresh build of XO

      My two xcp-ng servers, my XOA VM and my XO VM are all in the same subnet. šŸ˜•

      posted in Xen Orchestra
      B
      bern
    • RE: Pools don't appear under Settings > Servers on fresh build of XO

      In my setup, I have one host with one pool.

      Host          Pool
      xcpng01       xcpng01
      xcpng02       xcpng02
      

      dmesg shows no problem on both xcpng servers.

      The space looks ok to me:
      [13:43 xcpng01 ~]# df -h 
      Filesystem                                                                                                 Size  Used Avail Use% Mounted on
      devtmpfs                                                                                                   637M  4.0K  637M   1% /dev
      tmpfs                                                                                                      649M  132K  649M   1% /dev/shm
      tmpfs                                                                                                      649M  9.2M  640M   2% /run
      tmpfs                                                                                                      649M     0  649M   0% /sys/fs/cgroup
      /dev/sda1                                                                                                   18G   11G  6.7G  61% /
      xenstore                                                                                                   649M     0  649M   0% /var/lib/xenstored
      /dev/sda5                                                                                                  3.9G  231M  3.4G   7% /var/log
      /dev/mapper/XSLocalEXT--8e7231ff--ff9c--09d4--e3c9--11aef0a9a01d-8e7231ff--ff9c--09d4--e3c9--11aef0a9a01d   70G   24G   43G  36% /run/sr-mount/8e7231ff-ff9c-09d4-e3c9-11aef0a9a01d
      tmpfs                                                                                                      130M     0  130M   0% /run/user/0
      
      [13:46 xcpng02 ~]# df -h 
      Filesystem      Size  Used Avail Use% Mounted on
      devtmpfs        2.0G   24K  2.0G   1% /dev
      tmpfs           2.1G  400K  2.1G   1% /dev/shm
      tmpfs           2.1G   11M  2.0G   1% /run
      tmpfs           2.1G     0  2.1G   0% /sys/fs/cgroup
      /dev/sda1        18G  7.3G  9.5G  44% /
      xenstore        2.1G     0  2.1G   0% /var/lib/xenstored
      /dev/sda5       3.9G  340M  3.3G  10% /var/log
      tmpfs           411M     0  411M   0% /run/user/0
      

      Does the following could point to something?

      In /var/log/orchestra.log, the following messages are repeated continuously about every 2 minutes.

       _watchEvents Error: HTTP connection has timed out
          at ClientRequest.<anonymous> (/opt/xen-orchestra/node_modules/http-request-plus/index.js:49:23)
          at ClientRequest.emit (node:events:513:28)
          at ClientRequest.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
          at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
          at Object.onceWrapper (node:events:627:28)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
          at TLSSocket.Socket._onTimeout (node:net:580:8)
          at listOnTimeout (node:internal/timers:573:17)
          at processTimers (node:internal/timers:514:7) {
        originalUrl: 'https://192.168.9.90/jsonrpc',
        url: 'https://192.168.9.90/jsonrpc',
        call: {
          method: 'event.from',
          params: [ [Array], '00000000000014811213,00000000000014795804', 60.1 ]
        }
      }
      _watchEvents Error: HTTP connection has timed out
          at ClientRequest.<anonymous> (/opt/xen-orchestra/node_modules/http-request-plus/index.js:49:23)
          at ClientRequest.emit (node:events:513:28)
          at ClientRequest.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
          at TLSSocket.emitRequestTimeout (node:_http_client:840:9)
          at Object.onceWrapper (node:events:627:28)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.patchedEmit [as emit] (/opt/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
          at TLSSocket.Socket._onTimeout (node:net:580:8)
          at listOnTimeout (node:internal/timers:573:17)
          at processTimers (node:internal/timers:514:7) {
        originalUrl: 'https://192.168.9.91/jsonrpc',
        url: 'https://192.168.9.91/jsonrpc',
        call: {
          method: 'event.from',
          params: [ [Array], '00000000000021389621,00000000000021275380', 60.1 ]
        }
      }
      

      192.168.9.90 -> xcpng02
      192.168.9.91 -> xcpng01

      posted in Xen Orchestra
      B
      bern
    • Pools don't appear under Settings > Servers on fresh build of XO

      Yesterday, I build a fresh installation of XO on a newly build VM. The build was successful without any error.

      Under Settings > Servers I could add my two xcpng servers. But under "Pool" I don't see my pools.

      MissingPools_Screenshot from 2023-04-17 11-26-54.png

      If I disable and re-enable the servers, the pools appear for a few seconds and disappear. Also, the pools will appear by themselves but will stay only for a few seconds.

      I have no problem with the XO Appliance.

      Someone has an idea of my problem?

      Thanks

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      @julien-f It works!!!

      No more error in the yarn build output.

      Thanks a lot!

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      I reverted to a snapshot of a freshly installed Debian 11 and then I ran the following commands:

      apt-get install build-essential redis-server libpng-dev git python3-minimal libvhdi-utils lvm2 cifs-utils

      apt-get update

      curl -fsSL https://deb.nodesource.com/setup_18.x | bash - && apt-get install -y nodejs

      root@orchestrator:~# node -v
      v18.12.1

      root@orchestrator:~# which yarn
      root@orchestrator:~# corepack enable
      root@orchestrator:~# corepack prepare yarn@stable --activate
      Preparing yarn@stable for immediate activation...
      root@orchestrator:~# which yarn
      /usr/bin/yarn
      root@orchestrator:/opt/xen-orchestra# yarn -v
      3.3.0

      git clone -b master https://github.com/vatesfr/xen-orchestra

      yarn

      yarn build

      It looks like I am out of luck on this. šŸ˜•

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      Here are the commands from my history:

      116 git clone -b master https://github.com/vatesfr/xen-orchestra
      . . .
      119 cd xen-orchestra/
      . . .
      121 yarn
      122 yarn build

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      I ran the command from the documentation:

      git clone -b master https://github.com/vatesfr/xen-orchestra

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      I started from scratch with
      node -v
      v18.12.1

      which is the latest LTS according to https://nodejs.org/en/

      And I have the same errors.

      I am on the same OS as the documentation:
      lsb_release -a
      No LSB modules are available.
      Distributor ID: Debian
      Description: Debian GNU/Linux 11 (bullseye)
      Release: 11
      Codename: bullseye

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      @olivierlambert
      node -v
      v19.2.0

      I don't know if it is related but in the output if yarn, there is a lot of :
      something "can't be found in the cache and will be fetched from the remote registry"

      posted in Xen Orchestra
      B
      bern
    • RE: A lot of not found and error 127 in yarn build

      @Danp yes I did ran yarn first

      posted in Xen Orchestra
      B
      bern
    • A lot of not found and error 127 in yarn build

      I try to build xen orchestra from source by following the procedure at:
      https://xen-orchestra.com/docs/installation.html#from-the-sources

      The command "yarn build" return a lot of "not found" and error 127 as you could see below from the output of "yarn build".

      What could be the problem?

      Thanks

      * xapi-explore-sr:prebuild āˆ’ rimraf dist/
      * xen-api:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xapi-explore-sr:prebuild āˆ’ Error: 127
      * xapi-explore-sr:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      * xen-api:prebuild āˆ’ Error: 127
      * xen-api:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      * xapi-explore-sr:build āˆ’ Error: 127
      * xo-collection:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: cross-env: not found
      * xen-api:build āˆ’ Error: 127
      * xo-import-servers-csv:build āˆ’ tsc
      * xo-collection:prebuild āˆ’ Error: 127
      * xo-collection:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-collection:build āˆ’ Error: 127
      * xo-lib:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-lib:prebuild āˆ’ Error: 127
      * xo-lib:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-lib:build āˆ’ Error: 127
      * xo-remote-parser:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-remote-parser:prebuild āˆ’ Error: 127
      * xo-remote-parser:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-remote-parser:build āˆ’ Error: 127
      * xo-server:build āˆ’ cross-env NODE_ENV=production yarn run _build
      /bin/sh: 1: cross-env: not found
      * xo-server:build āˆ’ Error: 127
      * xo-server-audit:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-audit:prebuild āˆ’ Error: 127
      * xo-server-audit:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-audit:build āˆ’ Error: 127
      * xo-server-auth-github:build āˆ’ NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: babel: not found
      * xo-server-auth-github:build āˆ’ Error: 127
      * xo-server-auth-google:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-auth-google:prebuild āˆ’ Error: 127
      * xo-server-auth-google:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-auth-google:build āˆ’ Error: 127
      * xo-server-auth-ldap:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-auth-ldap:prebuild āˆ’ Error: 127
      * xo-server-auth-ldap:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-auth-ldap:build āˆ’ Error: 127
      * xo-server-auth-saml:prebuild āˆ’ yarn run clean
      * xo-server-auth-saml:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-auth-saml:build āˆ’ Error: 127
      * xo-server-backup-reports:prebuild āˆ’ yarn run clean
      * xo-server-backup-reports:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-backup-reports:build āˆ’ Error: 127
      * xo-server-load-balancer:build āˆ’ NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: babel: not found
      * xo-server-load-balancer:build āˆ’ Error: 127
      * xo-server-netbox:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-netbox:prebuild āˆ’ Error: 127
      * xo-server-netbox:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-netbox:build āˆ’ Error: 127
      * xo-server-perf-alert:prebuild āˆ’ yarn run clean
      * xo-server-perf-alert:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-perf-alert:build āˆ’ Error: 127
      * xo-server-sdn-controller:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-sdn-controller:prebuild āˆ’ Error: 127
      * xo-server-sdn-controller:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-sdn-controller:build āˆ’ Error: 127
      * xo-server-transport-email:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-transport-email:prebuild āˆ’ Error: 127
      * xo-server-transport-email:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-transport-email:build āˆ’ Error: 127
      * xo-server-transport-icinga2:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-transport-icinga2:prebuild āˆ’ Error: 127
      * xo-server-transport-icinga2:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-transport-icinga2:build āˆ’ Error: 127
      * xo-server-transport-nagios:prebuild āˆ’ yarn run clean
      * xo-server-transport-nagios:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-transport-nagios:build āˆ’ Error: 127
      * xo-server-transport-slack:prebuild āˆ’ yarn run clean
      * xo-server-transport-slack:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-transport-slack:build āˆ’ Error: 127
      * xo-server-transport-xmpp:prebuild āˆ’ yarn run clean
      * xo-server-transport-xmpp:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-transport-xmpp:build āˆ’ Error: 127
      * xo-server-usage-report:prebuild āˆ’ yarn run clean
      * xo-server-usage-report:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-usage-report:build āˆ’ Error: 127
      * xo-server-web-hooks:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * xo-server-web-hooks:prebuild āˆ’ Error: 127
      * xo-server-web-hooks:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-server-web-hooks:build āˆ’ Error: 127
      * xo-vmdk-to-vhd:prebuild āˆ’ yarn run clean
      * xo-web:prebuild āˆ’ yarn run clean && index-modules --auto src
      * xo-vmdk-to-vhd:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * xo-vmdk-to-vhd:build āˆ’ Error: 127
      * @xen-orchestra/fs:prebuild āˆ’ yarn run clean
      [08:32:55] Using gulpfile /opt/xen-orchestra/packages/xo-web/gulpfile.js
      [08:32:55] Starting 'clean'...
      [08:32:55] Finished 'clean' after 29 ms
      /bin/sh: 1: index-modules: not found
      * xo-web:prebuild āˆ’ Error: 127
      * xo-web:build āˆ’ GIT_HEAD=$(git rev-parse HEAD) NODE_ENV=production gulp build
      /bin/sh: 1: gulp: not found
      * xo-web:build āˆ’ Error: 127
      * @xen-orchestra/lite:build āˆ’ run-p type-check build-only
      /bin/sh: 1: run-p: not found
      * @xen-orchestra/lite:build āˆ’ Error: 127
      * @xen-orchestra/openflow:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * @xen-orchestra/openflow:prebuild āˆ’ Error: 127
      * @xen-orchestra/openflow:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * @xen-orchestra/openflow:build āˆ’ Error: 127
      * @xen-orchestra/upload-ova:prebuild āˆ’ rimraf dist/
      /bin/sh: 1: rimraf: not found
      * @xen-orchestra/upload-ova:prebuild āˆ’ Error: 127
      * @xen-orchestra/upload-ova:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * @xen-orchestra/upload-ova:build āˆ’ Error: 127
      * @xen-orchestra/fs:build āˆ’ cross-env NODE_ENV=production babel --source-maps --out-dir=dist/ src/
      /bin/sh: 1: cross-env: not found
      * @xen-orchestra/fs:build āˆ’ Error: 127
      āœ– 45
      
      
      posted in Xen Orchestra
      B
      bern