New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #11158] Crash with empty ScheduledDowntime 'ranges' attribute #3938
Comments
Updated by mfriedrich on 2016-02-22 19:12:25 +00:00
Try using a string as key to the "downtimes" dictionary you are referring to in your downtimes.conf
|
Updated by nE0sIghT on 2016-02-24 09:37:05 +00:00 dnsmichi wrote:
No changes |
Updated by mfriedrich on 2016-03-04 16:50:46 +00:00
|
Updated by mfriedrich on 2016-03-04 16:50:55 +00:00
|
Updated by mfriedrich on 2016-03-18 13:09:25 +00:00
Hm, can you try renaming the key in your apply for loop to something different than 'name'?
|
Updated by nE0sIghT on 2016-03-21 08:50:28 +00:00 dnsmichi wrote:
Changed to
Same failure |
Updated by mfriedrich on 2016-04-22 08:50:23 +00:00 Ok, found it. "ranges" is not assigned and therefore empty. That crashes inside FindNextSegment().
|
Updated by mfriedrich on 2016-04-22 08:56:34 +00:00 The thing is, the configuration is wrong. Setting the ScheduledDowntime ranges must happen differently. I've added an advanced example checking for the variables being set and with their proper type.
This generates the following downtime object:
I'll fix the crash though. |
Updated by mfriedrich on 2016-04-22 09:01:08 +00:00
|
Updated by mfriedrich on 2016-04-22 09:05:04 +00:00
Applied in changeset 7442cd9. |
Updated by mfriedrich on 2016-05-02 13:26:33 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11158
Created by nE0sIghT on 2016-02-15 08:40:15 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-04-22 09:05:04 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-02 13:26:32 +00:00 (in Redmine)
With attached configuration my icinga instance failing silently with return code 1.
No information provided in config file nor errors presented in icinga output.
The problem block is in conf.d/services/kscp/interfaces/askro.conf
With that block commented out icinga starts normally.
My OS environment is Oracle EL 7.
Attachments
Changesets
2016-04-22 09:00:21 +00:00 by mfriedrich 7442cd9
2016-05-12 09:08:20 +00:00 by mfriedrich 418636f
The text was updated successfully, but these errors were encountered: