Page 2 of 2
Re: Orphaned checks.
Posted: Sat Jul 07, 2018 9:41 am
by linuxnerd
i made the suggested changes and am still seeing the warning.
my limits.conf:
Code: Select all
#locked memory
* hard memlock 256
* soft memlock 256
#open files
* soft nofile 40960
* hard nofile 40960
#max user processes
* hard nproc 32768
* soft nproc 32768
#stack size
* hard stack 131072
* soft stack 131072
Re: Orphaned checks.
Posted: Tue Jul 10, 2018 5:12 am
by linuxnerd
i should have stated that this is a distributed setup where multiple nodes are performing active checks and sending the results to a 'master' node via ocsp / ncsa.
when i set obsess_over_service = 0, the problem goes away.
it seems like checks are delayed until all the ocsp handlers finish executing.
is there a way to have checks continue while the ocsp handler is still handler?
Re: Orphaned checks.
Posted: Tue Jul 10, 2018 8:21 am
by scottwilkerson
linuxnerd wrote:i should have stated that this is a distributed setup where multiple nodes are performing active checks and sending the results to a 'master' node via ocsp / ncsa.
when i set obsess_over_service = 0, the problem goes away.
it seems like checks are delayed until all the ocsp handlers finish executing.
is there a way to have checks continue while the ocsp handler is still handler?
I believe this was resolved in Nagios Core version > 4
Re: Orphaned checks.
Posted: Tue Jul 10, 2018 11:12 am
by linuxnerd
i managed to workaround the problem by spooling the check results into a buffer directory, then run a diff script to batch send the results to nsca.
Re: Orphaned checks.
Posted: Tue Jul 10, 2018 3:21 pm
by scottwilkerson
linuxnerd wrote:i managed to workaround the problem by spooling the check results into a buffer directory, then run a diff script to batch send the results to nsca.
that sounds like a better solution. Glad you were able to work it out.
Closing