Re: Performance issue
Posted: Tue Oct 24, 2017 6:17 am
Given information from https://assets.nagios.com/downloads/nag ... ptions.pdf
There are lots of errors lines
From the numbering of the existing files in /var/nagiosramdisk/spool/perfdata/, their timestamps and the npcd errors, it's like some other process already managed the perfdata.
Regarding the 'Max load reached', should I really change the default value in configuration file ?
I do not undestrand this detected load as this server seems to run with a CPU average < 50% (8 CPUs).
I also have thoses messages in perfdata.log
Should I change those values as explained in this old thread?
May it have an impact on performance ?
Code: Select all
[10-24-2017 11:56:12] NPCD: ERROR: Executed command exits with return code '7'
[10-24-2017 11:56:12] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /var/nagiosramdisk/spool/perfdata//1508838959.perfdata.service'
[10-24-2017 11:57:24] NPCD: WARN: MAX load reached: load 10.640000/10.000000 at i=0
[10-24-2017 11:57:39] NPCD: WARN: MAX load reached: load 10.260000/10.000000 at i=1
[10-24-2017 12:00:11] NPCD: ERROR: Executed command exits with return code '7'
[10-24-2017 12:00:11] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /var/nagiosramdisk/spool/perfdata//1508839199.perfdata.service'
[10-24-2017 12:00:31] NPCD: ERROR: Executed command exits with return code '7'
[10-24-2017 12:00:31] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /var/nagiosramdisk/spool/perfdata//1508839215.perfdata.service'
From the numbering of the existing files in /var/nagiosramdisk/spool/perfdata/, their timestamps and the npcd errors, it's like some other process already managed the perfdata.
Regarding the 'Max load reached', should I really change the default value in configuration file ?
I do not undestrand this detected load as this server seems to run with a CPU average < 50% (8 CPUs).
I also have thoses messages in perfdata.log
Code: Select all
2017-10-24 12:09:18 [14134] [0] *** TIMEOUT: Timeout after 5 secs. ***
2017-10-24 12:09:18 [14134] [0] *** TIMEOUT: Deleting current file to avoid NPCD loops
2017-10-24 12:09:18 [14134] [0] *** TIMEOUT: Please check your npcd.cfg
2017-10-24 12:09:18 [14134] [0] *** TIMEOUT: /var/nagiosramdisk/spool/perfdata//1508839749.perfdata.service-PID-14134 deleted
2017-10-24 12:09:18 [14134] [0] *** Timeout while processing Host: "<hostname>" Service: "System_-_Network_bandwidth"
2017-10-24 12:09:18 [14134] [0] *** process_perfdata.pl terminated on signal ALRM
Code: Select all
# grep -i time /usr/local/nagios/etc/pnp/process_perfdata.cfg
TIMEOUT = 5
[root@hq-nagios-xi01 var]# grep -ri time /usr/local/nagios/etc/pnp/npcd.cfg
# sleep_time - how many seconds should npcd wait between dirscans
# sleep_time = 15 (default)
sleep_time = 15
May it have an impact on performance ?