Icinga-Web – Configuration Changes Not Updating

icingamonitoring

So I've just installed Icinga and Icinga-Web. And everything looked ok when first inspecting the UI's on http://[server]/icinga/ and http://[server]/icinga-web/…

I went on and added some new hosts, services, commands, etc. and reloaded the icinga service, without problems. Then I flushed the icinga-web cache and restarted the apache2 service, again no problems.

After reloading the configuration, all of the new hosts and services shows up just fine, in the old icinga UI, and the checks are running perfectly, well almost 😉 (see below).

Old Icinga UI Status

However, in the new icinga-web interface it's a completely different story. The icinga-web UI still shows the hosts from the initial configuration (a single 'localhost' host with 8 services). The UI also shows the 'default' instance as being 'down' in the header status, and that 'the data is X minutes old' (see below).

New Icinga-Web UI Status

I've tried retracing my steps, by re-reading the icinga-web installation guide, but I can't figure out what I've done wrong or how to correct it. I've also tried to fiddle with the access.xml and databases.xml configuration files.

What am I doing wrong and how do I fix it?

Best Answer

In my case, there were two changes that needed to be made.

1) /etc/default/icinga needs to be configured so that IDO2DB will run:

# start ido2db daemon (no/yes)
IDO2DB=yes

2) The IDO module needs to be defined in /etc/icinga/modules/

/etc/icinga/modules/idoutils.cfg:

define module {
    module_name    ido_mod
    path           /usr/lib/icinga/idomod.so
    module_type    neb
    args           config_file=/etc/icinga/idomod.cfg
    }

The previous config file will, of course, need to match how your system is configured. The above is being used on an Ubuntu 12.10 server.

Related Solutions

Problem with Icinga web installation – server side errors

I poked about with this and the problem seems to be within the Agavi components, specifically:

lib/agavi/src/filter/AgaviExecutionFilter.class.php

And within the writeCache() method:

@mkdir(AgaviConfig::get('core.cache_dir') . DIRECTORY_SEPARATOR . 
        self::CACHE_SUBDIR .
        DIRECTORY_SEPARATOR . implode(DIRECTORY_SEPARATOR , 
        array_slice($groups, 0, -1)), 0777, true);

I dropped a logger line into this code and saw that mkdir is trying to recursively create a directory such as:

/usr/local/icinga-www/app/cache/content/amF2YXNjcmlwdF9jb250ZW50/QXBwS2l0X1dpZGdldHMvU3F1aXNoTG9hZGVy

I deleted this, restarted apache but the problem persisted.

At this point the server was running PHP 5.2.17.

I upgraded PHP to 5.3.5 and this issue magically resolved itself.

Out of interest I knocked PHP back to 5.2.17 to see if there were any differences between the mkdir() function behavior in that version compared to the one in 5.3.5. A test script showed that all that PHP did was warn that the folder existed in both versions, there was no hard error thrown.

Also, and bizarrely, icinga-web started working with PHP 5.2.17....and I have no idea why. I checked both version's php.ini files thinking that the error_reporting settings may have changed, but they were the same (except that PHP 5.3.5 is set to E_ALL & ~E_NOTICE | E_DEPRECATED whereas 5.2.17 is set to E_ALL & ~E_NOTICE).

Hope this is of use to anyone else encountering the same issue.

Icinga Web no hosts/services showing up

Please check the whether the web user has access to view the hosts/services that you've added. This can be set using the Icinga roles. For icinga2 have a look at /etc/icingaweb2/roles.ini. The link has more information.

For icinga classic web locate cgi.cgi inside icinga web root and add the new user to authorized_for_* directives wherever you want to allow the user access.

Best Answer

Related Solutions

Problem with Icinga web installation – server side errors

Icinga Web no hosts/services showing up

Related Topic