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 #6148] Config validator: Make sure that objects are not abstract. #1523
Comments
Updated by mfriedrich on 2014-05-08 12:06:30 +00:00
Get Classic UI 1.11.2 - #5940 |
Updated by tobiasvdk on 2014-05-09 11:52:17 +00:00 I updated to
|
Updated by mfriedrich on 2014-05-09 11:53:41 +00:00
set use_logging=1 in cgi.cfg and set the path to the cgi log file to an apache writable path. then post the output when triggering the error on the browser. |
Updated by tobiasvdk on 2014-05-09 12:20:31 +00:00 Thank you for your fast feedback! Output from
In line 89 the following service definition starts:
|
Updated by mfriedrich on 2014-05-09 12:33:25 +00:00 Ok. And now I want to see that config object in Icinga 2 for the involved host and service. Somehow the 'check_command' is not dumped. Btw - any reason why to use the autorelease packages, and not snapshot as it's still in pre beta stage? That way you could test fixes more fast. |
Updated by tobiasvdk on 2014-05-09 12:46:56 +00:00 service config: apply Service "disk-var-partition" to Host {
import "generic-service"
check_command = "generic-disk-nrpe-check"
vars.disk = "/var"
assign where host.vars.has_var_partition
} check command config: template CheckCommand "generic-disk-nrpe-check" {
import "plugin-check-command"
command = PluginDir + "/check_nrpe"
arguments = {
"-u"
"-H" = "$address$"
"-t" = 20
"-c" = "check_disk"
"-a" = "$warning_threshold$ $critical_threshold$ $disk$"
}
vars.disk = "/"
vars.warning_threshold = "20%"
vars.critical_threshold = "10%"
} dnsmichi wrote:
No ... I will change apt config to use |
Updated by tobiasvdk on 2014-05-09 12:56:51 +00:00 Some background to my setup. I configured a clustered setup with two endpoints: one master and one slave (which is doing/should do the checks). |
Updated by tobiasvdk on 2014-05-09 13:19:54 +00:00 Ohh, I upgraded to
|
Updated by mfriedrich on 2014-05-09 14:16:00 +00:00 True. The cluster part is undergoing major changes in git next currently. Remove that configuration while testing this issue. |
Updated by tobiasvdk on 2014-05-09 14:46:24 +00:00 Is anything wrong with the service and check command configuration I did? |
Updated by mfriedrich on 2014-05-09 16:30:21 +00:00
|
Updated by gbeutner on 2014-05-09 17:35:52 +00:00 Hm, this seems to be a bug in the config validator. Your check command is a template: "template CheckCommand". Try changing that to "object CheckCommand" and see if that fixes the problem. |
Updated by gbeutner on 2014-05-09 17:45:03 +00:00
Applied in changeset 0c31bae. |
Updated by tobiasvdk on 2014-05-12 07:52:54 +00:00 Changing/correcting the config works. Thank you for the hint! |
Updated by mfriedrich on 2014-05-12 08:08:42 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/6148
Created by tobiasvdk on 2014-05-08 11:20:45 +00:00
Assignee: (none)
Status: Resolved (closed on 2014-05-09 17:45:03 +00:00)
Target Version: 0.0.11
Last Update: 2014-05-12 08:08:42 +00:00 (in Redmine)
Using icinga2-classicui on debian wheezy shows the following error message in the web ui:
Installed packages:
cgi.cfg
Changesets
2014-05-09 17:40:56 +00:00 by gbeutner 0c31bae
Relations:
The text was updated successfully, but these errors were encountered: