Comments
-
As expected there is no data in xormon either. (Finally logged into that to verify if there is anything there either). It looks based on what I have favorited on the Dashboard that there is data getting loaded just don't have a way to look at the individual esx systems. I am thinking that this may be related to updating…
-
Results: [lpar2rrd@ant-nagios ~]$ ls -l /var/www/html/lpar2rrd/lpar2rrd/tmp/*pid -rw-r--r-- 1 lpar2rrd lpar2rrd 5 Jun 15 05:30 /var/www/html/lpar2rrd/lpar2rrd/tmp/custom.pid -rw-r--r-- 1 lpar2rrd lpar2rrd 5 Jun 15 05:20 /var/www/html/lpar2rrd/lpar2rrd/tmp/load_aws.sh.pid -rw-r--r-- 1 lpar2rrd lpar2rrd 5 Jun 15…
-
So upgrade the SDK to 7.0 also and still nothing showing anything other then the data stores. I have dropped vcsa and readded it back and still do not get anything. Would like to see if anyone has any ideas.
-
So I had a stored clone of this system and it is evidencing the same issue on 7.10. I did upgrade my VCSA to 7.02 due to the known security issues. Do I need to upgrade the SDK to match the vcsa version?
-
Looks like there is a difference in level of stupid of chrome vs firefox. I can resize things in Chrome but not in FF. I will play with is some more and see if I can come up with a more reproducible set of conditions
-
So that worked!! thanks. Now on to the other issue that I have but I will open another Discussion item about that.
-
after dealing with support this is corrected. Hopefully overall they will issue a point release to sort this for everyone. Thanks to the team for the fix.
-
Looks like you may need to do a: yum install perl-Want to get that module; [root@~]# locate *.pm|grep Want/usr/lib64/perl5/Want.pm[root@~]# rpm -q --whatprovides /usr/lib64/perl5/Want.pmperl-Want-0.18-4.el6.x86_64 I would start with that.
-
Per the email I sent, I am wondering if it is stopping with the 1st storage that I can't map the SAN ports for. There are a few storwize that I do not monitor the SAN switches for and those are the ones that I think it is hung up on. Matthew
-
Email sent. This is not pervasive across all the storage that I have but the first 4 seem to be ok for it then the rest don't present. SAN is monitored and responds/graphs appropriately.
-
At the time it didn't. I actually had to delete and recreate the user in the vcsa to get it to work. It appears that the VCSA has a 90 day reset on the password that there is no way to bypass and once it hits lockout mode you play hell trying to get it to be fixed. The lpar2rrd instances where connecting to 2 separate…
-
Pavel, Thanks, I thought that I was on 1.35-1 but wasn't and you are correct that fixed it on the first iterative. This is a great product and it has been a hit with us. Matthew
Howdy, Stranger!