Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

  1. #1
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    Hi,

    I scheduled a downtime this morning for 3 hosts.
    I then added a new downtime to extend the first one.

    Now I'm a weird state, where I can't install any more downtime for these hosts : when I do it from Thruk, it adds a comment about the downtime, but the hosts is NOT marked as downtime'd and continues to send notifications.
    I tried removing and re-adding all notifications, restarting Shinken - the host still won't go downtime.
    Also, when looking at ShinkenUI, the host is marked as "In Scheduled Downtime : Yes", but with no associated downtime.

    It looks like there an inconsistency between Shinken and Thruk.
    Is there a way to "reset" the downtime state, preferably without removing the retention file ?

  2. #2
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    After inspecting retention.dat through pickle, I see :
    Code:
    [('in_scheduled_downtime_during_last_check', False),
     ('pending_flex_downtime', 0),
     ('in_scheduled_downtime', True),
     ('scheduled_downtime_depth', -5)]
    Resetting 'in_scheduled_downtime'=False and 'scheduled_downtime_depth'=0 fixed the issue, but this is quite a complex way to solve the issue.

    Any idea about :
    - where the bug comes from
    - how to more easily reset the downtime status ?

  3. #3
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    More on my manipulation of the retention file at : http://www.shinken-monitoring.org/wi...roubleshooting

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

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    There should be a Downtime object in the pickle data too. If not, there is a problem I think.
    No direct support by personal message. Please open a thread so everyone can see the solution

  5. #5
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    When I [tt]print[/tt] the pickle data and grep it, I find no "retention" at all (case insensitive) :-\

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

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    no shinken.Downtime objects at all?
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #7
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    Well, as far as I can see there's only scalar values in the retention file

  8. #8
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    Ah, I missed a shinken.downtime.Downtime instance in ['hosts']['myhost']['downtimes'][0], indeed.

  9. #9
    Junior Member
    Join Date
    Apr 2013
    Posts
    20

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    OK, something is wrong I removed the retention file and re-scheduled a clean downtime, still the same behavior, and this in the retention file :
    Code:
     ('in_scheduled_downtime_during_last_check', False),
     ('pending_flex_downtime', 0),
     ('downtimes', [<shinken.downtime.Downtime instance at 0x18ef7a0>]),
     ('in_scheduled_downtime', False),
     ('scheduled_downtime_depth', 0)
    Note the 'in_scheduled_downtime'=False.
    The downtime was scheduled with the current date + 2h, flexible.

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

    Re: Thruk/ShinkenUI downtime inconsistency - can't add a new downtime

    Start at current date, or begin at current date +2 h?

    The object got the entry_time property to see the unixtime of the start.
    No direct support by personal message. Please open a thread so everyone can see the solution

Posting Permissions

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