On XI Install, with about 2800 hosts and 7500 services configured, we are witnessing a lot of "Warning: The check of service 'Total Processes' on host 'xyz' looks like it was orphaned (results never came back" messages.
We have ensured that Cron interval to submit passive check result and the freshness checks are adequately spaced apart. (i.e. 15 mins, and 23mins) We are also seeing temporary files coming in momentarily under /var/nagiosramdisk/spool/checkresults folder. (have setup Ramdisk for performance)
We understand this condition occurs only if the passive results are not updated back to Nagios. Are there any troubleshooting steps we can follow? I do not find a setting where I can enable debug for NRDP.
The permissions seems right.
[server]# groups apache
apache : apache nagios nagcmd
[server]# ls -l /usr/local/nagiosxi/
drwsrwsr-x 21 nagios nagios 12288 Apr 6 03:57 tmp
Any thoughts?
Thank you,
Vasudevan
Too many Orphaned messages in Log Forcing freshness
Re: Too many Orphaned messages in Log Forcing freshness
https://support.nagios.com/kb/article.php?id=19 covers some common causes and troubleshooting steps. Review this and let us know if your results or if you have any questions.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Too many Orphaned messages in Log Forcing freshness
Hi There,
Thank you for the KB. I have followed through and modified the ulimit parameters as suggested in the article. Did not help much. We have now moved out the DB to a separate host, the warning appears to have gone away, but will watch out for couple of more days.
Thank you for the support.
Regards,
Vasudevan
Thank you for the KB. I have followed through and modified the ulimit parameters as suggested in the article. Did not help much. We have now moved out the DB to a separate host, the warning appears to have gone away, but will watch out for couple of more days.
Thank you for the support.
Regards,
Vasudevan
Re: Too many Orphaned messages in Log Forcing freshness
Thanks for the update. Hopefully moving the database helps you a bit more.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Too many Orphaned messages in Log Forcing freshness
The orphaned messages have reduced after moving the database to an independent server, however it has not gone away. Also We are seeing the following intermittently.
"Could not stat() check result file '/var/nagiosramdisk/spool/checkresults/cgHVquV'
I am wondering if this is the cause of orphaned messages, since this spool directory is what NRDS is pointing to.
"Could not stat() check result file '/var/nagiosramdisk/spool/checkresults/cgHVquV'
I am wondering if this is the cause of orphaned messages, since this spool directory is what NRDS is pointing to.
Re: Too many Orphaned messages in Log Forcing freshness
Thanks for the update. PM me a profile(Admin > System Profile > Download Profile) and I'll take a closer look.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.