Gap in perf data : fork my_system_r failed
Posted: Wed Dec 09, 2015 12:31 pm
Hi guys,
We have XI 2014R.7.
Last night and into morning we have a gap in all our performance data in our PRODUCTION environment.
Nagios.log (indicating issue)
[Tue Dec 8 17:20:18 2015] Warning: fork() in my_system_r() failed for command "/bin/mv /usr/local/nagios/var/service-perfdata /usr/local/nagios/var/spool/xidpe/1449613218.perfdata.service"
NPCD.log (indicates gap in perf data)
[12-08-2015 22:48:25] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1449632884.perfdata.service'
[12-09-2015 11:08:15] NPCD: ERROR: Executed command exits with return code '1'
There is no system error in /var/log/messages. Our ulimit is below. Any idea why this issue would occur? And why it would suddenly clear up at that time? Thx.
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 95125
max locked memory (kbytes, -l) 128
max memory size (kbytes, -m) unlimited
open files (-n) 4096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 20480
cpu time (seconds, -t) unlimited
max user processes (-u) 4096
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
We have XI 2014R.7.
Last night and into morning we have a gap in all our performance data in our PRODUCTION environment.
Nagios.log (indicating issue)
[Tue Dec 8 17:20:18 2015] Warning: fork() in my_system_r() failed for command "/bin/mv /usr/local/nagios/var/service-perfdata /usr/local/nagios/var/spool/xidpe/1449613218.perfdata.service"
NPCD.log (indicates gap in perf data)
[12-08-2015 22:48:25] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1449632884.perfdata.service'
[12-09-2015 11:08:15] NPCD: ERROR: Executed command exits with return code '1'
There is no system error in /var/log/messages. Our ulimit is below. Any idea why this issue would occur? And why it would suddenly clear up at that time? Thx.
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 95125
max locked memory (kbytes, -l) 128
max memory size (kbytes, -m) unlimited
open files (-n) 4096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 20480
cpu time (seconds, -t) unlimited
max user processes (-u) 4096
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited