Results 1 to 4 of 4

Thread: Restarting arbiter resumes disabled notifications

  1. #1
    Junior Member
    Join Date
    Oct 2012
    Posts
    6

    Restarting arbiter resumes disabled notifications

    Hey there,

    A bit of context:
    When we're adding a new host and it's services to shinken, a common way we do things is to disable notifications on the host while we tweak the settings on shinken or on the monitored host until we get all the expected results. This way, we avoid false alarms being sent all over the place.

    The problem:
    Whenever we restart the arbiter to take into account the configuration modifications we've made, shinken removes the disabled notifications on the hosts and services.
    Are we doing something wrong or is this expected behaviour ? We'd prefer that notification settings be preserved across arbiter restarts.

    Retention is configured and stored in .dat flat files in the tmp directory - shinken has access to those files.

    Thanks !

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

    Re: Restarting arbiter resumes disabled notifications

    Ypou retention modules should have a problems, look at scheduler.log for details.
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Junior Member
    Join Date
    Oct 2012
    Posts
    6

    Re: Restarting arbiter resumes disabled notifications

    Retention seems to be done hourly and I don't see anything that could prove to be an issue - no errors.

    When I restart arbiter, this is what is shown in the scheduler log:
    Code:
    2012-10-10 07:18:40,390 [1349867920] [PickleRetentionGeneric] asking me to update the retention objects
    
    2012-10-10 07:18:40,438 [1349867920] Updating retention_file /tmp/retention.dat
    
    2012-10-10 07:18:40,439 [1349867920] Waiting for initial configuration
    
    2012-10-10 07:18:40,441 [1349867920] Warning in importing module : No module named android
    
    2012-10-10 07:18:40,441 [1349867920] Warning in importing module : No module named redis
    
    2012-10-10 07:18:40,442 [1349867920] Warning in importing module : No module named org.shinken_monitoring.tsca
    
    2012-10-10 07:18:40,443 [1349867920] Warning in importing module : No module named ldap
    
    2012-10-10 07:18:40,443 [1349867920] Warning in importing module : No module named memcache
    
    2012-10-10 07:18:40,444 [1349867920] Warning in importing module : cannot import name out_map
    
    2012-10-10 07:18:40,444 [1349867920] Trying to init module : PickleRetention
    
    2012-10-10 07:18:40,444 [1349867920] I correctly loaded the modules : [PickleRetention]
    
    2012-10-10 07:18:40,450 [1349867920] [PickleRetentionGeneric]Reading from retention_file /tmp/retention.dat
    
    2012-10-10 07:18:40,503 [1349867920] [PickleRetentionGeneric] OK we've load data from retention file
    Can you point me in the right direction ?

  4. #4
    Junior Member
    Join Date
    Oct 2012
    Posts
    6

    Re: Restarting arbiter resumes disabled notifications

    After doing some more research, I've come across this bug: https://github.com/naparuba/shinken/issues/560

    I'll try and see if 1.2 solves the issue and report back.

Posting Permissions

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