SR stats show “No stats” in Xen Orchestra after latest XCP-ng 8.3 patches

rtjdamen

Hi,

We have been running XCP-ng 8.3 for some time already, but after deploying the latest XCP-ng 8.3 patches, Storage → Stats in Xen Orchestra no longer shows any statistics for our SRs.
The page only displays “No stats”.

Key points:
• This started after installing the most recent 8.3 updates, not immediately after upgrading to 8.3
• The issue affects SR stats only
• Host and VM stats are displayed correctly
• Storage itself is fully functional (VMs running, space usage correct)
• SR status is Connected (not partially connected)

Anyone familiar with this issue?
Robin

olivierlambert

Hi,

Are you using QCOW2?

rtjdamen

@olivierlambert no we are using normal shared storage woth regular vdi we see this on all shared storage types nfs and iscsi

olivierlambert

Hmm it doesn't ring a bell to me. I would suggest to open a ticket in parallel so someone could take a look on next week

rtjdamen

@olivierlambert yes i will! I think it has to do with the poolmaster not getting the right information from all the slaves but maybe i am wrong. We detached one host this morning because of a broken mainboard so maybe the clue is there but maybe support can help!

Pilow

@rtjdamen hey there,

did you ever modify in the POOL advanced tab at the bottom the BACKUP network & MIGRATION network ?

fiddle with these, note what they are actually set, and change them if possible
between each change, check your SR stats

@florent could explain better how SR stats use the backup network to get the RRDs...

I guess you have stalled RRD tasks too ? in tasks list ?

florent

@Pilow
the rrd ( the stats ) use the same code path as the backup . I am not sure if it's a feature or a bug, but at least it's a good canary

the data volume of stats can be quite huge and have an impact on management. So it's a little justifiable to use the same network for backup and stats, at least until we can separate things more clealy .
At least it helps a lot to check if the network is really reachable (sometimes because of third party filtering or ip configuration error , other to the xoa missing some network), and the downside is not to dangerous.