Andreas,

Issue has been resolved after changing "Maximum number of check attempts
for service" rule. thanks for you help.

Thanks,
Venkat

On Tue, Oct 4, 2016 at 3:43 PM, Andreas Döhler <andreas.doeh...@gmail.com>
wrote:

> Hi Venkat,
>
> inside your log you have a transition from Warning to Unknown and this is
> filtered with "?" as the system don't know the previous hard state. The
> system only knows the last soft state what was "warning".
> I think it is better to take a look at your rules for what you want to
> receive notifications.
> The import coding line for this behavior can be found inside
> "check_mk/modules/events.py" line 232 and following.
> Try to understand what the code does there (good comments why they make it
> this way).
> If you think this is a wrong behavior then write a message to the check_mk
> team in Munich.
>
> Best regards
> Andreas
>
> venkat ramu <ramut...@gmail.com> schrieb am Di., 4. Okt. 2016 um
> 09:13 Uhr:
>
>> Andreas,
>>
>> I have noticed (LASTSERVICESHORTSTATE=UNKN) in the notify log for the
>> service which are getting "? → WARNING". Any suggestion?
>>
>> [image: Inline image 1]
>>
>>
>>
>> Thanks,
>> Venkat
>>
>> On Tue, Oct 4, 2016 at 3:26 AM, Andreas Döhler <andreas.doeh...@gmail.com
>> > wrote:
>>
>> Hi Venkat,
>>
>> The next step would be to switch on the debug logging for the
>> notification. With the complete context of one notification inside log file
>> you can see what the notification script gets from Nagios.
>> If there is all correct then the error must be inside the notification
>> script.
>>
>> Best regards
>> Andreas
>>
>> venkat ramu <ramut...@gmail.com> schrieb am Mo., 3. Okt. 2016 um 17:46:
>>
>> Andreas,
>>
>> I am getting same event (?) even after enabling "log_initial_state = 1".
>>
>> Thanks,
>> Venkat
>>
>> On Sun, Oct 2, 2016 at 9:46 PM, Vye <v...@vye.me> wrote:
>>
>> I get the same events with "?" state using nagios. It seems to happen
>> randomly on 1.2.6. Initial state is preserved but it doesn't happen when
>> the core restarts, just periodically.
>>
>> --Vye
>> Sent from my iPhone
>>
>> On Oct 2, 2016, at 8:18 AM, Andreas Döhler <andreas.doeh...@gmail.com>
>> wrote:
>>
>> Hi Venkat,
>>
>> i think the service is not OK before. Or your system don't know the
>> status it is comming from. This happens if you have not the start status
>> inside the log file.
>> You can take a look at the Nagios configuration if the option
>> "log_initial_state" is set to 1.
>> If this is not set the core don't "know" the state of your service after
>> restart of the core and it is reporting the state change as from "?" to
>> something else.
>>
>> Best regards
>> Andreas
>>
>> venkat ramu <ramut...@gmail.com> schrieb am Sa., 1. Okt. 2016 um
>> 16:35 Uhr:
>>
>> Can someone help on this issue.
>>
>> Thanks,
>> Venkat
>>
>> On Thu, Sep 29, 2016 at 5:20 PM, venkat ramu <ramut...@gmail.com> wrote:
>>
>> Can someone tell me, what could be the wrong.
>>
>> Thanks,
>> Venkat
>>
>> On Thu, Sep 29, 2016 at 6:33 AM, venkat ramu <ramut...@gmail.com> wrote:
>>
>> Hi All,
>>
>> We are using Check_MK 1.2.8p11. We have enabled notification for services OK
>> ➤ WARN,OK ➤ CRIT,WARN ➤ OK, WARN ➤ CRIT,CRIT ➤ OK, CRIT ➤ WARN.  when
>> some services goes ok/warning to critical, in the Email, Event show *"?
>> → CRITICAL*", Can someone please let me know why *"? (Question)"* is in
>> the mail Instead of *OK → CRITICAL*
>>
>>
>> <image.png>
>>
>>
>>
>> Thanks,
>> Venkat
>>
>>
>>
>> _______________________________________________
>> checkmk-en mailing list
>> checkmk-en@lists.mathias-kettner.de
>> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
>>
>> _______________________________________________
>> checkmk-en mailing list
>> checkmk-en@lists.mathias-kettner.de
>> http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
>>
>>
>>
>>
>>
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Reply via email to