Comments
-
send us some screenshots to document the issue via support@lpar2rrd.com
-
https://xormon.com/welcome-banner.php
-
try this: su - xormon cd xormon-ng/server-nest npx pm2 kill cd .. ./xormon.sh start
-
we have fixed it, send us an email support@xorux.com if you want to have it before June, we will send you a version with the fix.
-
Hi, your right, it should be there but is not. We will add it there, it will be in xormon v2.3.0 (June 2026), thanks for letting us know!
-
upgrade node.js at first https://xormon.com/upgrade-nodejs-v24.php
-
you have to install it on a persistent storage, then specify the path to it in VSP storage properties
-
no, the issue is still open
-
there is still running the agent under lpar2rrd user, keep it running just once, you can add more targets if you want (lpar2rrd server and xormon server if you want) * * * * * /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl <lpar2rrd server> <xormon server> If you want to consolidate under xormon, then this will…
-
send us this via support@xorux.com from the agent side: su - lpar2rrd # or xormon user, depends what user it is running, might be even root(not recommended) crontab -l cd /var/tmp date ps -ef| grep lpar2rrd ls -ltr lpar2rrd* tail lpar2rrd*err tail -1 lpar2rrd*txt # 3 files will be there, use the one without "ps" and "fs"…
-
everything should be here: https://xormon.com/install-cloud.php#IBMCloud I do not know your IBM cloud IP.
-
Hi, yes , we know that only vSAN capacity metrics are available under cluster totals I think. We will add even performance one in next version if anyone helps us with its testing. (we do not have vSAN in our labs and will not have it)
-
upgrade to yesterday's v2.2.10, it is fixed there https://xormon.com/note220.php
-
Latences have been fixed, upgrade to 2.2.10 released just today, we are not aware of problem with Eth inerfaces, we will check it out and let you know
-
df -h mount
-
read this https://xormon.com/data-migration.php
-
yep, XorMon is free with some limitations, same like lpar2rrd, no difference in this
-
UI --> settings --> IBM Power --> HMC --> <select HMC> --> change port to 443 BTW, you might already hear we have a new monitoring tool called XorMon. It's the replacement for LPAR2RRD and STOR2RRD. You can find more information here: https://xormon.com/documentation-ng.php . I recommend testing it out at least, it's a…
-
use the latest XorMon agent (BTW tomorrow will come 8.40 together with XorMon v2.2.0), it works even for lpar2rrd server https://xormon.com/note220.php
-
port 443 is supported for years in lpar2rrd, edit HMC properties in lpar2rrd and set 443 instead 12443, it is all.
-
not yet, it is a complex job, we have to move out from vmware UUIDs are they might not be unique (dues to VM cloning etc) I guess it could be done in 1 month, fee free to ask us then
-
is this working? su apache -s /bin/sh -c "touch /home/lpar2rrd/lpar2rrd/etc/web_config/x" That directory must be writable for apache user
-
this is the issue, you see it: permissions: Read-only file system This output: mount -a BTW, you might already hear we have a new monitoring tool called XorMon. It's the replacement for LPAR2RRD and STOR2RRD. You can find more information here: https://xormon.com/documentation-ng.php . I recommend testing it out at least,…
-
Hi, what it is about exactly? We do performance monitoring even for IBMi, we have the too for it which includes our IBMi agent This sounds like something for IBM support, nothing related to our tools (LPAR2RRD neither XorMon)
-
I believe 10 days
-
as a workaround you can use this procedure cd /home/lpar2rrd/lpar2rrd touch data/Linux/no_hmc/<Linux name>/* ./load.sh html reload the web browser when above cmd finishes, you should see that Linux in the menu again for next 10 days
-
no, as I wrote you, same VM UUIDs in 2 attached vCenters, we have to find some solution for that
-
Send us logs and a screenshot(s) with the problem UI --> Settings --> (Help -->) Logs --> Support Log --> Export All Logs: follow the form Send us generated file via https://upload.xormon.com
-
every AIX TL upgrade can screw Perl dependency, upgrade major version definitely does that. AIX feature .... Send us logs. Note a short problem description in the text field of the upload form. under stor2rrd user (use lpar2rrd user on our virtual appliance) cd `cat ~/.stor2rrd_home` tar cvhf logs.tar logs tmp/*txt gzip -9…
-
rpm -qa| grep httpd 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
Howdy, Stranger!