Critical/config: Error: Include file 'itl' does not exist

Icinga 2
1

Icinga2 doesnt start and I see below messages in icinga2 startup logfile.

Location: in /etc/icinga2/icinga2.conf: 26:1-26:13
/etc/icinga2/icinga2.conf(24): * Common monitoring plugin command definitions are included separately.
/etc/icinga2/icinga2.conf(25): */
/etc/icinga2/icinga2.conf(26): include <itl>
^^^^^^^^^^^^^
/etc/icinga2/icinga2.conf(27): include <plugins>
/etc/icinga2/icinga2.conf(28): include <plugins-contrib>

Icinga2 just exists with above messages and no other error message for info.
Please help how to bring it back.

2

please uplaod your /etc/icinga2/icinga2.conf

3

(DEV) root@host:/ # 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 <itl>
    include <plugins>
    include <plugins-contrib>
    include <manubulon>

/**

  • 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 <windows-plugins>

/**

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

/**

  • 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”.
    */
    include_recursive “conf.d”
4

please edit the post and use the preformatted text </> button to wrap the config

type or paste code here
5

Thanks for reply. I did it. I am able see it in above thread.
</

(DEV) root@host:/ # 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 <itl>
    include <plugins>
    include <plugins-contrib>
    include <manubulon>

/**

  • 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 <windows-plugins>

/**

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

/**

  • 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.
    <em>/
    include “features-enabled/</em>.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”.
    */
    include_recursive “conf.d”
6

no you should put the config inside the preformatted text box. that config is barely readable because of the formatting skills of the forum.

7

More importantly: What is your distribution and how did you install Icinga2?

8

Hi Lorenz, Icinga2 was installed long time back and I am not aware of the process.

However I found the issue and able to fix it.

Found “/u01/share” folder permissions were changed and Icinga2 failed to read all files from there. That “share” directory all necessary Icinga2 web files.

I change ownership of that folder to Icinga2(with which the icinga2 service runs) and the problem got fixed.

service is up and running fine.

Thank you very much for your response and help

9

Hello there and welcome to the community forum!
We always love to see posts formatted according to the formatting guidelines which can help you make your posts more readable - I think this is what the others were trying to tell you with your config not being readable.
You can always go back and edit your responses for more clarity!

1 Like