Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
This was going to be a post about trying to figure out what was wrong with my config, but now I figured that out. Now this will be about misleading error messages . I had a working set of config files and I am adding a new one that adds new hosts and services but uses servicegroups defined in existing config files. A config check with the new file kept erroring with
Error: Could not expand member services specified in servicegroup (config file /blah/blah) ....
The line referenced in the error was a servicegroup definition in an existing file that has always worked up until this point. I was starting to think that I hit some servicegroup membership ceiling or something. What I found was that my new config had a couple of services with a blank service_description and blank check_command as a result of an error in my script to generate the config file. So, the actual error was totally my fault but the Nagios error was pointing me in the complete wrong direction. Shouldn't it have instead errored on a service with a blank service_description?
grimm26 wrote: Shouldn't it have instead errored on a service with a blank service_description?
Probably, but it wouldn't know what to call the service in the error without a service description to reference. It could be more verbose as to the actual issue, though it may be wrapped up under a more broad config error. If you wish, submit a feature request/bug report to: http://tracker.nagios.org
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
grimm26 wrote: Shouldn't it have instead errored on a service with a blank service_description?
Probably, but it wouldn't know what to call the service in the error without a service description to reference. It could be more verbose as to the actual issue, though it may be wrapped up under a more broad config error. If you wish, submit a feature request/bug report to: http://tracker.nagios.org
I'll do that. Nagios may not know what to call it but it could say "service definition error in file foo on line 26."
True enough. Post a link to the bug here after it is submitted. I will wait to lock the thread until then.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.