On Mon, May 2, 2011 at 6:15 PM, Papp Tamas <tom...@martos.bme.hu> wrote:
> I tried it because it's in wiki:
>
> http://www.shinken-monitoring.org/wiki/official/configuringshinken-objectdefinitions
>
> It's a bug in the wiki :)
It should have beed moved to the unmanaged properties part.
>
> The remove of the retention.dat is more strange. What retention module
> are you using for your scheduler (if I'm not wrong, there is none by
> default, but the easiest one to activate is the pickle- flat file- one).
>
>
> What do you mean about retention module? Is this something, I can change?
>
Yes, it's a module that you link with your scheduler in the
shinken-specific.cfg file.
>
> Anyway, this was me. Before I removed retention.dat than restarted shinken.
> This time stop, rm retention.dat, start and success, I see pendings:)
> And now here is the surprise, I got service notifications!
> Than I changed the address in the host definition, so it got DOWN and a
> notification was sent. Still OK.
> I changed the host address back, it got UP with no notification:
>
> [2011-05-02 17:52:51] HOST ALERT: cindy;UP;HARD;10;OK - 192.168.232.55:
> rta 0.040ms, lost 0%
> [2011-05-02 17:52:04] SERVICE ALERT: cindy;ssh;OK;HARD;3;SSH OK -
> OpenSSH_4.3 (protocol 2.0)
> [2011-05-02 17:43:38] HOST ALERT: cindy;DOWN;HARD;10;CRITICAL -
> 192.168.232.56: Host unreachable @ 192.168.232.89. rta nan, lost 100%
> [2011-05-02 17:43:38] HOST NOTIFICATION:
> tompos;cindy;DOWN;notify-host-by-email;CRITICAL - 192.168.232.56: Host
> unreachable @ 192.168.232.89. rta nan, lost 100%
>
>
> I also have some question again.
>
> 1. Why was SERVICE ALERT before HOST ALERT? My guess is and documentation
> says HOST SATE is checked before SERVICE STATE. Or I misunderstanding
> something?
>
Yes, when the service got a problem, the host is checked too. But the ALERT
in the log is still here, after all the service got a problem.
>
> 2. Why was them not in SOFT UP before HARD UP?
>
When you are HARD DOWN, the next UP is a HARD one, there is no soft state
for this recovery part. Like for Nagios.
>
> 3. Why was not made a notification?;)
>
For the host? I can be your host notification configuration (must got the r
option) or your contact one (same option :) ).
>
> 4. If I understand the documentation and your suggestion well, SERVICE
> ALERTS depend on HOST STATE? In other words if HOST STATE IS DOWN, there is
> no SERVICE ALERT (CHECK?).
>
Services are checks, but service notification are not send. It only send
notification about the root problem, not about impacts :)
Jean
>
> Thank you,
>
> tamas
>
>
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
