NCPA 2.2.2 403 forbidden

[snapon_admin]

Trying to figure out a cause for this issue. We were running NCPA 2.2.0 on one of our Solaris 11 servers and the checks were working fine. There is an issue with Solaris service checks where the service output is truncated after a pipe, and according to the NCPA changelog it looks like this issue may have been corrected in version 2.2.2. We decided to update our agent to 2.2.2 and now all of our checks are getting the following error:

UNKNOWN: An error occured connecting to API. (HTTP error: '403 FORBIDDEN')

XI version 5.7.3
NCPA.py version 1.2.3
NCPA Solaris 11 agent version 2.2.2

[snapon_admin]

We got it to work by removing the allowed hosts list, but we'd obviously prefer to be able to use this list to lock access down to the IP of our XI server. Is there anything we can do to correct this?

[snapon_admin]

We're also noticing that the service output is still truncated after the pipe, which was our original reason for updating to 2.2.2 in the first place. Any idea when a fix for that might be available?

[ssax]

Before you removed the allowed hosts list, what did the ncpa_listener.log show on the remote systems when they were failing?

I don't see anything in the changelog for 2.2.2 that would indicate anything to do with a pipe was fixed:

https://github.com/NagiosEnterprises/nc ... HANGES.rst

Do you have the bug report number, forum post, or ticket that the bug report/feature request came from?

[snapon_admin]

Saw this under 2.2.1's changelog and thought it might be the issue we were having, guess it was something different.

Fixed issue with Solaris 11.4 services output parsing

I'm not sure a feature request or bug report was filed, but the issue was discussed on a ticket I had opened, ticket number 782030.

[lmiltchev]

According to our developers, the issue should be fixed in NCPA 2.3.0. See the changelog here:

https://github.com/NagiosEnterprises/nc ... HANGES.rst

[snapon_admin]

Any idea on a time frame for release of that version?

[lmiltchev]

I asked our developers - they don't have an ETA, but said that the release should be sometime soon. I would expect it to be released in a month or so, but again - nothing is set in stone.