Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DIE Illegal division by zero at /root/ViPullStatistics.pl line 146. #171

Closed
kamilnew opened this issue Oct 24, 2018 · 16 comments
Closed

DIE Illegal division by zero at /root/ViPullStatistics.pl line 146. #171

kamilnew opened this issue Oct 24, 2018 · 16 comments

Comments

@kamilnew
Copy link

vCSA 6.7 Update 1
[2018/10/23 11:55:35] /root/ViPullStatistics.pl line274 - [INFO] Processing vCenter x.x.x.x cluster xxx datastores in datacenter xxx
[2018/10/23 11:55:36] /root/ViPullStatistics.pl line146 - DIE Illegal division by zero at /root/ViPullStatistics.pl line 146.

got this error in log and graphs have "holes"

bledygraf1
bledygraf2

@rschitz
Copy link
Member

rschitz commented Oct 24, 2018

This will be fix in the next update, could you try this one and let me know https://github.com/sexibytes/sexigraf/blob/dev/root/ViPullStatistics.pl

@kamilnew
Copy link
Author

tried it but it doesnt work - got this in log file

2018/10/24 11:25:10] /usr/local/share/perl/5.20.2/Net/Graphite.pm line120 - WARN Use of uninitialized value $hash in concatenation (.) or string at /usr/local/share/perl/5.20.2/Net/Graphite.pm line 120.
[2018/10/24 11:25:10] /usr/local/share/perl/5.20.2/Net/Graphite.pm line120 - WARN Use of uninitialized value $hash in concatenation (.) or string at /usr/local/share/perl/5.20.2/Net/Graphite.pm line 120.
[2018/10/24 11:25:10] /root/ViPullStatistics.pl line1214 - DIE Can't call method "val" on an undefined value at /root/ViPullStatistics.pl line 1214.

rschitz added a commit that referenced this issue Oct 24, 2018
fix not connected standalone host processing #171
@rschitz
Copy link
Member

rschitz commented Oct 24, 2018

try the last version

@kamilnew
Copy link
Author

now i got this errors in log:
2018/10/24 17:00:11] /root/ViPullStatistics.pl line1219 - WARN Use of uninitialized value $StandaloneResourceVMHostName in string eq at /root/ViPullStatistics.pl line 1219.
[2018/10/24 17:00:11] /root/ViPullStatistics.pl line1226 - DIE Can't call method "val" on an undefined value at /root/ViPullStatistics.pl line 1226.

virtual machines stats are working now
datastores latency and iops dont work at all

@rschitz
Copy link
Member

rschitz commented Oct 24, 2018

@kamilnew
Copy link
Author

now there are no errors in logs but still no datastore data - i think there are datapoints but they are null

@kamilnew
Copy link
Author

can you show me how manually gather information about datastores to check if this values are null because of problem in my environment?

btw. i wish my enterprise products have this quality of support :)

@rschitz
Copy link
Member

rschitz commented Oct 25, 2018

Thanks for your support.
when you said "no datastore data" you talk about local datastores or shared one ? did you ever get data for those?

@kamilnew
Copy link
Author

shared one`s - those from lower screenshot - they were partialy working when i was taking screenshot on older versoin of ViPullStatistics.pl yesterday
i check historic data on sexigraf and i lost iops data at 27th of september , at the same time "holes" in datastore latency appear - this was during vsphere/vsan reconfiguration and that is why i think it may be problem in my environment - try to find anything in logs

@rschitz
Copy link
Member

rschitz commented Oct 25, 2018

holes generally means slow vcenter or too something that takes more than 5min to complete, by sliding pointer on the graphs you should see points but not enough to have lines.
check the Pull Exec Time dashboard to confirm

@kamilnew
Copy link
Author

pull exec look ok - ill try to pull data manually to see what is misiing - im sure that is problem with my environemt - about 40% of datastores have data and 60% dont - thanks for help
pullexec

@kamilnew
Copy link
Author

problem solved - i disabled storage i/o control on several datastores and thats why there was no data

@rschitz
Copy link
Member

rschitz commented Oct 26, 2018

we added "legacy" metrics for the datastores, you should had metrics anyway.

@rschitz
Copy link
Member

rschitz commented Oct 26, 2018

the metric we try first is sizeNormalizedDatastoreLatency which is enable by default now but few version back you had to enable it manually: http://frankdenneman.nl/2013/02/11/how-to-enable-sioc-stats-only-mode/

@kamilnew
Copy link
Author

yes it is enabled by default but i disabled it on purpose month ago - don`t even remember why :) thanks for help

@rschitz
Copy link
Member

rschitz commented Oct 26, 2018

you're welcome, thanks for you support and feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants