Service orphaned Issue

[sudha19rsan]

Hi,

In our production, we are running nagios version 3.4.1 in CentOS release 5.8 64 bit on Hyper-V Instances. Now a days we are facing number of issues in the service check with the below error.

Mar 13 01:47:46 XXXXXXXXX nagios: Warning: The check of service 'DEVICE_PING_STATUS' on host 'XXXXXX' looks like it was orphaned (results never came back). I'm scheduling an immediate check of the service...

All the service check has been orphaned and rescheduled for next 15 days or 7 days. Anyone suggest to resolve the issue.

Awaiting for your responses.

Regards
Sudharsan

[jolson]

Please read this document, which will help you troubleshoot the problem you're having: http://support.nagios.com/wiki/index.ph ... g_Orphaned

Let me know if any of the solutions work for you. I would start with the following:

Some users have encountered large numbers of warning messages that accumulate quickly that read as follows:

Warning: The check of service <Your Service> on host <Your Host> looks like it was orphaned (results never came back). I'm scheduling an immediate check of the service..

This is most likely caused by multiple instances of Nagios running. To fix this kill all instances of Nagios and then restart the process.

killall -9 nagios

Then restart Nagios from the Admin menu of the web interface.

[sudha19rsan]

Hi,

Again the same "service and host orphaned issue" persist on the nagios. I have tried out the following solutions

1) Killed the nagios multiple process threads
2) Increased the max concurrent check value and disabled the perl interrupter.
3) limit the memory limit in /etc/security/limits.conf

Still the issue persist , and no other work around solution to work with.

Could any one help me to resolve the same.

Regards
Sudharsan

[jdalrymple]

Did you try disabling embedded perl as indicated?

nagios.cfg:

Code: Select all

enable_embedded_perl=0
use_embedded_perl_implicitly=0

[sudha19rsan]

Ya I have disabled the embedded perl interpreter. Still searching for the permanent solution to fix the same. The issue was occurring regularly , the host and the services are orphaned and rescheduled for a week so that the monitored host and services are not monitored and altered as expected..

Regards
Sudharsan

[jdalrymple]

So the problem that you're seeking to fix isn't necessarily the orphaned bit but rather the rescheduled bit?

Can you supply us with your service definition? Specifically the retry_interval?

[sudha19rsan]

Please find the nagios.cfg file for your information specifically check intervals,

status_update_interval=10
# This is the interval at which Nagios should check for external commands.
# This value works of the interval_length you specify later. If you leave
# actual seconds rather than a multiple of the interval_length variable.
# scheduled intervals, Nagios will also check for external commands after
#command_check_interval=15s
command_check_interval=-1
auto_rescheduling_interval=30
# data at regular interval, but it will still save retention
retention_update_interval=60
# This is the seconds per unit interval as used in the
# that each interval is one minute long (60 seconds). Other settings
interval_length=60
#host_perfdata_file_processing_interval=0
#service_perfdata_file_processing_interval=0
# service performance data files. The interval at which the
service_freshness_check_interval=60
host_freshness_check_interval=60
service_perfdata_file_processing_interval=15
host_perfdata_file_processing_interval=15

Is their any possibility to fix the issue . Daily manually rescheduling the orphaned host and services using the web interface.

[sudha19rsan]

Enclosed the service definition sample for your perusal,

define service{
use switch-services
host_name XXXXXXXX
service_description DEVICE_PING_STATUS
check_command check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
contact_groups networkadmin
}

Service Check will happen every 5 mins and retry interval in 1 mins . Am i right ?

[abrist]

normal_check_interval 5
retry_check_interval 1

Are you using Manubulon and not Nagios? These directives are not nagios directives, as the nagios directives would be:

Code: Select all

check_interval 5
retry_interval 1

See:
http://nagios.sourceforge.net/docs/3_0/ ... tions.html
Also, the orphan issues are most likely due to resource limits on the kernel, what is the output of:

Code: Select all

ulimit -a

[sudha19rsan]

There is no limitation specified in the kernel level. Before that I have supplied the limitation on memory level in security limits but I have reverted due to this issue.

Only thing I have found that every host and service checks will be rescheduled for a while and result never come back. While checking the last check of the host it seems one week before the last check had been happened. So there is something need to be done on the nagios configuration file to.mitigate the issue. I m not sure where we need to supply the parameters for orphaned bits. One more thing I need to know why the service and host check has been orphaned ? Is this because of un availability of resources or anything thing else?