-
Notifications
You must be signed in to change notification settings - Fork 579
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 #7576] validate configured legacy timeperiod ranges #2194
Comments
Updated by mfriedrich on 2014-11-05 08:25:28 00:00 "use" in ranges is invalid. Where does that config come from? The error is sourced from this
Please show the object configuration of that file. |
Updated by mfriedrich on 2014-11-05 08:26:18 00:00
|
Updated by JayNewman on 2014-11-05 13:05:13 00:00 Thank you, you are quite correct - the "use" statement was improperly located in the config file. I updated the configuration , am still having problems. Have included below the entire file where I define timeperiods.
|
Updated by JayNewman on 2014-11-05 14:29:31 00:00 Update :
Do I have an error in the above definitions? and should this be planned for future development to be caught during checkconfig ? Cheers |
Updated by mfriedrich on 2014-11-11 21:58:18 00:00
is, for example, an invalid range. That obviously comes from an external source as well. There is an issue open for validating timeperiod definitions properly, but as you may have figured already, that format is a pain to validate and parse. And #6070 holds the general issue for improving error messages. |
Updated by mfriedrich on 2014-11-11 21:58:26 00:00
|
Updated by mfriedrich on 2014-11-11 21:59:08 00:00
|
Updated by mfriedrich on 2014-11-11 22:01:09 00:00
|
Updated by mfriedrich on 2014-11-24 12:33:14 00:00
To-do:
|
Updated by gbeutner on 2015-01-08 12:40:56 00:00
|
Updated by tobiasvdk on 2015-01-17 21:41:46 00:00
|
Updated by mfriedrich on 2015-01-23 10:04:08 00:00
|
Updated by mfriedrich on 2015-01-26 15:05:58 00:00
|
Updated by mfriedrich on 2015-02-09 09:29:15 00:00
|
Updated by mfriedrich on 2015-02-09 12:19:00 00:00
|
Updated by mfriedrich on 2015-02-09 12:34:03 00:00
|
Updated by gbeutner on 2015-02-13 09:53:47 00:00
|
Updated by mfriedrich on 2015-02-13 16:21:34 00:00
|
Updated by Anonymous on 2015-02-13 16:25:03 00:00
Applied in changeset 2ed78e8. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7576
Created by JayNewman on 2014-11-05 04:15:24 00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-02-13 16:25:02 00:00)
Target Version: 2.3.0
Last Update: 2015-02-13 16:25:02 00:00 (in Redmine)
Problem
TimePeriod ranges are checked at runtime and generate ugly exceptions.
Solution
Original Report
/etc/init.d/icinga2 checkconfig completes without errors.
However, performing a service restart generates an issue :
I tried commenting out the 1 time period configuration , and the error moved on to the next configuration in the file.
Here is the part of the configuration that caused the above error:
Changesets
2015-02-13 16:10:58 00:00 by (unknown) 2ed78e8
Relations:
The text was updated successfully, but these errors were encountered: