NSClient++ Help (#1) - Missing passive checks (#553) - Message List
I've got an interesting one for ya...
I have about 20 win2k3 boxes and they are pretty much all having the same issue.
Each one has the main NSC.ini and 2 additional ini file. The first one (A) has 7 passive checks. The second (B) has 10 passive checks. Here is the issue.
A1...A7 work ok B1...B5 work B6...B10 fail.
Comment out B5...nothing
Comment out B6...nothing
(back to normal)
Remove B5...(B6-8 still gone) Then I start seeing results from B9!
The logs always show that each test still in the config work. The sniffer traces indicate that what I am seeing in Nagios is it...nothing is being lost on the nagios side.
It is like it is hitting a limit or something. But these same profiles work on other server types. Any ideas?
I am hitting the same limit. I can configure 12 passive service checks on any given server and then the rest stop reporting the results, just like tavor999's do. As a workaround, I started monitoring clusters of services in a single command (i.e. all Exchange services). This allows me to monitor more services. But, my goal would be to monitor each Windows Service individually and generate individual alerts if they go down. Is there any way to work around this 512 byte limit? Would it be possible to run two instances of NSClient++ on a server, each on a different port?
Thanks very much for your help.DigHeal10/30/10 22:19:40 (3 years ago)
I would guess it is the 512 byte payload length which is maximum for NSCA
Michael Medinmickem04/14/10 07:00:46 (3 years ago)