NPCD[75327]: ERROR: Executed command exits with return code '7'

Dear all,
I have a very troubling question. All of my monitored servers alert at 6 am every day.I checked the icinga2 server log:

Dec 19 06:10:31 vgchuvicgamasp01 sssd: Killing service [ssh], not responding to pings!
Dec 19 06:10:43 vgchuvicgamasp01 sssd: Killing service [nss], not responding to pings!
Dec 19 06:11:31 vgchuvicgamasp01 NPCD[75327]: ERROR: Executed command exits with return code ‘7’
Dec 19 06:11:31 vgchuvicgamasp01 NPCD[75327]: ERROR: Command line was ‘/usr/lib/pnp4nagios/libexec/process_perfdata.pl -n --bulk /var/spool/icinga2/perfdata/service-perfdata.1576706991’
Dec 19 06:11:31 vgchuvicgamasp01 sssd: [ssh][89174] is not responding to SIGTERM. Sending SIGKILL.
Dec 19 06:11:33 vgchuvicgamasp01 NPCD[75327]: ERROR: Executed command exits with return code ‘7’
Dec 19 06:11:33 vgchuvicgamasp01 NPCD[75327]: ERROR: Command line was ‘/usr/lib/pnp4nagios/libexec/process_perfdata.pl -n --bulk /var/spool/icinga2/perfdata/host-perfdata.1576706991’
Dec 19 06:11:43 vgchuvicgamasp01 sssd: [nss][103661] is not responding to SIGTERM. Sending SIGKILL.
Dec 19 06:11:47 vgchuvicgamasp01 check_radius: rc_get_seqnbr: couldn’t get lock after 10 tries: /var/run/radius.seq
Dec 19 06:12:09 vgchuvicgamasp01 check_radius: rc_get_seqnbr: couldn’t get lock after 10 tries: /var/run/radius.seq
Dec 19 06:12:11 vgchuvicgamasp01 sssd[nss]: Starting up
Dec 19 06:12:37 vgchuvicgamasp01 sssd[ssh]: Starting up
Dec 19 06:13:03 vgchuvicgamasp01 NPCD[75327]: ERROR: Executed command exits with return code ‘7’
Dec 19 06:13:03 vgchuvicgamasp01 NPCD[75327]: ERROR: Command line was ‘/usr/lib/pnp4nagios/libexec/process_perfdata.pl -n --bulk /var/spool/icinga2/perfdata/host-perfdata.1576707034’
Dec 19 06:13:03 vgchuvicgamasp01 NPCD[75327]: ERROR: Executed command exits with return code ‘7’
Dec 19 06:13:03 vgchuvicgamasp01 NPCD[75327]: ERROR: Command line was ‘/usr/lib/pnp4nagios/libexec/process_perfdata.pl -n --bulk /var/spool/icinga2/perfdata/service-perfdata.1576707021’
#######
I changed the timeout value of the “/etc/pnp4nagios/process_perfdata.cfg” to 60 ,but my problem remained unresolved。

If anyone has a solution, please give me some hints. Thank you!

[root@icinga2server01 ~]# icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: v2.5.4)

Copyright © 2012-2016 Icinga Development Team (https://www.icinga.org/)
License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/gpl2.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Application information:
Installation root: /usr
Sysconf directory: /etc
Run directory: /var/run
Local state directory: /var
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /var/run/icinga2/icinga2.pid

System information:
Platform: Red Hat Enterprise Linux Server
Platform version: 6.10 (Santiago)
Kernel: Linux
Kernel version: 2.6.32-754.6.3.el6.x86_64
Architecture: x86_64

Build information:
Compiler: GNU 4.8.2
Build host: 10525b1d9830
[root@icinga2server01 ~]#

Hello and welcome.

Can you try and correlate this times to a backup window or an execution of a resource demanding task ?

This looks eerily like issues I encountered in the past that during the nightly backup the hosts became non responsive and then multiple alerts were sent.

If that is the case, you can create a timeperiod “backuptime”, and exclude the backup window from it’s definition and assign it to the host, that way if that is the case you are not monitoring the host during that event and can sleep better at night.

thank you for your information.
I will query the information related to backup according to your suggestion.