PowerShell NRPE – How to Display Accentuated Characters in Check_NRPE Result

nagiosnrpensclient++powershell

I have a custom Powershell script called by Nagios using "check_nrpe". Currently all check results output messages with special characters like 'è', 'é' or 'à' are not displayed properly when the check result is shown on Nagios.

How to allow those to be displayed properly?

Check command

$USER1$/check_nrpe  -H server.tld -c check_foo -a 7 7 7

Script call on nsclient.ini

[/settings/external scripts/scripts]
check_foo = cmd /c echo X:\scripts_\check-foo.ps1 -arg1 "$ARG1$" -arg2 "$ARG2$" -arg3 "$ARG3$"; exit($lastexitcode) | powershell.exe -command -

Expected result

CRITICAL - Vérification échouée

Actual result

# UTF-8 BOM (GUI)
CRITICAL - Vrification choue

# UTF-8 BOM (CLI)
CRITICAL - V,rification ,choue,

# UTF-8 (GUI)
CRITICAL - VǸrification ǸchoueǸ

Currently my Powershell script is remotely called with "check_nrpe" from the Linux CentOS 7 monitoring machine and NSClient++ on the target server (Windows 2016 Server). The script itelf is encoded as "UTF-8 BOM".

Best Answer

disable your nsclient.ini encoding utf8

[/settings/NRPE/server]
;encoding = utf8

in your script use

[Console]::OutputEncoding = [System.Text.Encoding]::UTF8

output your result with : (instead of write-output or write-host)

[Console]::WriteLine("ééé")

works for me pick up from here

Related Solutions

PowerShell – How to Check if Running with Administrator Privileges

$currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
$currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)

(from Command line safety tricks)

Powershell – Passing arguments to a Powershell Script using Nagios NRPE

Arguments can be allowed on multiple levels (depending on how you want to slice your "security"). In essence this means you can allow arguments at the NRPE level as well as the external scripts level (and in your case you probably want them in both places)

You can find some background details here: http://docs.nsclient.org/howto/external_scripts.html#arguments

But disregarding the theory to answer your question you need to enable allow arguments in TWO places (see the following):

[/settings/NRPE/server]
allow arguments=true

[/settings/external scripts]
allow arguments=true

[/settings/external scripts/scripts]
foo=scripts\\foo.bat "argument 1" "argument 2"

The one your missing is the latter one:

[/settings/external scripts]
allow arguments=true

So adding that would resolve your issue.

Edit: Add information about the second issue.

The secondary problem with the power shell launch (see comment to this post) was related to powershell oddness which requires a rather intricate command line syntax:

[/settings/external scripts/scripts]
test = cmd /c echo scripts\test.ps1 "$ARG1$"; exit($lastexitcode) | powershell.exe -command -

The problem was the missing - at the end of the command (correct command above).

Related Topic