Pavel

send us joblog of these jobs support at lpar2rrd dot com

from xormon NG host: telnet <vcenter name> 443

it is not about vCenter version. looks like a network problem, connection to the vcenter is filtered on a firewall, contact your security department ... and open: Xormon NG --> vcenter:443 TCP

Hi, it is not needed anymore, just removed that from the docu. Thanks

upgrade to this version, it is fixed there https://download.xormon.com/ng/xormon-ng-1.6.6.tar.gz

Hi, support basic auth in browsers as you know use LDAP/AD authorization in lpar2rrd, in fact it is about Apache setting, not a nice method but it works for some users. I know, it is again about modifying apache settings https://lpar2rrd.com/ldap.php perferable way: use our brand new tool called XorMon Next Generation, it…

Hi, ok, your right, there will be new version which fixes a few issues released today/tomorrow, we will include into that even this one. Thanks for spotting it.

Hi Franck, send us logs, we will check it UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com

Hi, send us logs, perhaps some minor corruption due to filesystem was full. Note a short problem description in the text field of the upload form. cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir tar cvhf logs.tar logs tmp/*txt gzip -9 logs.tar Send us logs.tar.gz via https://upload.stor2rrd.com

Hi, no way to migrate perf data from stor2rrd to Xormon NG you can however collect data simultaneously, then switch off old stor2rrd when you want, when you have enough of hist data in the new tool. https://xormon.com/data-migration.php stor2rrd to storr2rd data migration:…

it will be ok

on the agent side

tail /var/tmp/lpar2rrd-agent-xorux-lpar2rrd.err

on the agent side: su - lpar2rrd date crontab -l ls -ltr /var/tmp/lpar*|tail ps -ef| grep lpar2rrd

send us gzipped cpu.mm https://upload.lpar2rrd.com

we do not see such behaviour in our labs, can you upgrade on the latest build? https://download.xormon.com/ng/xormon-ng-1.5.24.tar.gz (docker one: https://download.xormon.com/docker/xormon-ng-docker-1.5.24.tar.gz ) https://xormon.com/xormon-upgrade.php

yep, this is a prerequisite noted on our web pages in the install docu

upgrade to 7.9x and let us know if the issue persist

can you upgrade once more to this version? https://www.lpar2rrd.com/download-temp/lpar2rrd-7.92-5.tar If no data in next 1 - 2 hours then send us logs Note a short problem description in the text field of the upload form. cd /home/lpar2rrd/lpar2rrd # or where is your LPAR2RRD working dir tar cvhf logs.tar logs tmp/*txt…

are you at the latest stor2rrd v7.9x? If so, send us logs Note a short problem description in the text field of the upload form. cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir tar cvhf logs.tar logs tmp/*txt gzip -9 logs.tar Send us logs.tar.gz via https://upload.stor2rrd.com

try to upgrade to this version, let us know if the problem persists https://www.lpar2rrd.com/download-temp/lpar2rrd-7.92-4.tar upgrade docu: https://lpar2rrd.com/upgrade.php

but where do you get or see that error? I got no idea. It is not in the UI, it looks like a cmd loine error, but what program generates it? Where did you fin it. Is working connection test: UI --> settings --> Stofage --> your cohesity alias --> connection test

Does the connection test working: UI --> settings --> RHV --> select the management station --> copnnection test If it woks, then send us logs Note a short problem description in the text field of the upload form. cd /home/lpar2rrd/lpar2rrd # or where is your LPAR2RRD working dir tar cvhf logs.tar logs tmp/*txt tmp/*json…

what exactly do you run? connection test from cmd line or UI?

the best would be providing us some screenshot(s) and logs, both via the upload form, we will check it and let you know. Note a short problem description in the text field of the upload form. cd /home/lpar2rrd/lpar2rrd # or where is your LPAR2RRD working dir tar cvhf logs.tar logs tmp/*txt tmp/*json gzip -9 logs.tar Send…

Hi, logs will not be shared anywhere, just internal emploees will have access to them for troubleshooting purposes.

and this causes the agent to exit with uncorrrectly? No ... what happens when you make the change you suggested, any difference in cronlog?

is there any problem with WLM data? Do you see WLM graphs under lpar2rrd UI?

hot fix: rm tmp/menu_vmware*; ./load.sh html or upgrade to: https://www.lpar2rrd.com/download-tmp/mpibov/lpar2rrd-7.91-4.tar

then send logs