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

[MathieuRA]

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

[acebmxer]

@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.

[MathieuRA]

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

[ph7]

@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.

[acebmxer]

@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.

[ph7]

A reboot made the restore list come back
But I also experienced a instability in the V6 backup info
Now it's ok

Still on 9226C

[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.

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)

[ph7]

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

[ph7]

40159
Pool dashboard

VM dashboard

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

[acebmxer]

Pool dashboard the same also...

[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?

[acebmxer]

@MathieuRA

From pool dashboard...

[MathieuRA]

@acebmxer so the endpoint seems to respond correctly.

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