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

    XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702

    Scheduled Pinned Locked Moved Xen Orchestra
    18 Posts 2 Posters 149 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.
    • D Offline
      DustinB @HH
      last edited by

      @HH I am Jarli01

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DustinB @DustinB
        last edited by

        For what it's worth, I just updated my XOCE installation and everything is working without issue.

        a524ba76-b8c2-48a8-94c2-e7b8606111c1-image.png

        Try updating with sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f

        H 1 Reply Last reply Reply Quote 0
        • H Offline
          HH @DustinB
          last edited by

          @DustinB
          root@as-xoce:~# sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
          % Total % Received % Xferd Average Speed Time Time Time Current
          Dload Upload Total Spent Left Speed
          100 6489 100 6489 0 0 28724 0 --:--:-- --:--:-- --:--:-- 28840
          copying : node/22.17.1
          installed : v22.17.1 (with npm 10.9.2)
          Stopping xo-server...
          Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
          Checking for Yarn package...
          Checking for Yarn update...
          Paketlisten werden gelesen… Fertig
          Abhängigkeitsbaum wird aufgebaut… Fertig
          Statusinformationen werden eingelesen… Fertig
          yarn ist schon die neueste Version (1.22.22-1).
          0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
          Checking for missing dependencies...
          Checking for Repo change...
          Checking xen-orchestra...
          Current branch master
          Current version 5.181.0 / 5.178.0
          Current commit e5702e407c728f3e56b30a6448f9849ad303a562 2025-07-18 16:21:14 +0200
          0 updates available
          Updating from source...
          No local changes to save
          No stash entries found.
          Already up to date.
          Clearing directories...
          Installing...
          yarn install v1.22.22
          [1/5] Validating package.json...
          [2/5] Resolving packages...
          success Already up-to-date.
          $ husky install
          husky - Git hooks installed
          Done in 1.31s.
          yarn run v1.22.22
          $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
          ╭──────────────────────────────────────────────────────────────────────────╮
          │ │
          │ Update available v2.5.0 ≫ v2.5.5 │
          │ Changelog: https://github.com/vercel/turborepo/releases/tag/v2.5.5 │
          │ Run "npx @turbo/codemod@latest update" to update │
          │ │
          │ Follow @turborepo for updates: https://x.com/turborepo │
          ╰──────────────────────────────────────────────────────────────────────────╯
          turbo 2.5.0

          • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
          • Running build in 22 packages
          • Remote caching disabled

          Tasks: 30 successful, 30 total
          Cached: 30 cached, 30 total
          Time: 2.035s >>> FULL TURBO

          Done in 2.27s.
          Updated version 5.181.0 / 5.178.0
          Updated commit e5702e407c728f3e56b30a6448f9849ad303a562 2025-07-18 16:21:14 +0200
          Checking plugins...
          Ignoring xo-server-test plugin
          Cleanup plugins...
          Restarting xo-server...

          INFO:
          root@as-xoce:~# turbo --version
          2.5.5
          root@as-xoce:~#
          a4d46a8b-8027-4300-99b6-16f48b6d37ba-grafik.png

          Hat nichts gebracht... 😞

          H 1 Reply Last reply Reply Quote 0
          • H Offline
            HH @HH
            last edited by HH

            Es gab laut Weboberfläche wieder Updates...
            1aa150ee-4126-4f24-aa4a-7bade37770a9-Bildschirmfoto vom 2025-07-22 10-41-10.png /home/helmut/Bilder/Bildschirmfotos/Bildschirmfoto vom 2025-07-22 10-41-10.png

            34e9be87-8ad8-40ee-8be9-1f6e0acf9087-Bildschirmfoto vom 2025-07-22 10-43-22.png /home/helmut/Bilder/Bildschirmfotos/Bildschirmfoto vom 2025-07-22 10-43-22.png

            Nach Update:
            dabf333e-aa7c-4058-90c4-71fafa39319d-grafik.png
            Warum erkennt er die Updates nicht ?
            Er sagt auch immer turbo nicht Aktuell, bei Versions Abfrage kommt aber 2.5.5.
            Hat jemand eine Idee was hier nicht passen könnte ?

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              DustinB @HH
              last edited by

              @HH It might be worth checking the logs, journalctl -u xo-server -f -n 50

              If nothing stands out still, you can always export your configuration file for XOCE, build a new installation on a new VM and import the configuration.

              For what it's worth, I don't see anything standing out with what has been provided.

              H 1 Reply Last reply Reply Quote 0
              • H Offline
                HH @DustinB
                last edited by

                @DustinB said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                journalctl -u xo-server -f -n 50

                Weisst du was das bedeutet:
                Jul 22 08:45:47 as-xoce xo-server[887]: at process.callbackTrampoline (node:internal/async_hooks:130:17)
                Jul 22 08:45:47 as-xoce xo-server[887]: }
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-ldap
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-github
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-google
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-saml
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-oidc
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register netbox
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-icinga2
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register test-plugin
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-nagios
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-slack
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register backup-reports
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register load-balancer
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-email
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register audit
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register perf-alert
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register transport-xmpp
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register web-hooks
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.749Z xo:plugin INFO successfully register usage-report
                Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.861Z xo:plugin INFO successfully register sdn-controller
                Jul 22 09:03:45 as-xoce xo-server[887]: (node:887) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
                Jul 22 09:03:45 as-xoce xo-server[887]: (Use node --trace-deprecation ... to show where the warning was created)
                Jul 22 09:03:45 as-xoce xo-server[887]: 2025-07-22T09:03:45.700Z xo:xo-server WARN Node warning {
                Jul 22 09:03:45 as-xoce xo-server[887]: error: DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
                Jul 22 09:03:45 as-xoce xo-server[887]: at IncomingMessage.flash (/opt/xen-orchestra/node_modules/connect-flash/lib/flash.js:67:16)
                Jul 22 09:03:45 as-xoce xo-server[887]: at file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:322:11
                Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                Jul 22 09:03:45 as-xoce xo-server[887]: at Xo._handleHttpRequest (file:///opt/xen-orchestra/packages/xo-server/src/xo.mjs:173:7)
                Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                Jul 22 09:03:45 as-xoce xo-server[887]: at initialize (/opt/xen-orchestra/node_modules/passport/lib/middleware/initialize.js:98:5)
                Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                Jul 22 09:03:45 as-xoce xo-server[887]: at urlencodedParser (/opt/xen-orchestra/node_modules/body-parser/lib/types/urlencoded.js:94:7)
                Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13) {
                Jul 22 09:03:45 as-xoce xo-server[887]: code: 'DEP0044'
                Jul 22 09:03:45 as-xoce xo-server[887]: }
                Jul 22 09:03:45 as-xoce xo-server[887]: }

                H D 2 Replies Last reply Reply Quote 0
                • H Offline
                  HH @HH
                  last edited by

                  Habe das jetzt gemacht:
                  root@as-xoce:~# sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -b next-release
                  % Total % Received % Xferd Average Speed Time Time Time Current
                  Dload Upload Total Spent Left Speed
                  100 6489 100 6489 0 0 22982 0 --:--:-- --:--:-- --:--:-- 23010
                  copying : node/22.17.1
                  installed : v22.17.1 (with npm 10.9.2)
                  Stopping xo-server...
                  Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
                  Checking for Yarn package...
                  Checking for Yarn update...
                  Paketlisten werden gelesen… Fertig
                  Abhängigkeitsbaum wird aufgebaut… Fertig
                  Statusinformationen werden eingelesen… Fertig
                  yarn ist schon die neueste Version (1.22.22-1).
                  0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
                  Checking for missing dependencies...
                  Checking for Repo change...
                  Checking xen-orchestra...
                  Current branch master
                  Current version 5.181.0 / 5.178.0
                  Current commit a9789ba6301f60ab839b2329bcd95c15d1989649 2025-07-22 10:09:54 +0200
                  Switching to branch 'next-release'...
                  No stash entries found.
                  error: pathspec 'next-release' did not match any file(s) known to git
                  1 updates available
                  Updating from source...
                  No stash entries found.
                  Updating a9789ba63..6b172f704
                  Fast-forward
                  .github/ISSUE_TEMPLATE/bug_report.yml | 4 ++--
                  @xen-orchestra/lite/src/views/xoa-deploy/XoaDeployView.vue | 12 ++++++------
                  docs/docs/architecture.md | 2 +-
                  packages/xo-server-audit/.USAGE.md | 2 +-
                  packages/xo-server-sdn-controller/.USAGE.md | 2 +-
                  packages/xo-server-sdn-controller/README.md | 2 +-
                  packages/xo-server-test/_xoConnection.mjs | 2 +-
                  packages/xo-server-transport-xmpp/README.md | 2 +-
                  packages/xo-web/src/xo-app/about/index.js | 4 ++--
                  packages/xo-web/src/xo-app/backup/new/index.js | 2 +-
                  packages/xo-web/src/xo-app/home/index.js | 2 +-
                  11 files changed, 18 insertions(+), 18 deletions(-)
                  Clearing directories...
                  Installing...
                  yarn install v1.22.22
                  [1/5] Validating package.json...
                  [2/5] Resolving packages...
                  success Already up-to-date.
                  $ husky install
                  husky - Git hooks installed
                  Done in 1.40s.
                  yarn run v1.22.22
                  $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
                  ╭──────────────────────────────────────────────────────────────────────────╮
                  │ │
                  │ Update available v2.5.0 ≫ v2.5.5 │
                  │ Changelog: https://github.com/vercel/turborepo/releases/tag/v2.5.5 │
                  │ Run "npx @turbo/codemod@latest update" to update │
                  │ │
                  │ Follow @turborepo for updates: https://x.com/turborepo │
                  ╰──────────────────────────────────────────────────────────────────────────╯
                  turbo 2.5.0

                  • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
                  • Running build in 22 packages
                  • Remote caching disabled

                  Tasks: 30 successful, 30 total
                  Cached: 26 cached, 30 total
                  Time: 1m11.856s

                  Done in 72.71s.
                  Updated version 5.181.0 / 5.178.0
                  Updated commit 6b172f7047447c9b12ff588bed1e9f19ae3fc0eb 2025-07-22 11:19:12 +0200
                  Checking plugins...
                  Ignoring xo-server-test plugin
                  Cleanup plugins...
                  Restarting xo-server...
                  root@as-xoce:~#

                  Und warum geht es jetzt ?
                  385abc13-7572-43ba-8705-968e072ea1b4-grafik.png

                  H 1 Reply Last reply Reply Quote 0
                  • H Offline
                    HH @HH
                    last edited by

                    Das gibt es doch nicht, was passiert hier ?
                    1e19b1ce-c747-4229-a815-63fac8654825-grafik.png
                    cfc11402-7546-4468-9c9c-69818923be73-grafik.png
                    Jetzt geht es schon wieder nicht ?
                    Liegt das wicrklich an meinem Server ?

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      DustinB @HH
                      last edited by

                      @HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                      @DustinB said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                      journalctl -u xo-server -f -n 50

                      Weisst du was das bedeutet:
                      Jul 22 08:45:47 as-xoce xo-server[887]: at process.callbackTrampoline (node:internal/async_hooks:130:17)
                      Jul 22 08:45:47 as-xoce xo-server[887]: }
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-ldap
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-github
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.714Z xo:plugin INFO successfully register auth-google
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-saml
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register auth-oidc
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register netbox
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-icinga2
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register test-plugin
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-nagios
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-slack
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register backup-reports
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register load-balancer
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.715Z xo:plugin INFO successfully register transport-email
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register audit
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register perf-alert
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register transport-xmpp
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.734Z xo:plugin INFO successfully register web-hooks
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.749Z xo:plugin INFO successfully register usage-report
                      Jul 22 08:45:47 as-xoce xo-server[887]: 2025-07-22T08:45:47.861Z xo:plugin INFO successfully register sdn-controller
                      Jul 22 09:03:45 as-xoce xo-server[887]: (node:887) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
                      Jul 22 09:03:45 as-xoce xo-server[887]: (Use node --trace-deprecation ... to show where the warning was created)
                      Jul 22 09:03:45 as-xoce xo-server[887]: 2025-07-22T09:03:45.700Z xo:xo-server WARN Node warning {
                      Jul 22 09:03:45 as-xoce xo-server[887]: error: DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
                      Jul 22 09:03:45 as-xoce xo-server[887]: at IncomingMessage.flash (/opt/xen-orchestra/node_modules/connect-flash/lib/flash.js:67:16)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at file:///opt/xen-orchestra/packages/xo-server/src/index.mjs:322:11
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Xo._handleHttpRequest (file:///opt/xen-orchestra/packages/xo-server/src/xo.mjs:173:7)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at initialize (/opt/xen-orchestra/node_modules/passport/lib/middleware/initialize.js:98:5)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at /opt/xen-orchestra/node_modules/express/lib/router/index.js:286:9
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Function.process_params (/opt/xen-orchestra/node_modules/express/lib/router/index.js:346:12)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at next (/opt/xen-orchestra/node_modules/express/lib/router/index.js:280:10)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at urlencodedParser (/opt/xen-orchestra/node_modules/body-parser/lib/types/urlencoded.js:94:7)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at Layer.handle [as handle_request] (/opt/xen-orchestra/node_modules/express/lib/router/layer.js:95:5)
                      Jul 22 09:03:45 as-xoce xo-server[887]: at trim_prefix (/opt/xen-orchestra/node_modules/express/lib/router/index.js:328:13) {
                      Jul 22 09:03:45 as-xoce xo-server[887]: code: 'DEP0044'
                      Jul 22 09:03:45 as-xoce xo-server[887]: }
                      Jul 22 09:03:45 as-xoce xo-server[887]: }

                      Nothing appears to be wrong here

                      @HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                      Current commit a9789ba6301f60ab839b2329bcd95c15d1989649 2025-07-22 10:09:54 +0200
                      Switching to branch 'next-release'...
                      No stash entries found.

                      I'm assuming you're using the "Stable" branch, but maybe not. Take a look at my github on how to check what channel to be on.

                      @HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                      Is this really due to my server?

                      Possibly....

                      H 1 Reply Last reply Reply Quote 0
                      • H Offline
                        HH @DustinB
                        last edited by

                        @DustinB
                        Verstehe ich es richtig:
                        Mit diesem Scribt frage ich den "Stable Channel" ab ?
                        sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -n stable

                        Mit welchem Befehl kann ich den eingestellten "Channel" abfragen ?

                        Habe normalerweise(vor der Fehler kam), diesen Befehl benützt:
                        sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash

                        D 1 Reply Last reply Reply Quote 0
                        • D Offline
                          DustinB @HH
                          last edited by

                          @HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                          udo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -n stable

                          correct, this will put you on the "stable" release of XO from Source.

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

                          Would work for a properly running instance, but you may have changed at some point to "next-release"

                          H 1 Reply Last reply Reply Quote 0
                          • H Offline
                            HH @DustinB
                            last edited by

                            @DustinB
                            Ja, habe halt getestet mit:
                            sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -b next-release
                            War er dann Up to date...
                            Was muss ich machen, das das wieder korrekt funktioniert ?
                            Was muss man machen wenn XO von Version 5.x auf 6.x geht ?

                            D 1 Reply Last reply Reply Quote 0
                            • D Offline
                              DustinB @HH
                              last edited by

                              @HH Just follow the documented steps in the updater github, since 6.0 hasn't been fully released yet there isn't anything special to it.

                              H 1 Reply Last reply Reply Quote 0
                              • H Offline
                                HH @DustinB
                                last edited by

                                @DustinB
                                Meinst du diese Seite:
                                https://github.com/Jarli01/xenorchestra_updater
                                Das habe ich alles so gemacht..

                                since 6.0 hasn't been fully released yet there isn't anything special to it.
                                Ich meinte nicht, das ich jetzt auf 6.0 möchte, sondern wenn 6.0 "Stable LTS" wird, get das automatisch mit deinem Skript ?
                                sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash
                                Oder was muss man tun, wenn es soweit ist ?

                                D 1 Reply Last reply Reply Quote 0
                                • D Offline
                                  DustinB @HH
                                  last edited by

                                  @HH said in XO Commuity Edition Xen Orchestra, commit fee7b geht nicht auf Master, commit e5702:

                                  I didn't mean that I want to go to 6.0 now, but when 6.0 becomes "Stable LTS", get that automatically with your script ?

                                  Assuming there aren't any major changes to the upgrading processing using the existing script should work, but that has to be determined once a general release is created.

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