Nagios Support Forum

Nagios XI version: 5.7.5
NCPA agent Version: 2.3.0.el7.x86_64.rpm

Installed the latest (ncpa-2.3.0.el7.x86_64.rpm) Nagios Cross Platform Agent (NCPA) agent on a RHEL 7 server. Followed by then configuring it to work in passive mode. No issues with the install or configuration. Started seeing the expected "Error: Got host checkresult" messages for the agent on the Nagios server in it's log file.

I can then see it in the nagios web UI as an unconfigured object. If I go through the wizard to configure it to be monitored, after the last step, it claims that an error occurred while attempting to apply your configuration to the monitoring engine. There does not appear to be anything useful in the downloaded configuration .gz file for the failed configuration. There are no special characters in the hostname -- which I found noted as another users issue to failing verification.

Running the following only generates warning about missing contacts.
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

The new host is not visible from any of the dashboards or views. It is however visible in Core Config Manager (CCM).

The following was the config used for the agent
#/usr/local/ncpa/etc/ncpa.cfg.d/initial.cfg
[passive checks]
%HOSTNAME%|__HOST__ = system/agent_version
%HOSTNAME%|CPU Usage = cpu/percent --warning 60 --critical 80 --aggregate avg
%HOSTNAME%|Memory Usage = memory/virtual --warning 80 --critical 90 --units Gi

Any help or advice would be appreciated. Thank you in advance,
Eric

Hi,

The new host is not visible from any of the dashboards or views. It is however visible in Core Config Manager (CCM).

It sounds like the new host is in the configuration database but there's an error with the object(s), so when you Apply Configuration it's reverting to the last known configuration and that's why it's not showing up in the dashboards.

Let's run the following tail command, then navigate to the CCM and then try to Apply Configuration and post the full output of the log to the thread. We should be to review the error message and correct the settings.
Thanks,
Benjamin