Box293 MSW checks aborting
Posted: Sun Apr 19, 2020 1:57 pm
Nagios Core 4.3.4
Using Box293 MSW checks
I am repeating this error on a regular basis.
Host: TGCSESXI-16
Service: Host pNic Status vmnic3 - TGCSESXI-16
Status: UNKNOWN
Last check: 04-19-2020 14:50:02
Duration: 0d 0h 8m 30s
Attempt: 3/3
Status information: Total number of concurrent checks exceeds 15, aborting!
This also happens on many VMs at the same time and on other checks all pertaining to the MSW checks
Anyone have any ideas on what I can check or change here?
Thank you
Tom
Update I changed the check_interval 5 and retry_interval 3 to 180 360 1440 etc. not sure if this will help some checks do not need to be checked every 5 minutes
thoughts?
I found this in box293 manual
Arguments Config File Some arguments can be defined in a config file to make check commands simpler. The config file is checked when the plugin runs.
It is called .visdkrc and is located in the vi-admin home directory /home/vi-admin or ~ as it is also referenced. This file is a simple plain text file.
The current arguments that can be defined in the config file are:
• --concurrent_checks ◦ VI_CONCURRENT_CHECKS= • --server ◦ VI_SERVER= • --timeout ◦ VI_TIMEOUT=
Example: • VI_CONCURRENT_CHECKS=45 • VI_SERVER=vcenter.box293.local • VI_TIMEOUT=120
When the plugin executes, it will use the values of the arguments defined in the config file. HOWEVER if the argument is also supplied to the plugin (like --concurrent_checks 20), the argument will override the value in the config file.
The main reason for introducing the config file had to do with making Nagios command / service definition simpler. Lets say you had defined 20 different command definitions in Nagios for the box293_vmware_plugin. At some point, you may need to increase the --conncurrent_checks or --timeout value, which would involve updating 20 separate commands. By using the config file, you only need to update the config file once and all Nagios checks from this point forward will use the updated argument value. No need to update Nagios or restart
But I do not see the config file on my MSW server in the /home/vi-admin folder
not sure how to see a . file in Linux
Using Box293 MSW checks
I am repeating this error on a regular basis.
Host: TGCSESXI-16
Service: Host pNic Status vmnic3 - TGCSESXI-16
Status: UNKNOWN
Last check: 04-19-2020 14:50:02
Duration: 0d 0h 8m 30s
Attempt: 3/3
Status information: Total number of concurrent checks exceeds 15, aborting!
This also happens on many VMs at the same time and on other checks all pertaining to the MSW checks
Anyone have any ideas on what I can check or change here?
Thank you
Tom
Update I changed the check_interval 5 and retry_interval 3 to 180 360 1440 etc. not sure if this will help some checks do not need to be checked every 5 minutes
thoughts?
I found this in box293 manual
Arguments Config File Some arguments can be defined in a config file to make check commands simpler. The config file is checked when the plugin runs.
It is called .visdkrc and is located in the vi-admin home directory /home/vi-admin or ~ as it is also referenced. This file is a simple plain text file.
The current arguments that can be defined in the config file are:
• --concurrent_checks ◦ VI_CONCURRENT_CHECKS= • --server ◦ VI_SERVER= • --timeout ◦ VI_TIMEOUT=
Example: • VI_CONCURRENT_CHECKS=45 • VI_SERVER=vcenter.box293.local • VI_TIMEOUT=120
When the plugin executes, it will use the values of the arguments defined in the config file. HOWEVER if the argument is also supplied to the plugin (like --concurrent_checks 20), the argument will override the value in the config file.
The main reason for introducing the config file had to do with making Nagios command / service definition simpler. Lets say you had defined 20 different command definitions in Nagios for the box293_vmware_plugin. At some point, you may need to increase the --conncurrent_checks or --timeout value, which would involve updating 20 separate commands. By using the config file, you only need to update the config file once and all Nagios checks from this point forward will use the updated argument value. No need to update Nagios or restart
But I do not see the config file on my MSW server in the /home/vi-admin folder
not sure how to see a . file in Linux