Yes, on our high-traffic production servers, NSClient routinely is slow to respond. But we're potentially talking several thousand checks that we've had this issue with.
I'll need to figure out a way to make this change in bulk.
Also, if we're holding the check (or socket) in memory longer, this will have a significant impact on nagios server memory usage, right?
Weird scheduling issues
Re: Weird scheduling issues
Andrew J. - Do you even grok?
Re: Weird scheduling issues
I just searched the event log. 482 Socket timeout messages in the past 24hours.
Andrew J. - Do you even grok?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Weird scheduling issues
You could just add it to the command definition in the CCM, depending on your setup it would likely only be a couple commands to add it to.