On 05/02/2011 09:30 AM, nap wrote:

Also it says:
[1304269057] Checking notificationways...
[1304269057]    Checked 3 notificationways

I defined only one of it:

I don't know if this is a shinken or an omd problem. My guess is
shinken. Please let me know, if you need more information.
I suppose you got 2 contacts isn't it?
In fact, when you define a contact with a "old school definition" (commands+period in the contact definition) shinken autogenerate a notification-way with theses values, and link it to your contact. But I do not unsderstand why you get notification by group of 2, is the shinken.log say it launch it twice or not?

Now this is the configuration, I use:

define contactgroup {
    contactgroup_name        jm-admins
    alias                                 Admins
    members                         tompos

define contact {
    name                                _contact
    can_submit_commands    1
    notificationways                email
    register                             0

define contact {
    use                             _contact
    contact_name            tompos
    alias                           Tamas Papp
    email                          tamas.papp@foo.bar

define notificationway {
    notificationway_name                  email
    host_notification_commands        notify-host-by-email
    host_notification_period               24x7
    host_notification_options              d,u,r,f,s
    service_notification_commands   notify-service-by-email
    service_notification_period          24x7
    service_notification_options         w,u,c,r,f

define host {
    use                                         host-pnp
    name                                      _host
    hostgroups                             jm-hosts
    contact_groups                      jm-admins
    max_check_attempts            10
    notification_interval               60
    check_period                         24x7
    notification_period                 24x7
    check_command                   check-host-alive
    check_interval                            0    ; set it to 0 if you want checks only on STATUS change
    retain_status_information          0    ; do not use status after restart
    retain_nonstatus_information    0
    register                                      0

define host {
    use                            _host
    host_name                svn
    alias                          svn

No shinken says, it has two notificationways. How can I dump the whole of the current used configuration, like the object.cache for nagios?

As I can see, notifications still are handled only for host alerts and shinken makes a host alert notification in every hour as defined by notification_interval. Service alerts are not sent and it doesn't care about state changes.

And there is another thing. As you can see, ratain_(non)status_information is 0. If I see well, it should restart checks from the state PENDING on every restart. It does not do it, every state is preserved. Even if I remove the file retention.dat.

What do I miss?;)

Thank you,