We are using NSClient++ in two different ways :
- First one is the normal way, as a Nagios Client. NSClientpp is called by Nagios for performing several checks. Results of these checks are reported into Nagios web GUI.
- Second is as a remote execution backdoor, allowing us to perform remote batch execution on windows host, from a scheduler installed on linux host. The scheduler is installed on same server than Nagios server, then it could use check_nrpe command to launch batch on remote host as external scripts.
Our problem is, when a batch to execute (second usage described above) takes some times, other checks performed in the same time by Nagios server (first usage described above) are not possible. It seems that, during the execution of a "check" (in fact, one of our external script), NSClientpp is unable to handle any other requests.
This is a big problem, because some of remote batches we have to execute may takes hours to complete, we then reveive alerts for nagios checks (because NSClientpp is not available). Our understanding of this situation is that NSClientpp is not multithread/multiprocess, and does not fork when receiving a request, making the parent process available to handle other request (like any daemon server should do).
Please be notice that our problem has nothing to deal with "timeout" settings, which are properly adjusted to our need, on both configuration sides (nagios sserver and nsclientpp ini file).
Question are :
- Can anyone confirm that NSClientpp behaviour is not allowing such concurent call ?
- Does anyone can suggest a solution ?
We have read that using NSClientpp should be deprecated, and NC_net is supposed to be better. Beside of that we haven't found so much documentation about feature of that client, and we are not able to find out if this client will handle concurent calls properly. Since we have "some" windows servers monitored by Nagios, we don't want to deploy NC_net and replace NSClientpp before being sure of the reliability of it... So if anyone have info regarding this, he/she would be welcome
Thanks in advance for any of your updates !