Hi Team,
We are monitoring our vcentre servers using Vmware Virtualization wizard with the help of box 293 plugin. Below is the status of memory usage for a vcentre servr:
CRITICAL: 'Cluster 1' Memory {Free: -0.899,999,999,999,999 GB (CRITICAL <= 4.79)} {Used: 40.6 GB} {Effective: 39.7 GB} {Total: 47.9 GB}
Here if you see, the total memory is 47.9 GB. But, Nagios is checking something called Effective memory and is giving critical state after comparing threshold value with the same.
We are expecting it to check total memory and not effective memory.
Could you please help us to get this done?
I am attaching the service definition, command definition and service screenshot here.
Thanks in advance!!
Vcentre memory issue
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Vcentre memory issue
You do not have the required permissions to view the files attached to this post.
Re: Vcentre memory issue
It looks like there's a bug in the box23_check_vmware.pl script. Not knowing what is in that script, or where it came from, makes it hard to debug.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Re: Vcentre memory issue
Hello,
Thanks for the reply!!
We need a solution for this. Any ways to fix it?
Any idea when this bug will be fixed?
Thanks for the reply!!
We need a solution for this. Any ways to fix it?
Any idea when this bug will be fixed?
Re: Vcentre memory issue
We don't usually fix bugs in third-party scripts. That's up to the third party who wrote it.
I would contact the author of the box23_check_vmware.pl script to report the issue.
There's a bug in the box23_check_vmware.pl script that's causing the amount of free memory to be miscalculated. It's likely a logic error, since there's no way a server can have < 0 free memory. Make it subtract the "used" from the "total" instead of what it's doing; subtracting the "used" from the "effective."
You could open it up yourself in a text editor and fix the bug. This could be an opportunity to send them a PR on GitHub (if it even is on GitHub -- for all I know some employee at your company wrote this). Keep in mind that if it's GPL licensed, you're obligated under the terms of the license to publish the modified source if you change it.
I would contact the author of the box23_check_vmware.pl script to report the issue.
There's a bug in the box23_check_vmware.pl script that's causing the amount of free memory to be miscalculated. It's likely a logic error, since there's no way a server can have < 0 free memory. Make it subtract the "used" from the "total" instead of what it's doing; subtracting the "used" from the "effective."
You could open it up yourself in a text editor and fix the bug. This could be an opportunity to send them a PR on GitHub (if it even is on GitHub -- for all I know some employee at your company wrote this). Keep in mind that if it's GPL licensed, you're obligated under the terms of the license to publish the modified source if you change it.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.