-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
non-ASCII/Unicode character in service name is tripping up the api/services requests #1221
Comments
NCPA was built to support any UTF-8 characters (a superset of ASCII), so NCPA will likely break if non-UTF-8 characters are used for checks. That said, the |
I have a similar problem with a windows server running some stupid software with umlauts in its servicename. NCPA-Version 3.1.0 |
Out of curiosity, what output do you get for following in PowerShell for an affected system? $OutputEncoding = [System.Text.Encoding]::UTF8 |
I'm thinking this is likely a problem with 'psutil' module. The code path is straightfoward in NCPA with no UTF string translations occurring.
We essentially get a PSUTIL winservice class, and the error is getting the service status from that object without any variables being changed within NCPA, itself.
I checked history of psutil, and don't see any known issues on versions of psutil since 3.1.1 deployment of NCPA. |
|
Hi,
It seems that NCPA does not handle special characters properly in service names. I tried saving ncpa.cfg in different encodings (UTF-8 without BOM, ANSI), but the issue persists. Is there a way to ignore Windows services with accented characters in ncpa.cfg? Thanks! |
@albertbertus, We are aware of this issue and will try to fix it as soon as possible. Unfortunately, we have been given other priorities for the near-term and are unable to work on it at the moment. If you can convince the PSUtil team to fix this bug, we can update the version we are using to include the fix earlier. Otherwise it'll be a while before we can get a workaround merged in. |
Hi @ne-bbahn, |
@ne-bbahn, which version of psutils was used for the 3.1.1 build of NCPA? I assume 6.0.0, but can't validate. I opened psutil issue. I THINK I may have identified the issue and stated it there. |
Based on the files in lib/library.zip, the version included is 6.1.1. Since a version is not specified, the build just pulls in whatever the default version is. This may have been updated since the Nagios NCPA build artifacts were last created as using pip install --upgrade psutil is now giving me 7.0.0. |
NCPA 3.1.1 on Windows Server 2019
The text was updated successfully, but these errors were encountered: