ncpa error messages and bugs 1.0/1.1
Posted: Thu Dec 05, 2013 1:37 pm
I'm using Nagios XI 2012R2.5 on a Centos VM provided by Nagios and have created a NRDS config which passively runs a command on the client server. When running NCPA 1.0 and starting the passive listener process, I get the following error.
This is my ncpa.cfg.
I update the agent to version 1.1 (i386), configured the ncpa agent. I noticed that the ncpa.cfg originally had CONFIG_NAME and CONFIG_VERSION in upper case, but these returned to lower case after I used the URL to configure the client. I still get the error below
and the api doesn't show up in the HUD for the client https://kchenowe-ubuntu.dhcp.mycompany.com:5693/ when clicking on the Api link in the NCPA interface, I get the following URL and error
https://kchenowe-ubuntu.dhcp.mycompany. ... ot%20exist.
Here is the new ncpa.cfg
Throughout this exercise, the NRDS configuration is updated (via nrds_updater -h <host>) and those files are unchanged.
Is there a bug in the 1.0 version of the NCPA client regarding the CONFIG_* variables?
Is there a bug in the 1.1 version of the NCPA linux client (running ubuntu 13.10)? (Why would the client config change the case on the CONFIG_* variable keys?
I have the 1.0 client from a previous download, but didn't see it on the internet. Where are both (and future) versions of the NCPA client available on the web?
Should I use NCPA version 1.0 or 1.1?
We are in the process of purchasing Nagios XI. Thank you in advance for your help.
Code: Select all
2013-12-05 09:46:17,543 27250 INFO started
2013-12-05 09:46:17,545 27250 INFO Hostname is being assigned as the domain name of this computer.
2013-12-05 09:46:17,546 27250 INFO HOSTNAME was not explicitly declared. Using kchenowe-ubuntu
2013-12-05 09:46:17,546 27250 INFO Hostname is being assigned as the domain name of this computer.
2013-12-05 09:46:17,546 27250 INFO HOSTNAME was not explicitly declared. Using kchenowe-ubuntu
2013-12-05 09:46:17,547 27250 INFO Hostname is being assigned as the domain name of this computer.
2013-12-05 09:46:17,547 27250 INFO HOSTNAME was not explicitly declared. Using kchenowe-ubuntu
2013-12-05 09:46:17,548 27250 ERROR No option 'CONFIG_NAME' in section: 'nrds'
Traceback (most recent call last):
File "ncpa_posix_passive.py", line 41, in run_all_handlers
File "/usr/local/ncpa/passive/nrds.py", line 21, in run
if self.config_update_is_required():
File "/usr/local/ncpa/passive/nrds.py", line 91, in config_update_is_required
'configname': self.config.get('nrds', 'CONFIG_NAME'),
File "/usr/lib/python2.6/ConfigParser.py", line 541, in get
NoOptionError: No option 'CONFIG_NAME' in section: 'nrds'
Code: Select all
[passive]
uid = nagios
handlers = nrds
loglevel = info
gid = nagcmd
sleep = 300
logfile = var/ncpa_passive.log
pidfile = var/ncpa_passive.pid
[api]
community_string = mytoken
[plugin directives]
.sh = /bin/sh $plugin_name $plugin_args
.pl = perl $plugin_name $plugin_args
plugin_path = plugins/
.ps1 = powershell -ExecutionPolicy Unrestricted $plugin_name $plugin_args
.vbs = cscript $plugin_name $plugin_args //NoLogo
[listener]
uid = nagios
certificate = adhoc
loglevel = info
ip = 0.0.0.0
gid = nagcmd
logfile = var/ncpa_listener.log
port = 5693
pidfile = var/ncpa_listener.pid
[nrds]
config_version = None
config_name = sample_config
update_plugins = on
config_os = None
update_config = on
token = mytoken
url = https://172.28.154.55/nrdp
[nrdp]
token = mytoken
hostname = kchenowe-ubuntu.dhcp.mycompany.com
parent = https://172.28.154.55/nrdp
[passive checks]
%hostname%|swap usage = /memory/swap/percent --warning 40 --critical 80
%hostname%|cpu usage = /cpu/percent --warning 20 --critical 30
%hostname%|memory usage = /memory/virtual/percent --warning 60 --critical 80I update the agent to version 1.1 (i386), configured the ncpa agent. I noticed that the ncpa.cfg originally had CONFIG_NAME and CONFIG_VERSION in upper case, but these returned to lower case after I used the URL to configure the client. I still get the error below
Code: Select all
2013-12-05 11:38:47,889 32257 INFO HOSTNAME was not explicitly declared. Using kchenowe-ubuntu
2013-12-05 11:38:47,890 32257 ERROR No option 'CONFIG_NAME' in section: 'nrds'
Traceback (most recent call last):
File "ncpa_posix_passive.py", line 41, in run_all_handlers
File "/usr/local/ncpa/passive/nrds.py", line 21, in run
if self.config_update_is_required():
File "/usr/local/ncpa/passive/nrds.py", line 91, in config_update_is_required
'configname': self.config.get('nrds', 'CONFIG_NAME'),
File "/usr/lib/python2.6/ConfigParser.py", line 541, in get
NoOptionError: No option 'CONFIG_NAME' in section: 'nrds'https://kchenowe-ubuntu.dhcp.mycompany. ... ot%20exist.
Code: Select all
Web page content
{
"error": "Referencing node that does not exist."
}Code: Select all
[passive]
uid = nagios
handlers = nrds
loglevel = info
gid = nagcmd
sleep = 300
logfile = var/ncpa_passive.log
pidfile = var/ncpa_passive.pid
[api]
community_string = mytoken
[plugin directives]
.sh = /bin/sh $plugin_name $plugin_args
plugin_path = plugins/
.ps1 = powershell -ExecutionPolicy Unrestricted $plugin_name $plugin_args
pl = perl $plugin_name $plugin_args
.vbs = cscript $plugin_name $plugin_args //NoLogo
[listener]
uid = root
certificate = adhoc
loglevel = info
ip = 0.0.0.0
gid = root
logfile = var/ncpa_listener.log
port = 5693
pidfile = var/ncpa_listener.pid
[nrds]
config_version = None
config_name = sample_config
update_plugins = on
config_os = None
update_config = on
token = mytoken
url = https://172.28.154.55/nrdp/
[nrdp]
token = mytoken
hostname = kchenowe-ubuntu.dhcp.mycompany.com
parent = https://172.28.154.55/nrdp/
[passive checks]
%hostname%|swap usage = /memory/swap/percent --warning 40 --critical 80
%hostname%|cpu usage = /cpu/percent --warning 20 --critical 30
%hostname%|memory usage = /memory/virtual/percent --warning 60 --critical 80Throughout this exercise, the NRDS configuration is updated (via nrds_updater -h <host>) and those files are unchanged.
Is there a bug in the 1.0 version of the NCPA client regarding the CONFIG_* variables?
Is there a bug in the 1.1 version of the NCPA linux client (running ubuntu 13.10)? (Why would the client config change the case on the CONFIG_* variable keys?
I have the 1.0 client from a previous download, but didn't see it on the internet. Where are both (and future) versions of the NCPA client available on the web?
Should I use NCPA version 1.0 or 1.1?
We are in the process of purchasing Nagios XI. Thank you in advance for your help.