Comments
-
here is the docu how to do it: just set https in Apache, it is all, check Google how to set https in your Apache version. 1. install mod_ssl package or make sure it is already installed # dnf install mod_ssl # rpm -qa| grep ssl mod_ssl-2.4.18-1 2. edit httpd.conf and include conf/extra/httpd-ssl.conf into Apache cfg (use…
-
execute that under lpar2rrd user
-
send us logs Note a short problem description in the text field of the upload form. under lpar2rrd user: cd `cat ~/.lpar2rrd_home` gzip -9 logs.tar Send us logs.tar.gz via https://upload.lpar2rrd.com
-
Alletra MP is supported only in our newer product called XorMon Next Generation (stor2rrd modern replacement) https://xormon.com/storage/monitoring/HPE/HPE-3PAR-MSA-XP7-NIMBLE-StoreOnce-monitoring.php It is not going to be back-ported to stor2rrd so far.
-
what is your stor2rrd version? Let me check if we support it, it is for sure supported in our new modern stor2rrd replacement XorMon NG
-
https://xormon.com/storage/monitoring/iXsystems/FreeNAS-TrueNAS-monitoring.php --> FreeNAS v24.10+ the storage API has changed, it will be supported since XorMon NG v2.0.0. We can provide you a build with its support if you want
-
ok, BTW our new product XorMon NG (stor2rrd/lpar2rrd modern replacement) does not suffer for such issue for sure.
-
Hi, is not there any special character in the name of volume like ":" or similar?
-
we could just provide some CLI based cmds to remove that particular peak
-
Hi, we do not know how to do it apart of removing peak data (automatically??) but then we will not present any peak. How to define such peak for removal? It could be different for every device, metric ... no way to do it automatically. perhaps to enable users to remove selected data ion their own ... we do not see a way…
-
no, use XorMon NG (LPAR2RRD modern successor) which does that and many more https://xormon.com/error-log-monitoring.php
-
Send us logs and screenshot from CPU OS graph. Note a short problem description in the text field of the upload form. under lpar2rrd user: cd `cat ~/.lpar2rrd_home` gzip -9 logs.tar Send us logs.tar.gz via https://upload.lpar2rrd.com
-
Hi 1.logs Send us logs: UI --> Settings --> Logs --> Support Logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls. 2.send also some screenshot via upload form to see storage name and volume which are missing
-
send us logs UI --> Settings --> Logs --> Support Logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
You must use Timescale community edition how is noted in the docu
-
is that about Xormon Original (lpar2rrd/stor2rrd app front-end) or Xormon Next Generation (NG)?
-
Send us logs: UI --> Settings --> Logs --> Support Logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
send us logs UI --> Settings --> Logs --> Support Logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
then ignore it if you get data in graphs
-
you can have whatever you want TZ in the HMC, just reboot the HMC after each change.
-
this is caused by not rebooting the HMC after the time zone change. It also happens after the HMC upgrade. reboot the the HMC, it should be ok after that.
-
is connection test ok? UI --> settings --> devices --> storage --> connection test for that storage Are you at the latest xormon 1.9.5, if not, upgrade at first if 1 + 2 are fine, send us log UI --> Settings --> Logs --> Support Logs: follow the form Send us generated file…
-
under root: rm /var/tmp/lpar2rrd-agent.out Then it will run, problem is you run it under root some time (test??) and output file is same, lpar2rrd user cannot write to that file, so exiting on its start
-
su - lpar2rrd crontab -l date ls -ltr /var/tmp tail /var/tmp/lpar*err
-
well, 8.10 is intended for XorMon NG, there are special enhancements (LVM info, errpt log ...) for it but generally it should work with LPAR2RRD server even older versions send us via support@xorux.com : ls -ltr /var/tmp/lpar* and logs from the lpar2rrd server Note a short problem description in the text field of the…
-
use rest api: https://xormon.com/public-api.php
-
we use volume ID as a unique key for storing in the database. When 2 items have same unique key then just one is saved, that is why you cannot see both volumes. No easy solution here, it would have to be re-designed all volumes data storing, through away all volumes data and create some other unique key based on volume id…
-
how 2 different volumes on different storage devices can share same volume ID? We expect that volume ID is ALWAYS unique.
-
send us logs and a few screenshots to document the issue (attach even screenshot from storage connection test) UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
above "volume id" in stor2rrd does not seem to be regular volume id used for host mapping purposes, that is perhaps why xormon NG does not show it, we will analyze it and let you know more info later on
Howdy, Stranger!