That means you have an other file in which the command notify-host-by-email
is also defined. grep the command's name to find where. You will probably have
the same problem for the notify-service-by-email.
I had the same problem when I installed NagiosQL and I solved it by setting
Nagios to use
On Feb 12, 2009, at 20:26, Israel Brewster isr...@frontierflying.com wrote:
Well, since you are writing the OCSP command script, you should be
able to have the script itself Filter for hosts you want, i.e if
$HOSTNAME$=hostA or hostB, etc then run script, otherwise, do nothing.
Yes, I
On Feb 12, 2009, at 20:37, Max perld...@webwizarddesign.com wrote :
How about setting the notification command in the service to a null
command of some sort and using a service escalation with the
escalation states critical, warning, and ok all set and a
first_notification value of 1 so that
Hi,
Sorry if that question had already been answered but I couldn't find any answer
by searching on the web and on the Nagios-User mailing list.
I would like to create a service which will notify me after each check, even if
it is an OK-state and if the state hadn't changed.
I've tried by
Thank you very much for the lead. It helped me a lot and.
I followed your advice and I used the ocsp_command directive from the
nagios.cfg with a script printing into the file nagios.cmd the external command
SEND_CUSTOM_SVC_NOTIFICATION and it works fine now.
Thanks for the lead.
- Mail
There is still a small problem though... With that method, every service with
obsess_over_service enabled will execute the command, and every command defined
as ocsp_command in nagios.cfg will be executed by services enabling
obsess_over_service :s.
Well... don't know if ther is a better way
