Hi there, we just upgraded a few of our Icinga boxes from 1.8.4 to 1.11 and
noticed that Icinga fails the config check on startup due to a couple of
empty hostgroups. We have a handful of hostgroups that look like the one
below:
define hostgroup{
hostgroup_name some-group
alias Some G
Cool, will do. Thanks!
On Tue, Apr 8, 2014 at 9:08 AM, Michael Friedrich <
michael.friedr...@gmail.com> wrote:
> On 07.04.2014 21:08, Jason Erdmann wrote:
>
>> So in the icinga-core source, I noticed that the handling of populating
>> hostgroups is a bit different from 1.8.4 to 1.11, eg. the 'r
On 07.04.2014 21:08, Jason Erdmann wrote:
So in the icinga-core source, I noticed that the handling of populating
hostgroups is a bit different from 1.8.4 to 1.11, eg. the 'result != ok'
that short-circuits the allow_empty_hostgroup_assignment option? I'm
sure there's a good reason for this, but
So in the icinga-core source, I noticed that the handling of populating
hostgroups is a bit different from 1.8.4 to 1.11, eg. the 'result != ok'
that short-circuits the allow_empty_hostgroup_assignment option? I'm sure
there's a good reason for this, but any insight as to why? Anything we can
do
Hi there, we just upgraded a few of our Icinga boxes from 1.8.4 to 1.11 and
noticed that Icinga fails the config check on startup due to a couple of
empty hostgroups. We have a handful of hostgroups that look like the one
below:
define hostgroup{
hostgroup_name some-group
alias Some G
