Marc Powell wrote:
On Mar 10, 2009, at 7:38 PM, Udo Müller wrote:
The problem is that i have the event_handler_enabled?
Yes, and notify-by-email specified as the event_handler.
I had the same misconfiguration under 2.x, and when I went to 3.x I
ended up making a cron job delete the nagios
Hi all,
I recently upgraded my nagios 2.x to 3.x. Nagios' preflight-check runs fine.
For service notification i use this event handler:
/usr/bin/printf %b * Nagios * Notification Type:
$NOTIFICATIONTYPE$ Service: $SERVICEDESC$ Host: $HOSTALIAS$ Address:
$HOSTADDRESS$ State:
On Mar 10, 2009, at 1:20 PM, Udo Müller wrote:
Hi all,
I recently upgraded my nagios 2.x to 3.x. Nagios' preflight-check
runs fine.
Is this an implication that this worked under 2.x?
For service notification i use this event handler:
/usr/bin/printf %b * Nagios * Notification
Marc Powell wrote:
On Mar 10, 2009, at 1:20 PM, Udo Müller wrote:
Hi all,
I recently upgraded my nagios 2.x to 3.x. Nagios' preflight-check
runs fine.
Is this an implication that this worked under 2.x?
Correct.
For service notification i use this event handler:
/usr/bin/printf %b
On Mar 10, 2009, at 7:38 PM, Udo Müller wrote:
I already read this and asked myself why nagios invokes that event
handler.
My configuration is e.g:
define service {
flap_detection_enabled0
check_freshness 0
check_period 24x7
Marc Powell wrote:
So will it help if i disable the event_handler_enabled?
Absolutely. Someone seems to have been changed this in your config
during the upgrade. None of this behavior has changed between (many)
versions.
Great. Works. TY for your help and the deeper look into nagios :)
