Page 2 of 2
Re: Lame Service definition Warning?
Posted: Wed Jul 02, 2014 6:23 pm
by rajasegar
tmcdonald wrote:Right about here:
view.png
No wonder, usually the diskette icon is for saving so I did not click on that.
Here is the code which looks exactly the same.
Code: Select all
define servicedependency {
dependent_host_name MY1PIRR1
dependent_service_description MIMIX Repl Group2
host_name MY1PIRR1
service_description MIMIX Repl Group1
inherits_parent 1
execution_failure_criteria n,
notification_failure_criteria n,
dependency_period 24x7
}
Re: Lame Service definition Warning?
Posted: Thu Jul 03, 2014 1:43 pm
by tmcdonald
The issue here is that dependent_host_name and host_name do not mean the same thing, but you have them set to be.
The dependent_host_name should be set to the host_name of the host that your dependent service runs on. So if ServiceB on HostB is dependent on ServiceA on HostA, you would want this layout:
Code: Select all
define servicedependency {
dependent_host_name HostB
dependent_service_description ServiceB
host_name HostA
service_description ServiceA
inherits_parent 1
execution_failure_criteria n
notification_failure_criteria n
dependency_period 24x7
}
Re: Lame Service definition Warning?
Posted: Thu Jul 03, 2014 1:47 pm
by lmiltchev
What happens when you specify anything other than "n" (none) for the "Execution failure criteria" and "Notification failure criteria"? Do you still get the "lame service definition warning"?
Re: Lame Service definition Warning?
Posted: Thu Jul 03, 2014 7:06 pm
by rajasegar
lmiltchev wrote:What happens when you specify anything other than "n" (none) for the "Execution failure criteria" and "Notification failure criteria"? Do you still get the "lame service definition warning"?
Changed to the following, no more lame message.
Code: Select all
define servicedependency {
dependent_host_name MY1PIRR1
dependent_service_description MIMIX Repl Group2
host_name MY1PIRR1
service_description MIMIX Repl Group1
inherits_parent 1
execution_failure_criteria c,
notification_failure_criteria c,
dependency_period 24x7
}