Xml and rrd files are not created automatically

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

I am trying to enable graph for particular service, when click on graph button of any particular service while getting below error.

XML file "/var/lib/pnp4nagios/perfdata/example.com/ZOMBIE-PROCESSES.xml" not found. Read FAQ online

Also Xml and rrd files are not created automatically. Please suggest me on the same.

Thanks,
Imran Khan.
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Xml and rrd files are not created automatically

Post by sreinhardt »

Could you post a sample of the output from this command when run via the command line? Also do you have performance data processing enabled for these services?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Re: Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

I am facing this issue with all the services. How to check performance data processing is enabled or not for these services?

NRPE configuration file:-
command[check_zombie_procs]=/usr/lib64/nagios/plugins/check_procs -w 5 -c 10 -s Z

Service file:-
define service{
use generic-service ; Name of service template to use
host_name example.com
service_description ZOMBIE-PROCESSES
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 5
retry_check_interval 2
contact_groups abcgrp
notification_interval 200
notification_period 24x7
notification_options w,u,c,r
check_command check_nrpe!check_zombie_procs
}

Ran the below command on all Linux machine.
/usr/lib64/nagios/plugins/check_procs -w 5 -c 10 -s Z
PROCS OK: 0 processes with STATE = Z

Command:-
define command{
command_name check_local_procs
command_line $USER1$/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
}

Thanks,
Imran Khan.
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Re: Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

Any help?

Thanks,
Imran Khan.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Xml and rrd files are not created automatically

Post by slansing »

It doesn't look like that check is returning performance data, you can check by going to a service that is using the plugin at Home > Services "Click on a service" and look for the section in the details table that shows "Performance Data:" Is there any listed there?
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Re: Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

Thanks for the reply.

Performance Data is showing empty in some services of all the servers. Please let me know how to enable this option for all the services to fix the mentioned error.

Thanks,
Imran Khan.
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: Xml and rrd files are not created automatically

Post by abrist »

Can you give us an example of the type of checks without performance data (some checks do not return perfdata)?
Lets get a tail of the perfdata logs:

Code: Select all

tail -25 /usr/local/nagios/var/perfdata.log
tail -25 /usr/local/nagios/var/npcd.log
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Re: Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

I have ran the below command on nagios system to verify pnp4nagios but getting error. This is not new setup.

# perl verify_pnp_config --mode bulk --config=/etc/nagios/nagios.cfg --pnpcfg=/etc/pnp4nagios
[INFO] ========== Starting Environment Checks ============
[INFO] My version is: verify_pnp_config-0.6.21-R.40
[INFO] Start Options: verify_pnp_config --mode bulk --config=/etc/nagios/nagios.cfg --pnpcfg=/etc/pnp4nagios
[INFO] Reading /etc/nagios/nagios.cfg
[OK ] Running product is 'nagios'
[OK ] object_cache_file is defined
[OK ] object_cache_file=/var/nagios/objects.cache
[INFO] Reading /var/nagios/objects.cache
[OK ] resource_file is defined
[OK ] resource_file=/etc/nagios/resource.cfg
[INFO] Reading /etc/nagios/resource.cfg
[INFO] Reading /etc/pnp4nagios/process_perfdata.cfg
[INFO] Reading /etc/pnp4nagios/pnp4nagios_release
[OK ] Found PNP4Nagios version "0.6.11"
[OK ] Effective User is 'nagios'
[OK ] User nagios exists with ID '101'
[OK ] Effective group is 'nagios'
[OK ] Group nagios exists with ID '103'
[INFO] ========== Checking Bulk Mode Config ============
[OK ] process_performance_data is 1 compared with '/1/'
[OK ] service_perfdata_file is defined
[OK ] service_perfdata_file=/var/log/pnp4nagios/service-perfdata
[OK ] service_perfdata_file_template is defined
[OK ] service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$
[OK ] PERFDATA template looks good
[OK ] service_perfdata_file_mode is defined
[OK ] service_perfdata_file_mode=a
[OK ] service_perfdata_file_processing_interval is defined
[OK ] service_perfdata_file_processing_interval=15
[OK ] service_perfdata_file_processing_command is defined
[OK ] service_perfdata_file_processing_command=process-service-perfdata-file
[OK ] host_perfdata_file is defined
[OK ] host_perfdata_file=/var/log/pnp4nagios/host-perfdata
[OK ] host_perfdata_file_template is defined
[OK ] host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$
[OK ] PERFDATA template looks good
[OK ] host_perfdata_file_mode is defined
[OK ] host_perfdata_file_mode=a
[OK ] host_perfdata_file_processing_interval is defined
[OK ] host_perfdata_file_processing_interval=15
[OK ] host_perfdata_file_processing_command is defined
[OK ] host_perfdata_file_processing_command=process-host-perfdata-file
[CRIT] service_perfdata_command is defined (service_perfdata_command=process-service-perfdata)
[CRIT] service_perfdata_command is not allowed in mode 'bulk'
[CRIT] host_perfdata_command is defined (host_perfdata_command=process-host-perfdata)
[CRIT] host_perfdata_command is not allowed in mode 'bulk'
[HINT] Config options are not allowed in bulk mode (2)

Thanks,
Imran Khan
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: Xml and rrd files are not created automatically

Post by abrist »

Are you using the vanilla bulk mode, or bulk mode with npcd?
What is the output of:

Code: Select all

grep "service_perfdata\|host_perfdata" /usr/local/nagios/etc/nagios.cfg
grep "service_perfdata\|host_perfdata" /usr/local/nagios/etc/commands.cfg
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
imran_khan
Posts: 196
Joined: Mon May 27, 2013 3:16 pm

Re: Xml and rrd files are not created automatically

Post by imran_khan »

Hello,

I am not sure, it is vanilla bulk mode, or bulk mode with npcd?

[root@localhost nagios]# cat nagios.cfg | grep "service_perfdata\|host_perfdata"
# host_perfdata_command (defined below) and service performance
# data will be processed using the service_perfdata_command (also
host_perfdata_command=process-host-perfdata
service_perfdata_command=process-service-perfdata
#host_perfdata_file=/tmp/host-perfdata
#service_perfdata_file=/tmp/service-perfdata
#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
#host_perfdata_file_mode=a
#service_perfdata_file_mode=a
#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0
#host_perfdata_file_processing_command=process-host-perfdata-file
#service_perfdata_file_processing_command=process-service-perfdata-file
#service_perfdata_file=/var/spool/nagios/service-perfdata
#service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$
#service_perfdata_file_mode=a
#service_perfdata_file_processing_interval=15
#service_perfdata_file_processing_command=process-service-perfdata-file
#host_perfdata_file=/var/spool/nagios/host-perfdata
#host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$
#host_perfdata_file_mode=a
#host_perfdata_file_processing_interval=15
#host_perfdata_file_processing_command=process-host-perfdata-file
service_perfdata_file=/var/log/pnp4nagios/service-perfdata
service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$
service_perfdata_file_mode=a
service_perfdata_file_processing_interval=15
service_perfdata_file_processing_command=process-service-perfdata-file
host_perfdata_file=/var/log/pnp4nagios/host-perfdata
host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$
host_perfdata_file_mode=a
host_perfdata_file_processing_interval=15
host_perfdata_file_processing_command=process-host-perfdata-file

[root@localhost Defination]# cat commands.cfg | grep "service_perfdata\|host_perfdata"
# host_perfdata_file and service_perfdata_file options in the main config file.
Locked