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

    Backup Info under VM tab in v6 never loads...

    Scheduled Pinned Locked Moved Backup
    25 Posts 3 Posters 256 Views 3 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.
    • A Offline
      acebmxer @MathieuRA
      last edited by

      @MathieuRA

      sudo journalctl -u xo-server -n 50
      Mar 27 19:27:10 xo-ce xo-server[55210]: 2026-03-27T19:27:10.657Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'vms'>
      Mar 27 19:27:10 xo-ce xo-server[55210]:   error: TypeError: Cannot read properties of undefined (reading 'vms')
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at BackupLogService.isVmInBackupLog (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/backup-lo>
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at filter (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:228:40)
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at Array.filter (<anonymous>)
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at Xo.getBackupNgLogsSorted (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng-lo>
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.m>
      Mar 27 19:27:10 xo-ce xo-server[55210]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.>
      Mar 27 19:27:10 xo-ce xo-server[55210]: }
      Mar 27 19:27:10 xo-ce xo-server[55210]: 2026-03-27T19:27:10.657Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/das>
      Mar 27 19:27:24 xo-ce xo-server[55210]: 2026-03-27T19:27:24.056Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'vms'>
      Mar 27 19:27:24 xo-ce xo-server[55210]:   error: TypeError: Cannot read properties of undefined (reading 'vms')
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at BackupLogService.isVmInBackupLog (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/backup-lo>
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at filter (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:228:40)
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at Array.filter (<anonymous>)
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at Xo.getBackupNgLogsSorted (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng-lo>
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.m>
      Mar 27 19:27:24 xo-ce xo-server[55210]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.>
      Mar 27 19:27:24 xo-ce xo-server[55210]: }
      Mar 27 19:27:24 xo-ce xo-server[55210]: 2026-03-27T19:27:24.057Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/das>
      Mar 27 19:27:41 xo-ce xo-server[55210]: 2026-03-27T19:27:41.663Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'vms'>
      Mar 27 19:27:41 xo-ce xo-server[55210]:   error: TypeError: Cannot read properties of undefined (reading 'vms')
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at BackupLogService.isVmInBackupLog (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/backup-lo>
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at filter (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:228:40)
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at Array.filter (<anonymous>)
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at Xo.getBackupNgLogsSorted (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng-lo>
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.m>
      Mar 27 19:27:41 xo-ce xo-server[55210]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.>
      Mar 27 19:27:41 xo-ce xo-server[55210]: }
      Mar 27 19:27:41 xo-ce xo-server[55210]: 2026-03-27T19:27:41.663Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/das>
      Mar 27 19:27:55 xo-ce xo-server[55210]: 2026-03-27T19:27:55.046Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'vms'>
      Mar 27 19:27:55 xo-ce xo-server[55210]:   error: TypeError: Cannot read properties of undefined (reading 'vms')
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at BackupLogService.isVmInBackupLog (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/backup-lo>
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at filter (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:228:40)
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at Array.filter (<anonymous>)
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at Xo.getBackupNgLogsSorted (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng-lo>
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.m>
      Mar 27 19:27:55 xo-ce xo-server[55210]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.>
      Mar 27 19:27:55 xo-ce xo-server[55210]: }
      Mar 27 19:27:55 xo-ce xo-server[55210]: 2026-03-27T19:27:55.046Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/das>
      Mar 27 19:28:12 xo-ce xo-server[55210]: 2026-03-27T19:28:12.633Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'vms'>
      Mar 27 19:28:12 xo-ce xo-server[55210]:   error: TypeError: Cannot read properties of undefined (reading 'vms')
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at BackupLogService.isVmInBackupLog (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/backup-lo>
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at filter (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:228:40)
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at Array.filter (<anonymous>)
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at Xo.getBackupNgLogsSorted (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/backups-ng-lo>
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.m>
      Mar 27 19:28:12 xo-ce xo-server[55210]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.>
      Mar 27 19:28:12 xo-ce xo-server[55210]: }
      Mar 27 19:28:12 xo-ce xo-server[55210]: 2026-03-27T19:28:12.633Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/das>
      lines 1-50/50 (END)
      
      MathieuRAM 1 Reply Last reply Reply Quote 0
      • MathieuRAM Online
        MathieuRA Vates 🪐 XO Team @acebmxer
        last edited by

        Hi @acebmxer.
        Can you test on the branch mra-fix-vm-dashboard?

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          acebmxer @MathieuRA
          last edited by acebmxer

          @MathieuRA

          That seemed to work....

          Screenshot 2026-03-30 104123.png

          Screenshot 2026-03-30 104147.png

          Edit - Updated back to master commit. and broken again as expected... So you patched branch works...

          Screenshot 2026-03-30 104516.png

          MathieuRAM 1 Reply Last reply Reply Quote 1
          • MathieuRAM Online
            MathieuRA Vates 🪐 XO Team @acebmxer
            last edited by

            @acebmxer Thanks. We will do our best to merge the fix tomorow

            A 1 Reply Last reply Reply Quote 1
            • A Offline
              acebmxer @MathieuRA
              last edited by

              @MathieuRA

              Dont think you pushed this already unless i am mistaken. But on Commit 9226c

              One vm populates the backup second on dashboard while the other do not. this happens to be the same vm check to confirm your changes. I dont recall if i checked other vms.

              But on Commit 9226c 1 vm dashboard loads correctly.

              MathieuRAM 1 Reply Last reply Reply Quote 0
              • MathieuRAM Online
                MathieuRA Vates 🪐 XO Team @acebmxer
                last edited by MathieuRA

                @acebmxer
                The fix has been deployed to the master branch. Have you encountered any other issues?

                P A 2 Replies Last reply Reply Quote 0
                • P Online
                  ph7 @MathieuRA
                  last edited by

                  @MathieuRA I have
                  I updated to 9226C yesterday
                  but today I discovered problems with restore
                  only one VM of four showing up.
                  I am 2 behind and will update to master now.

                  P 1 Reply Last reply Reply Quote 0
                  • A Offline
                    acebmxer @MathieuRA
                    last edited by

                    @MathieuRA

                    I am guessing i did thoroughly check out your fix against all vms.... Some vms will populate others will not... Here are more of the log info. Let me know if you still need more if this is caused by my script.

                    xo-logs.txt

                    I ran this all through claude code and this is its thoughts...

                    The server logs don't show anything related to the backup spinner, but there are two issues worth addressing:
                    
                    1. Invalid environment assignment (line 11 of the service file)
                    
                    
                    /etc/systemd/system/xo-server.service:11: Invalid environment assignment, ignoring
                    Something in the service file's Environment= or EnvironmentFile= line is malformed. This could be from the install script. Worth checking what's on line 11 of that file.
                    
                    2. PAM limits failures (recurring)
                    
                    
                    pam_limits: Could not set limit for 'nofile' to soft=1024, hard=1048576
                    pam_limits: Could not set limit for 'memlock' to soft=775520256, hard=...
                    The xo user can't set its own resource limits when running sudo. This suggests the systemd LimitNOFILE/LimitMEMLOCK directives in the service file conflict with what PAM is trying to apply.
                    
                    3. listMissingPatches / updater plugin busy — repeated but harmless; XO polls for host patches and races with the xcp-ng updater. Not related to your issue.
                    
                    4. WebSocket ECONNRESET/UND_ERR_SOCKET — normal; long-lived connections to xcp-ng hosts drop and reconnect.
                    
                    None of these explain the backup spinner — that's still a UI/API retrieval bug. But the service file issues are worth fixing. Can you share the output of:
                    
                    
                    cat -n /etc/systemd/system/xo-server.service
                    That'll show exactly what's wrong on line 11, and I can check if the install script is generating it incorrectly.
                    
                    cat -n /etc/systemd/system/xo-server.service
                    
                         1  [Unit]
                         2  Description=Xen Orchestra Server
                         3  After=network-online.target redis.service
                         4  Wants=network-online.target
                         5
                         6  [Service]
                         7  Type=simple
                         8  User=xo-service
                         9
                        10  Environment="NODE_ENV=production"
                        11  WorkingDirectory=/opt/xen-orchestra/packages/xo-server
                        12  ExecStartPre=/bin/mkdir -p /run/xo-server/mounts
                        13  ExecStartPre=/bin/chmod 755 /run/xo-server/mounts
                        14  ExecStart=/usr/bin/node /opt/xen-orchestra/packages/xo-server/dist/cli.mjs
                        15  Restart=always
                        16  RestartSec=10
                        17  SyslogIdentifier=xo-server
                        18
                        19  # Runtime directory
                        20  RuntimeDirectory=xo-server
                        21  RuntimeDirectoryMode=0755
                        22
                        23  # Allow binding to privileged ports (80/443)
                        24  AmbientCapabilities=CAP_NET_BIND_SERVICE
                        25  # Bounding set: ceiling for all processes in this service tree.
                        26  # CAP_NET_BIND_SERVICE: bind to ports 80/443
                        27  # CAP_SETUID/CAP_SETGID/CAP_AUDIT_WRITE: required for sudo to function
                        28  # CAP_SYS_ADMIN: required for mount syscall (NFS/CIFS remotes)
                        29  CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_SETUID CAP_SETGID CAP_SYS_ADMIN CAP_AUDIT_WRITE
                        30
                        31  [Install]
                        32  WantedBy=multi-user.target
                    
                    The current service file looks completely fine — line 11 is WorkingDirectory=... which is valid. The "Invalid environment assignment" warning in the Feb 24 logs was from an older version of the file that has since been fixed (likely by a re-run of your install script).
                    
                    The current file has no issues. All directives are correct:
                    
                    Environment="NODE_ENV=production" — valid syntax
                    CapabilityBoundingSet — looks correct from the recent commit fixes
                    Everything else is standard
                    The PAM limits errors you saw are also unrelated to the service file syntax — those happen because pam_limits tries to apply /etc/security/limits.conf rules when xo-server runs sudo, but systemd's own LimitNOFILE takes precedence and PAM can't override it. This is expected behavior and harmless.
                    
                    Bottom line: The server logs don't reveal any cause for the backup spinner. The spinner is almost certainly this known XO behavior: when the UI subscribes to backup log data for a VM, if the response takes too long or returns in an unexpected format, the loading state never resolves. It's a frontend bug, not a server configuration issue.
                    
                    1 Reply Last reply Reply Quote 0
                    • P Online
                      ph7 @ph7
                      last edited by

                      A reboot made the restore list come back
                      But I also experienced a instability in the V6 backup info
                      Now it's ok
                      Screenshot 2026-03-31 at 12-11-32 Xen Orchestra.png

                      Still on 9226C

                      A P 2 Replies Last reply Reply Quote 0
                      • A Offline
                        acebmxer @ph7
                        last edited by acebmxer

                        @ph7 @mathieura
                        feels like i am sliding down hill.....

                        on latest commit 40179

                        did reboot xo after update.

                        Edit - if i refresh the browser the "Last 3 backup Archives" and "last replication" stop spinning. Also tried in incognito mode to eliminate cookie issues.

                        Screenshot_20260331_062036.png

                        sudo journalctl -u xo-server -n 75
                        Mar 31 10:17:46 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:17:46 xo-ce xo-server[852]: }
                        Mar 31 10:17:46 xo-ce xo-server[852]: 2026-03-31T10:17:46.484Z xo:rest-api:error-handler INFO [GET] /vms/fb72a8d7-a039-849f-b547-24fc56f056ba/dashbo>
                        Mar 31 10:17:48 xo-ce xo-server[852]: 2026-03-31T10:17:48.391Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:17:48 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:17:48 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:17:48 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:17:48 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:17:48 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:17:48 xo-ce xo-server[852]: }
                        Mar 31 10:17:48 xo-ce xo-server[852]: 2026-03-31T10:17:48.391Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/dashbo>
                        Mar 31 10:17:57 xo-ce xo-server[852]: 2026-03-31T10:17:57.455Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:17:57 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:17:57 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:17:57 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:17:57 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:17:57 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:17:57 xo-ce xo-server[852]: }
                        Mar 31 10:17:57 xo-ce xo-server[852]: 2026-03-31T10:17:57.455Z xo:rest-api:error-handler INFO [GET] /vms/b46151e7-690c-9513-126e-3824da2b0ca9/dashbo>
                        Mar 31 10:18:19 xo-ce xo-server[852]: 2026-03-31T10:18:19.646Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:19 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:19 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:19 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:19 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:19 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:19 xo-ce xo-server[852]: }
                        Mar 31 10:18:19 xo-ce xo-server[852]: 2026-03-31T10:18:19.647Z xo:rest-api:error-handler INFO [GET] /vms/24714e97-146f-76f2-699c-bc93116b6a90/dashbo>
                        Mar 31 10:18:34 xo-ce xo-server[852]: 2026-03-31T10:18:34.797Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:34 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:34 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:34 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:34 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:34 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:34 xo-ce xo-server[852]: }
                        Mar 31 10:18:34 xo-ce xo-server[852]: 2026-03-31T10:18:34.797Z xo:rest-api:error-handler INFO [GET] /vms/fb72a8d7-a039-849f-b547-24fc56f056ba/dashbo>
                        Mar 31 10:18:39 xo-ce xo-server[852]: 2026-03-31T10:18:39.691Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:39 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:39 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:39 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:39 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:39 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:39 xo-ce xo-server[852]: }
                        Mar 31 10:18:39 xo-ce xo-server[852]: 2026-03-31T10:18:39.692Z xo:rest-api:error-handler INFO [GET] /vms/fb72a8d7-a039-849f-b547-24fc56f056ba/dashbo>
                        Mar 31 10:18:40 xo-ce xo-server[852]: 2026-03-31T10:18:40.921Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:40 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:40 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:40 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:40 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:40 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:40 xo-ce xo-server[852]: }
                        Mar 31 10:18:40 xo-ce xo-server[852]: 2026-03-31T10:18:40.921Z xo:rest-api:error-handler INFO [GET] /vms/fb72a8d7-a039-849f-b547-24fc56f056ba/dashbo>
                        Mar 31 10:18:42 xo-ce xo-server[852]: 2026-03-31T10:18:42.439Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:42 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:42 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:42 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:42 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:42 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:42 xo-ce xo-server[852]: }
                        Mar 31 10:18:42 xo-ce xo-server[852]: 2026-03-31T10:18:42.439Z xo:rest-api:error-handler INFO [GET] /vms/138538a8-ef52-4d0a-4433-5ebb31d7e152/dashbo>
                        Mar 31 10:18:49 xo-ce xo-server[852]: 2026-03-31T10:18:49.547Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:49 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:49 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:49 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:49 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:49 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:49 xo-ce xo-server[852]: }
                        Mar 31 10:18:49 xo-ce xo-server[852]: 2026-03-31T10:18:49.547Z xo:rest-api:error-handler INFO [GET] /vms/b46151e7-690c-9513-126e-3824da2b0ca9/dashbo>
                        Mar 31 10:18:51 xo-ce xo-server[852]: 2026-03-31T10:18:51.696Z xo:rest-api:error-handler ERROR Cannot read properties of undefined (reading 'status'>
                        Mar 31 10:18:51 xo-ce xo-server[852]:   error: TypeError: Cannot read properties of undefined (reading 'status')
                        Mar 31 10:18:51 xo-ce xo-server[852]:       at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:240:36
                        Mar 31 10:18:51 xo-ce xo-server[852]:       at Array.map (<anonymous>)
                        Mar 31 10:18:51 xo-ce xo-server[852]:       at VmService.#getBackupsInfo (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/vms/vm.service.mjs:>
                        Mar 31 10:18:51 xo-ce xo-server[852]:       at promiseWriteInStream (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/helpers/utils.helper.mjs>
                        Mar 31 10:18:51 xo-ce xo-server[852]: }
                        Mar 31 10:18:51 xo-ce xo-server[852]: 2026-03-31T10:18:51.696Z xo:rest-api:error-handler INFO [GET] /vms/24714e97-146f-76f2-699c-bc93116b6a90/dashbo>
                        lines 36-75/75 (END)
                        

                        Screenshot_20260331_062307.png
                        Screenshot_20260331_062331.png

                        1 Reply Last reply Reply Quote 0
                        • P Online
                          ph7 @ph7
                          last edited by

                          And now its back to only one VM in restore (V5) 9226C
                          Now I will Update to master

                          1 Reply Last reply Reply Quote 0
                          • P Online
                            ph7
                            last edited by

                            40159
                            Pool dashboard
                            Screenshot 2026-03-31 at 12-45-42 Xen Orchestra.png

                            VM dashboard
                            Screenshot 2026-03-31 at 12-46-24 Xen Orchestra.png

                            And V5 only showing 1 VM to restore
                            In the 3 latest tests there has been 3 different VM's shown

                            1 Reply Last reply Reply Quote 0
                            • A Offline
                              acebmxer
                              last edited by

                              Pool dashboard the same also...

                              Screenshot_20260331_065442.png

                              MathieuRAM 1 Reply Last reply Reply Quote 0
                              • MathieuRAM Online
                                MathieuRA Vates 🪐 XO Team @acebmxer
                                last edited by MathieuRA

                                Hi, I'm not sure I understand, let's try to resume.

                                You're both using an up to date master branch and you're both experiencing a problem with a pool dashboard?

                                What is the output of GET /rest/v0/pools/:id/dashboard?

                                A 1 Reply Last reply Reply Quote 0
                                • A Offline
                                  acebmxer @MathieuRA
                                  last edited by

                                  @MathieuRA

                                  From pool dashboard...

                                  Screenshot 2026-03-31 082906.png

                                  Screenshot 2026-03-31 082922.png

                                  Screenshot 2026-03-31 082933.png

                                  MathieuRAM 1 Reply Last reply Reply Quote 0
                                  • MathieuRAM Online
                                    MathieuRA Vates 🪐 XO Team @acebmxer
                                    last edited by

                                    @acebmxer so the endpoint seems to respond correctly.

                                    Can you confirm that the pool dashboard UI is still displaying infinite loaders?

                                    P 1 Reply Last reply Reply Quote 0
                                    • P Online
                                      ph7 @MathieuRA
                                      last edited by

                                      @MathieuRA Yes, still spinning
                                      2h since reboot of XO-vm

                                      MathieuRAM 1 Reply Last reply Reply Quote 0
                                      • MathieuRAM Online
                                        MathieuRA Vates 🪐 XO Team @ph7
                                        last edited by

                                        @ph7 Can you open your browser's console, go to the network tab, find the call to the endpoint rest/v0/pools/:id/dashboard and paste the result here?

                                        1 Reply Last reply Reply Quote 0

                                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                        With your input, this post could be even better 💗

                                        Register Login
                                        • First post
                                          Last post