Icinga Web shows no information

Hi.

I have a running small Icinga2/IncingaWeb2 setup.

Some days ago I upgraded Icinga via APT. Since then it is still accessible but shows no hosts or services.

I have checked IDO and information is still stored there by Icinga2.
I have checked API permissions and I’m able to access API with the credentials given to IcingaWeb.
I have removed and reinstalled IcingaWeb2 but still the same.
I have enabled setup and run it again but still the same.

Can you point me to other elements to verify?

Thanks in advance
Javier Vilarroig

Hi & welcome,

From which version to which version did you upgrade? Could you share your icinga2.conf? Where are your host and services objects defined?

Hi.

Thanks for you fast answer :slight_smile:

Upgrade from 2.6.2 to 2.8.2

Hosts and services are defined in /etc/icinga2/zones.d/master/ folder, hosts.conf and services.conf files.

icinga2.conf
root@services:~# cat /etc/icinga2/icinga2.conf
/**

  • Icinga 2 configuration file
    • this is where you define settings for the Icinga application including
  • which hosts/services to check.
  • For an overview of all available configuration options please refer
  • to the documentation that is distributed as part of Icinga 2.
    */

/**

  • The constants.conf defines global constants.
    */
    include “constants.conf”

/**

  • The zones.conf defines zones for a cluster setup.
  • Not required for single instance setups.
    */
    include “zones.conf”

/**

  • The Icinga Template Library (ITL) provides a number of useful templates
  • and command definitions.
  • Common monitoring plugin command definitions are included separately.
    */
    include
    include
    include
    include

/**

  • This includes the Icinga 2 Windows plugins. These command definitions
  • are required on a master node when a client is used as command endpoint.
    */
    include

/**

  • This includes the NSClient++ check commands. These command definitions
  • are required on a master node when a client is used as command endpoint.
    */
    include

/**

  • The features-available directory contains a number of configuration
  • files for features which can be enabled and disabled using the
  • icinga2 feature enable / icinga2 feature disable CLI commands.
  • These commands work by creating and removing symbolic links in
  • the features-enabled directory.
    /
    include "features-enabled/
    .conf"

/**

  • Although in theory you could define all your objects in this file
  • the preferred way is to create separate directories and files in the conf.d
  • directory. Each of these files must have the file extension “.conf”.
    */
    // Disabled by the node setup CLI command on 2019-07-29 15:50:56 +0000
    // Disabled by the node setup CLI command on 2019-07-29 16:07:30 +0000
    // Disabled by the node setup CLI command on 2019-07-30 12:58:31 +0000
    // include_recursive “conf.d”
    // Added by the node setup CLI command on 2019-07-29 15:50:56 +0000
    // Added by the node setup CLI command on 2019-07-30 12:58:31 +0000
    include “conf.d/api-users.conf”

Thanks!

Ok, that looks good. The version you mentioned belong most properly to icingaweb2 but not icinga2 (core).

How does your zones.conf and constants.conf look like?

BTW: For better readability please format your posts as described here.

Hi.

Yes, version numbers are icingaweb2. icinga2 version is 2.12.0

zones.conf

object Zone "global-templates" {
  global = true
}

object Zone "director-global" {
  global = true
}

constants.conf

const PluginDir = "/usr/lib/nagios/plugins"

const ManubulonPluginDir = "/usr/lib/nagios/plugins"

const PluginContribDir = "/usr/lib/nagios/plugins"

const NodeName = "server.example.org"

const ZoneName = "server.example.org"

const TicketSalt = "SALT_REMOVED"

Thanks!

Your zones.conf is incomplete. Did you run icinga2 node wizard?

Sorry for the radio silence. I have been sick.

My mistake. I had an issue copying. This is my zones.conf:

object Zone "global-templates" {
  global = true
}


object Zone "director-global" {
  global = true
}

object Endpoint "services.unidata.msf.org" {
	host = "services.unidata.msf.org"
}

object Endpoint "pr3.unidata.msf.org" {
	host = "pr3.unidata.msf.org"
}

object Endpoint "pr4.unidata.msf.org" {
	host = "pr4.unidata.msf.org"
}

object Zone "master" {
	endpoints = [ "services.unidata.msf.org" ]
}

object Zone "pr3.unidata.msf.org" {
	parent = "master"
	endpoints = [ "pr3.unidata.msf.org" ]
}

object Zone "pr4.unidata.msf.org" {
	parent = "master"
	endpoints = [ "pr4.unidata.msf.org" ]
}

Don’t worry. It sounds good that you are recovered.

but

Does that mean you have conf files and director in use?
From which icinga2 core version did you upgrade?
Do you have satellites in use?

Hi Roland.

No, we do not use director.

The upgrade was from 2.10.5 to to 2.12.5.

Yes, the setup includes two satellites (pr3 and pr4) in high availability mode.

Everything was running well until we upgraded the icinga packages.

Thanks!

There has been a change with conf files since V2.11 and it’s causing malfunction if your conf files does not meet the new file structure. Details could be found here.

Ok. I will read the document.

Thanks a lot for your help!

FYI, after reviewing the zones configuration the issue is solved. :slight_smile:

Thanks a lot for your help.