Results 1 to 7 of 7

Thread: WS Arbiter configuration & problem

  1. #1
    Junior Member
    Join Date
    May 2014
    Location
    Bordeaux - France
    Posts
    17

    WS Arbiter configuration & problem

    Hello everyone,

    I'm trying to set some passive check on my infrastructure. I read some documentation about ws arbiter and it's looks cool and simple.
    I just have some question :

    1. Is it possible to send the push result on the port 80 ?
    I tested to change the port in the ws_arbiter.cfg but after the change, it's not working.

    2. Do i need to configure something for email notification ?
    When a push notification send a return code (warning or critical) i didn't receive a mail. I can see them on the webui but no notification.

    3. The cron works every minutes on my system. Sometime the state of a service change (from ok to warning) between to check. Does shinken require minimum periode check or it's a bug ?

    Thank you for help

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: WS Arbiter configuration & problem

    1: no, port 80 need root account, and won't be possible with the shinken user. Use a reverse proxy for such case.
    2: wrong notification configuration. Drop your retention to be sure your configuration is loaded like you want
    3: the minimum is 2s between status
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    May 2014
    Location
    Bordeaux - France
    Posts
    17

    Re: WS Arbiter configuration & problem

    Thank you for the answers.

    It's looks like my shinken still has enabled the actif check for this host. So some time, i have on the webui [error] no plugin or directory (something like that ).

    The actif host check is disable but when i selected a service, actif check is still enable. My configuration of my host is :

    Code:
    define host{
        use           services-linux
        contact_groups     admins
        host_name        passive
        passive_checks_enabled 1
        active_checks_enabled  0
        contact_groups     admins
        notifications_enabled  1
        }

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: WS Arbiter configuration & problem

    What about retention drop?
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5
    Junior Member
    Join Date
    May 2014
    Location
    Bordeaux - France
    Posts
    17

    Re: WS Arbiter configuration & problem

    Yes it was a problem with the retention. If i disable the retention i have no problem.
    I used the mongodb retention. So for the moment i disable this retention.

    What i need to do to enable the retention with active and passive check ?

    Thank you for your help

  6. #6
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: WS Arbiter configuration & problem

    If you are useing a recent shinekn version theses values are taken from conf and no more from retention, that's all
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #7
    Junior Member
    Join Date
    May 2014
    Location
    Bordeaux - France
    Posts
    17
    I use shinken 2.0.2, but i didn't understand what i need to change on my configuration. I need to change the shinken.cfg file ?

    And i have one more question about ws_arbiter. Is it possible to change the state of host if the ws_arbiter doesn't receive a notification for the last 5 min ?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •