Results 1 to 2 of 2

Thread: Service notifications not being sent for ~24 hours after config reload

  1. #1
    Junior Member
    Join Date
    Apr 2014
    Posts
    6

    Service notifications not being sent for ~24 hours after config reload

    I am currently migrating with a config that worked with Shinken 1.4 to Shinken 2.x.

    It appears that whenever the config is reloaded service notifications are suppressed for approximately 24 hours, this does not appear to affect host notifications at all. I pulled the latest 2.4 branch this morning and am observing identical behaviour.

    Unfortunately this is a huge concern as we have a config that changes on a daily basis and as such we are not receiving any service notifications other than on weekends.

    I have the minimal config that I have observed this behaviour with attached,Any thoughts on possible causes, or where to look for the issue?
    Attached Files Attached Files

  2. #2
    Junior Member
    Join Date
    Apr 2014
    Posts
    6
    Managed to get this partially resolved, apparently the combination of my daily schedule, the system clock being set to utc, and generic-service having its notification period set to "workdays" rather than 24x7 caused notification to appeared to stop several hours after we applied updates. Stupid oversights.

Posting Permissions

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