NCPA Web GUI - Live Data/Top Processes

[onegative]

G 'Day Nagios XI Support,

So I have encountered an issue which has completely befuddled me. What could cause such behavior is surely a mystery.

I would appreciate someone from support duplicating this scenario as to confirm/reject my testing.

At first I though it might be a system (serverA) specific but after replicating the conditions on serverB it happens exactly the same.

Scenario Description:
NCPA version 2.0.5
InstallDir E:\DCOM\Nagios\NCPA
Install Type (Windows Interactive and Silent)
Configurations Common to both serverA & serverB Attached
Debug Logs to both serverA & serverB Attached

Once the ncpa listener and passive services are up and operational perform the following steps.

Open a Desktop browser (Firefox 56.0) and connect to the remote ncpa listener
Login and then select Live Data -> Top Processes (Works!)
Then open a local Browser (Firefox 56.0) on the remote host where the ncpa listener exists
Login and then select Live Data -> Top Processes (Will not function locally)
Simultaneously the Desktop Browser also stops functioning and if you attempt to select Live Data -> Top Processes again you get no result data.

Parsing the ncpa_listener.log with debug activated you find the following errors.
This is very similar to the Bug Report # 114 on GitHub for NCPA.

Code: Select all

2017-10-05 09:54:39,858:ERROR:app:Exception on /ws/top [GET]
Traceback (most recent call last):
  File "C:\Python27\lib\site-packages\flask\app.py", line 1817, in wsgi_app
  File "C:\Python27\lib\site-packages\flask\app.py", line 1477, in full_dispatch_request
  File "C:\Python27\lib\site-packages\flask\app.py", line 1381, in handle_user_exception
  File "C:\Python27\lib\site-packages\flask\app.py", line 1475, in full_dispatch_request
  File "C:\Python27\lib\site-packages\flask\app.py", line 1461, in dispatch_request
  File "C:\ncpa\agent\listener\server.py", line 154, in token_auth_decoration
  File "C:\ncpa\agent\listener\server.py", line 667, in top_websocket
  File "C:\Python27\lib\json\__init__.py", line 244, in dumps
  File "C:\Python27\lib\json\encoder.py", line 207, in encode
  File "C:\Python27\lib\json\encoder.py", line 270, in iterencode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa0 in position 983: invalid start byte

If I log off the local session on the remote host, the problem persists. But once I close the browser on the remote host and refresh the Desktop Browser the Live Data Top Processes return data resumes.

Testing other browsers like IE 11.0 also experiences issues like not being about to display the API json data.

I truly believe some real QA testing is warranted against the NCPA listener if the product is being seriously considered as an agent solution for Nagios XI moving forward. I really like the NCPA agent but must be careful not to demo the issues when trying to sell the product across organizational teams.

Anyway find attached the logs and base common cfg files being utilized.

Would appreciate some feedback from the Support Staff if they are able to replicate the test.

And as always I appreciate all your hard work and dedication,
Danny

[kyang]

What language is your NCPA server set to?
I see there's a UTF8 encoding issue. Possibly the characters that are being outputted for python are an issue.

We've tested this, and it works just fine.

Let us know!

[onegative]

The servers are all set to "English (United States) - US"

Did you actually look at the debug log? This doesn't appear to be a language issue.

Danny

[jomann]

There seems to be two separate issues here.

1. Firefox, having two of them connected to NCPA causes them both to not work, and gives an error. I am not sure why but it is likely due to how the requests are being formatted and sent. I will look into that. Issue created here.

2. IE in the API, this is a problem with IE's javascript not allowing for default values in functions. I will also update this for the next version. Issue created here.

Both of these are added as issues on GitHub.

I test NCPA with Chrome pretty thoroughly and during the testing of the above I did not see any issues with the Top Processes tab in Chrome. You may want to use that for the time being if possible.

[onegative]

Jake,

Thank you very much for following up on this...I was pretty confident my testing was showing a true issue.

Request complete.

Warm regards,
Danny

[jomann]

Thanks for giving us the details.

I'll close this then. If you want to track these issues you can do so on Github.