Reopen:NS Client Error after upgrade

[sutenag]

Hi. I have to open a new topic for this problem.Problem is back again after the weekend

Output from putty Nagios server.
[root@searnanpmon01 libexec]# /usr/local/nagios/libexec/check_nrpe -u -H 10.208.85.30 -t 90 -c check_vix_pendingcards -a '0' '8'
The command (check_vix_pendingcards) returned an invalid return code: -1073741502

With no ARG, same error
[root@searnanpmon01 libexec]# /usr/local/nagios/libexec/check_nrpe -u -H 10.208.85.30 -t 90 -c check_vix_pendingcards
The command (check_vix_pendingcards) returned an invalid return code: -1073741502

Can run the check local on the windows server

C:\Program Files\NSClient++>c:\perl\bin\perl.exe c:\afc\scripts\nagios\check_vix_pendingproducts.pl
OK - No files older than one hour found

Seems that the connection from Nagios to the windows server with this checker is down, if you see in the log file there are no entries from 160311 09:xx to today

In what log file can i find more details info about check connection from nagios server to the windows server?

[hsmith]

For clarification, what did you upgrade - NSClient, or Nagios XI?

[sutenag]

we upgrade the nagios server from 2012R1.7 to 5.2.3, we had problems with some checkers like webinject that Sean help us in a remote session, he did also upgrade the nagios version in a remote session. We did upgrade the nsclient from 0.3 to 0.4 in the troubleshot process to solve this checker. Please read the closed/locked topic "NS Client Error after upgrade"

[tgriep]

Could you post your nsclient.ini file for your windows system so we can see how the command is defined?
Are you seeing any errors in the nsclient.log file on the windows system?

[sutenag]

But i have attache the nsclient.ini to this topic..?

Yesterday we change some value back to the old format like "allowed_hosts" and restart nsclient service, change it back to new format "allowed hosts" restart the nsclient service and then it starts to work. Also notice if we are logged in with mstc IP /admin (console) and restart the nsclient service it helps.

[tgriep]

Sorry, I missed the attached files.
Are you saying that it is working now?

FYI, when ever you change the nsclient.ini file, the the nsclient service will need to be restarted on the Windows system.
The ini file is loaded when the service is started.

[sutenag]

hi. Its ok think you have a lot of topic to look through and its easy to miss all the attached files.

But after we restart the nsclient servals times the checker comes online with OK status, and change the ini file to incorrect vaules and restart, change it back to new values and restart the it over again. Yes its working now and we have to see for how long.

[hsmith]

Let us know if the issues come back.