alfcruz

Oh, thank you for this patch. Only saw it today, as I had the news that lpar was updated to 7.30. Thank you!

The particular SR that gives problems when graphing (disk-aba8434e) , is not listed into the configuration > storage tab.

Reporting again, the Configuration > Storage tab tables show greatly detailed information. For each xcp-ng host there is a line containing an particular xcp-ng storage resource and it contained VDI (volume). Since we use all the production vms into shared storage resources, I'd find more useful to group data for each…

Reporting back, the specific storage the gives the error in the above picture, have rrd files under some of the xcp-ng hosts directories (there are 7 hosts/dirs), but not all of them. Different files, with the same names.

Hi David, thank you for helping me. We consider iso performance of less interest than the storage resources that contain vms. We only use isos to install lguest utilities and store files used in the vm installation process, so is a little percent of use compared to production. I'll try to configure as you told me to do.…

Is there an easy way to avoid the guest tools ISO file to be entered into the storage resources data collection or in the graph data plot under pool's storage resources?

Hi David! The patch does work! Thanks! Some graphs do not show, and I'll try later in the day. One of interest to me is storage activity. That fails, I think, because the guest tools file in /opt/xensource/iso/guest-tools-8.2.0-2.xcpng8.2.iso [12:15 uaaxcpngp01h01 ~]# xe sr-list…

Please, let me know if I could be of any help, to test anything, or provide new data. Thank you.

I use XCP-ng version 8.2 LTS. Thank you.

Hi David. You found it - the file is almost empty. Contains only {} on a line by itself. Do you know how I can properly config this file, please?

In this same CentOS VM, named Ohm, I run stor2rrd com great success. Many years now.

[root@ohm lpar2rrd]# find . -name menu_xenserver.json[root@ohm lpar2rrd]# find . -name menu*.json[root@ohm lpar2rrd]# find . -name…

[root@ohm logs]# tail -30 error.log-xenXenServer XAPI2JSON: 0 timeouted.Wed Jul 7 08:28:23 -03 2021: There is already running another copy of load_xenserver.sh, exiting ...""XenServer XAPI2JSON: 0 timeouted.XenServer XAPI2JSON: 0 timeouted.XenServer XAPI2JSON: 0 timeouted.XenServer XAPI2JSON: 0 timeouted.XenServer…

Some data/info more... [lpar2rrd@ohm lpar2rrd]$ ll -a etctotal 248drwxr-xr-x 4 lpar2rrd lpar2rrd 4096 Jul 6 15:48 .drwxr-xr-x. 20 lpar2rrd lpar2rrd 4096 Jul 6 16:00 ..-rw-r--r-- 1 lpar2rrd lpar2rrd 930 Jun 10 09:54 alias.cfg-rw-r--r-- 1 lpar2rrd lpar2rrd 26381 Jun 10 09:54 dbinit.sql-rw-r--r-- 1 lpar2rrd lpar2rrd 22663 Jun…

Hello, David! All 7 connection testes give feedback similar to the picture below. --//-- load_xenserver.sh appears to be collecting data, as the rrd files are being created, as the following directory listing example. [lpar2rrd@ohm lpar2rrd]$ ll -Rh data/XEN*data/XEN:total 28Kdrwxr-xr-x. 2 lpar2rrd lpar2rrd 4.0K Jul 1…