notifications

[alexus]

On Thu, Sep 24, 2009 at 1:49 PM, Marc Powell <marc at ena.com> wrote:
>
> On Sep 24, 2009, at 12:05 PM, alexus wrote:
>
>> On Thu, Sep 24, 2009 at 12:19 PM, Marc Powell <marc at ena.com> wrote:
>>> 2009/9/19 alexus <alexus at gmail.com>:
>
>>> *From objects.cache* --
>>>
>>> host definition
>>
>> define host {
>
> looks good
>
>>> service definition
>>
>> define service {
>
> looks good.
>
>>> contactgroup definition
>>
>> define contactgroup {
>>        contactgroup_name       staff
>>        alias   alexusbiz corp.
>>        members dmitry chorine
>
> I haven't seen anyone use contact names with spaces in them but I'm
> not aware of any reason it wouldn't work.
>
>>> contact definition
>>
>> define contact {
>
> This looks good as well.
>
>>> the service notification command{} definition for the contact
>>
>> define command {
>
> Fine.
>
>>> all referenced timeperiod definitions
>>
>> define timeperiod {
>
> Here too...
>
> Nothing obviously wrong with the object configs that I can see.
>
>>>  From nagios.log --
>>>
>>> all entries related to this host or service around the time you
>>> expect
>>> a notification to be sent.
>>
>> -bash-3.2# grep dummy nagios.log
>> [1253764800] CURRENT SERVICE STATE: jothost.j;dummy;CRITICAL;HARD;
>> 3;CRITICAL
>> [1253807636] SERVICE ALERT: jothost.j;dummy;CRITICAL;SOFT;1;CRITICAL
>> [1253807696] SERVICE ALERT: jothost.j;dummy;CRITICAL;SOFT;2;CRITICAL
>> [1253807756] SERVICE ALERT: jothost.j;dummy;CRITICAL;HARD;3;CRITICAL
>
> Yet nagios doesn't believe that it's supposed to attempt a notification
>
>>> Also, verify in the web interface that notifications are enabled for
>>> the host and service and that it is not in a period of scheduled
>>> downtime.
>
> Did you check the web interface to verify that notifications for the
> specific service are enabled? You should also check under 'Process
> Info' to make sure notifications are enabled program wide
> (enable_notifications 1 in nagios.cfg).

through web i see notifications is enabled

if this would be disabled i wouldn't get any notifications, yet some
of notifications i'm getting and some not...

-bash-3.2# grep enable_notifications ~nagios/etc/nagios.cfg
enable_notifications=1
-bash-3.2#


>
> Both of these options can be disabled in the web interface. Since you
> appear to be using retention, those settings will be remembered
> between restarts and will take precedence over config file/
> objects.cache settings. You can see the current settings for these
> types of things in the status.dat file but using the web interface is
> usually easier.
>

this is from status.dat

servicestatus {
        host_name=jothost.j
        service_description=dummy
        modified_attributes=0
        check_command=check_dummy!2
        check_period=247
        notification_period=247
        check_interval=2.000000
        retry_interval=1.000000
        event_handler=
        has_been_checked=1
        should_be_scheduled=1
        check_execution_time=0.006
        check_latency=0.221
        check_type=0
        current_state=2
        last_hard_state=2
        last_event_id=0
        current_event_id=3158
        current_problem_id=1526
        last_problem_id=0
        current_attempt=3
        max_attempts=3
        state_type=1
        last_state_change=1253807626
        last_hard_state_change=1253807746
        last_time_ok=0
        last_time_warning=0
        last_time_unknown=0
        last_time_critical=1253824786
        plugin_output=CRITICAL
        long_plugin_output=
        performance_data=
        last_check=1253824786
        next_check=1253824906
        check_options=0
        current_notification_number=0
        current_notification_id=0
        last_notification=0
        next_notification=0
        no_more_notifications=0
        notifications_enabled=1
        active_checks_enabled=1
        passive_checks_enabled=1
        event_handler_enabled=1
        problem_has_been_acknowledged=0
        acknowledgement_type=0
        flap_detection_enabled=1
        failure_prediction_enabled=1
        process_performance_data=1
        obsess_over_service=1
        last_update=1253824866
        is_flapping=0
        percent_state_change=0.00
        scheduled_downtime_depth=0
        }


> --
> Marc
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>



-- 
http://alexus.org/

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null