Re-send: Notificaitons after the commit

[Yu Watanabe]

Hello Robert.

I would use that instead...

Would you please give us an advice to my question?

Whenever nagios restarts, is there any affection to the service notification sequence
that has been occuring every 24hours on a certain service?

For example, 

  If notification is occuring every 8:00 a.m. remaining the same CRITICAL status, and if a restart occurs like 10:00 p.m.

  [2010/01/13 22:24:06] Caught SIGTERM, shutting down...
  [2010/01/13 22:24:06] Successfully shutdown... (PID=31954)

  would the notification stops for a next day and be sent on the next , next day?

Thank you,
Yu Watanabe

Robert Wolfe さんは書きました:
>I am curious here...
>
>If all you are doing is restarting Nagios, why not just use:
>
>	/etc/init.d/nagios restart
>
>Instead of all the other commands and parameters?
>
>-----Original Message-----
>From: Yu Watanabe [mailto:yu.watanabe at jp.fujitsu.com] 
>Sent: Tuesday, March 02, 2010 9:12 AM
>To: Assaf Flatto
>Cc: nagios-users at lists.sourceforge.net
>Subject: Re: [Nagios-users] Re-send: Notificaitons after the commit
>
>Hello Assaf
>
>Sorry, for ambiguous expression.
>
>Word "Commit", I used in the meaning of executing the following command,
>
>/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
>/etc/init.d/nagios restart
>
>And yes. After the above command, the notification that was been occuring every 24hours before then
>suddenly stopped. So, I doubted the restart procedure if this is doing something wrond.
>
>Thank you
>Yu Watanabe
>
>Assaf Flatto さんは書きました:
>>Yu Watanabe wrote:
>>> Hello all.
>>>
>>> I am re-sending the message again. Message seems to be not sent properly.
>>> I apologize if this becomes duplicate message.
>>> -----------------------------------------------------------------------------------
>>>
>>> I have a question about the notifications after the commit. 
>>> I am wondering whether nagios refreshes the notification history event though the state retention option
>>> is specified.
>>>
>>> Could someone help us out?
>>>
>>> I am using the Nagios v3.0.6 and following is the situation:
>>>
>>> 1. Service Notification interval is set as 24h
>>> 2. Host status is UP at that time
>>> 3. Normal check interval is set 24h
>>>
>>> Following is the history from the nagios.log:
>>>
>>> * HARD status change had occured at Jan 11 08:35 . Notification has been sent at 08:35
>>> * Notification was sent at Jan 12 08:35
>>> * Notification was sent at Jan 13 08:35
>>> * Commit was executed at Jan 13 22:24
>>> * Notification was not sent at Jan 14 08:35 <--** This is the problem ***
>>> * Recovery status change had occured from CRITICAL -> OK at Jan 15 08:35. Notification has been sent at 08:35.
>>>
>>> I thought that Nagios inherits the last notification time when it restarts using the nagiostatus.sav. 
>>> But it seems to be not the case for this time.
>>>
>>> Could someone give us an advice?
>>>
>>> Thank you.
>>> Yu Watanabe
>>>   
>>When you say commit  ? what exactly do you mean ?
>>are you committing code upstream of nagios and then testing it on your 
>>system ?
>>are you performing some action and then the alerts are not generated ?
>>
>>Please provide more information - or clarify what you mean.
>>
>>Assaf
>>
>>------------------------------------------------------------------------------
>>Download Intel® Parallel Studio Eval
>>Try the new software tools for yourself. Speed compiling, find bugs
>>proactively, and fine-tune applications for parallel performance.
>>See why Intel Parallel Studio got high marks during beta.
>>http://p.sf.net/sfu/intel-sw-dev
>>_______________________________________________
>>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
>>
>
>
>------------------------------------------------------------------------------
>Download Intel® Parallel Studio Eval
>Try the new software tools for yourself. Speed compiling, find bugs
>proactively, and fine-tune applications for parallel performance.
>See why Intel Parallel Studio got high marks during beta.
>http://p.sf.net/sfu/intel-sw-dev
>_______________________________________________
>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
>


**********************************************************************
FUJITSU SOCIAL SCIENCE LABORATORY LIMITED(FUJITSU SSL)

System Infrastructure Development Department
Telecom Sstems Business Group 2

   Yu Watanabe

    E-Mail : yu.watanabe at jp.fujitsu.com
    Phone  : 044-739-1427 +5283

**********************************************************************


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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