I’m currently working on Windows Server 2016 with NSClient++ (x64) 0.5.0062
I have written a powershell script to send notifications to Nagios using this line of code
Set-Alias nscp "C:\Program Files\NSClient++\nscp.exe" -Scope Global
nscp client --module NSCAClient address=172.22.50.9:5667 encryption=XOR command="MDI_zip_d" result=$status message="$global:statusInformation"
I have set the nsclient.ini on the section [/settings/NSCA/client] a new hostname, you see… My current hostname on the server is all capitalized like this, MDIARCH03, the server on Nagios is configured in lowercase letter… Before this version of Nagios, I used to tell through the above command the server name through the line sender-host=mdiarch03 and that would work just fine. But ever since we upgraded to this new version the passive check won’t work.
This is what I get from the event log
[09-03-2018 17:26:12] Error: External command failed -> PROCESS_SERVICE_CHECK_RESULT;MDIARCH03;MDI_zip_d;2;teste do nagios [09-03-2018 17:26:11] Warning: Passive check result was received for service ‘MDI_zip_d’ on host ‘MDIARCH03’, but the host could not be found!
sender-host=ARG - Nagios
Re: sender-host=ARG - Nagios
Hello CokraMehinka,
It seems that you may be encountering a case-sensitivity issue here. Have you tried matching the capitalization in the argument?
Also note that it is suggested to switch from NSClient++ to the officially supported NCPA (Nagios Cross-Platform Agent) which is maintained by Nagios.
It seems that you may be encountering a case-sensitivity issue here. Have you tried matching the capitalization in the argument?
Also note that it is suggested to switch from NSClient++ to the officially supported NCPA (Nagios Cross-Platform Agent) which is maintained by Nagios.
April: Actively advancing awesome answers with ardent alliteration, aptly addressing all ambiguities. Amplify your acumen and avail our amicable assistance. Eagerly awaiting your astute assessments of our advice.