Since i've upgraded all my windows servers with the latest version of centreon-nsclient 0.5.3 available, i got some issues with few probes and the one who make me struggle is a check_process on a specific software that was already added on the server.
For this software we have 2 servers and it's suppose to run on only one of our server, the server of production. The problem is that the command give us back the wrong value indeed our "basic command" should return "OK" on our server 1 if the "process.exe" run correctly and "critical" if the process is Stopped but the problem is that the prob keept sending us that this process is currently down but is in reality "UP" when we check his state on the server in the task manager.
To be honest i don't know where this problem come from, i did few test to be sure it comes from the nsclient++ and not from our server/software, like doing a backup of the nsclient version and yes we have no problem with any probes with the old version of nsclient 0.43
The check-process command is suppose to return the current state of the process
Hello Xepra
Could this be related to case-sensitivity in the process name? check_process is case-sensitive, and it should not be.
This issue is logged here: https://github.com/mickem/nscp/issues/587
Check_process problem
Hello Guys,
Since i've upgraded all my windows servers with the latest version of centreon-nsclient 0.5.3 available, i got some issues with few probes and the one who make me struggle is a check_process on a specific software that was already added on the server.
For this software we have 2 servers and it's suppose to run on only one of our server, the server of production. The problem is that the command give us back the wrong value indeed our "basic command" should return "OK" on our server 1 if the "process.exe" run correctly and "critical" if the process is Stopped but the problem is that the prob keept sending us that this process is currently down but is in reality "UP" when we check his state on the server in the task manager.
To be honest i don't know where this problem come from, i did few test to be sure it comes from the nsclient++ and not from our server/software, like doing a backup of the nsclient version and yes we have no problem with any probes with the old version of nsclient 0.43
The check-process command is suppose to return the current state of the process
Expected Behavior
Normally this should happen :
Actual Behavior
This happen instead.
Details
Additional Details
NSClient++ log:
Thanks by advance to anyone who can help me with this issue
Xepra.