Total number of concurrent checks exceeds 15, aborting!

[WillemDH]

FYI Troy Lea the creator of the plugin is probably the best person to give you the most correct answer. It's hard to give you an exact answer as it depends of a lot of factors.

For comparison, I have 2 VMA's, one per datacenter, each with 6 CPU's. We have 36 ESX servers on 2 datacenters, 6 clusters, 40 datastores. Our 2 VMA's CPU load is very high. As you can imagine there are too many factors to be able to just say you need this or that. I would say you need at least one more VMA, possibly even two more. You also need to calculate some space for extra load in case of problems, as load tends to get higher caused by shorter retry intervals etc.

I would increase the default concurrent checks to 35 for 6 CPU's in box293_check_vmware.pl

Code: Select all

        concurrent_checks => {
                type => '=i',
                help => 'Maximum amount of concurrent checks that can run at any one time. Default is 15. This option helps prevent the vMA appliance from being overloaded.',
                required => 0,
                default => 35,
                }, # End 'concurrent_checks' => {

Good luck and let us know how it goes.

[Box293]

@WillemDH is spot on. Basically it comes down to how much resources your vMA has to handle the amount of checks you want to run. More vMA's might be a good option in your circumstances.

FYI in the next update to the plugin I'll be adding support for a settings file so things like concurrent_checks can be defined in the config file ... you won't need to define it multiple command or service definitions. Probably will be released within a month.

[bsivavani]

We have increased concurrent_checks to 50, now flood stopped.

Please be open this thread for couple of days.

[bsivavani]

Also please let us know cpu, disk and memory on your vMA.
And how many esxi servers, data store and storage adapter monitoring in one vMA and its performance.

[tmcdonald]

That sort of thing is getting into consulting and is not covered by our support. If @WillemDH is willing to discuss this sort of thing with you, I would request that it be done via email or PM.

[bsivavani]

I am trying to send via PM, but the message routing to outbox. Please confirm if you receive the message.

[hsmith]

If you're having issues sending a message on the forums, please post a screenshot so we know if there is a potential issue.

[bsivavani]

Able to send PM now.

[tmcdonald]

Please note that @WillemDH is not a Nagios employee, and is not under obligation to reply or provide support. Whether or not he does is entirely up to him - please respect his decision either way.

As this has gone beyond the realm of support and into consulting, I would like to close this thread now. If you are interested in consulting, you can email [email protected] to begin the discussion.

[bsivavani]

Thanks for all support. Please close this thread.