Page 2 of 2
Re: Issues while running Powershell script in Nagios XI
Posted: Fri Jan 29, 2021 5:02 pm
by ssax
It's working properly on mine with that config file and the same setup.
Please double-check the version that is listed next to it in the control panel on this new server.
Additionally, is the nsclient++ service running as the local system account on there? (that's the default)
Is there a nsclient.ini on that system instead of an NSC.ini?
If you run it manually from the a powershell session on that system, does it work?
Re: Issues while running Powershell script in Nagios XI
Posted: Wed Feb 03, 2021 12:12 am
by RIDS_I2MP
Hello Team,
The NSC Client version is same as we have used earlier i.e 0.3.9 on the server where it is working fine.
Only on this server it is showing as no output available. the screenshot which I had attached earlier.
NSC Client++ service is running and also I have restarted it twice now.
PFA that there is only NSC.ini file present and if I run it manually on the powershell it runs successfully.
Re: Issues while running Powershell script in Nagios XI
Posted: Wed Feb 03, 2021 5:54 pm
by ssax
Please PM me a copy of your profile.zip file from Admin > System Profile by clicking the Download Profile button, I want to see how it's configured on the XI side.
It doesn't like it on yours for some reason:
Code: Select all
2021-01-29 11:07:18: error:modules\CheckExternalScripts\CheckExternalScripts.cpp:214: The command (cmd) returned an invalid return code: -1073741502
Please edit the NSC.ini and change these:
Code: Select all
[log]
;# LOG DEBUG
; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test)
;debug=1
;
;# LOG FILE
; The file to print log statements to
;file=nsclient.log
To these:
Code: Select all
[log]
;# LOG DEBUG
; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test)
debug=1
;
;# LOG FILE
; The file to print log statements to
file=nsclient.log
Then restart the nsclient++ service, run the check again, and send me the nsclient.log from the system after.
Once that's done, disable debug logging and restart the nsclient++ service so it doesn't fill up your drive.