Turn off logging for Icinga 5665 api, we use nrpe (5666) port

Icinga 2
1

Hi, i checked for similar topics and didn’t find anything useful. As it seems Icinga is logging, that is actively trying to conneto to 5665 or API port on end point hosts which run NRPE and use that port instead for communication with Icinga. Question is can i turn off excessive logging so it doesn’t write nor in icinga2.log nor in journalctl?

Give as much information as you can, e.g.

  • Platform version: 8.10 (Cerulean Leopard)

  • Platform: AlmaLinux Kernel version: 4.18.0-553.54.1.el8_10.x86_64

  • Enabled features (icinga2 feature list) Enabled features: api checker graphite icingadb ido-pgsql livestatus mainlog notification

  • Icinga Web 2 version and modules (System - About):

    businessprocess 2.4.0 Configure
    director 1.11.6 Configure
    doc 2.11.3 Configure
    graphite 1.2.5 Configure
    idoreports 0.10.0 Configure
    incubator 0.22.0 Configure
    migrate 2.11.3 Configure
    monitoring 2.11.3 Configure
    nagvis 1.2.1 Configure
    pdfexport 0.10.2 Configure
    reactbundle 0.7.0 Configure
    reporting 1.0.3 Configure
    setup 2.11.3 Configure
    translation 2.11.3 Configure
    vspheredb 1.7.1 Configure
    x509 1.1.2 Configure

  • Config validation (icinga2 daemon -C):
    [2026-04-01 09:05:17 +0200] information/cli: Icinga application loader (version: r2.14.3-1)
    [2026-04-01 09:05:17 +0200] information/cli: Loading configuration file(s).
    [2026-04-01 09:05:28 +0200] warning/config: Ignoring directory ‘/var/lib/icinga2/api/zones/icinga.izum.pri’ for unknown zone ‘icinga.izum.pri’.
    [2026-04-01 09:05:28 +0200] information/ConfigItem: Committing config item(s).
    [2026-04-01 09:05:28 +0200] information/ApiListener: My API identity: icinga.izum.pri
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 NotificationComponent.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 LivestatusListener.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 GraphiteWriter.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 IdoPgsqlConnection.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 142 Downtimes.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 9192 Dependencies.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 CheckerComponent.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 39 Users.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 13 UserGroups.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 3 TimePeriods.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 20 ServiceGroups.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 9192 Services.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 78 ScheduledDowntimes.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 29 Zones.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 7 NotificationCommands.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 46054 Notifications.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 FileLogger.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 IcingaApplication.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 585 Hosts.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 40 HostGroups.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 2 EventCommands.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 27 Endpoints.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 53 Comments.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 2 ApiUsers.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 ApiListener.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 374 CheckCommands.
    [2026-04-01 09:05:31 +0200] information/ConfigItem: Instantiated 1 IcingaDB.
    [2026-04-01 09:05:31 +0200] information/ScriptGlobal: Dumping variables to file ‘/var/cache/icinga2/icinga2.vars’
    [2026-04-01 09:05:31 +0200] information/cli: Finished validating the configuration file(s).

2

you most likely have the agent settings on for the hosts.

Since you are using nrpe for check execution, there is no need for an agent and no need for actively connecting to it.

so set that all to No in your host or host-template and you should be fine.
Don’t do that for satellite or real agent hosts. (for instances that have icinga2 installed and configured)

This is an example of a icinga2 host that is connected to my master using icinga2.

Whether the parent (master) node should actively try to connect to this agent

The first yes creates the config for an command endpoint.
The second yes tells the master to connect to the agent.
The third yes tells the agent to accept config (but this currently only considered in the powershell install command)

Bildschirmfoto 2026-04-01 um 10.00.53
Bildschirmfoto 2026-04-01 um 10.00.531296×544 28.7 KB

3

That seems to solve the problem, we found that Nrpe/Nsclient (for Windows) suits us better in terms of monitoring.

4

Do you perhaps also know hot to solve problem in logs:
[2026-04-01 12:57:33 +0200] critical/Socket: accept() failed with error code 9, “Bad file descriptor”
[2026-04-01 12:57:33 +0200] critical/LivestatusListener: Cannot accept new connection.

5

do you use livestatus?, is is deprecated.
here is the doc for that Features - Icinga 2

If it is unused in your infrastructure you can disable it like this:

icinga2 feature list
icinga2 feature disable livestatus
systemctl restart icinga2

6

…and will be removed in 2.18.0: Remove deprecated features · Issue #10731 · Icinga/icinga2 · GitHub
So i think now is a good time to start migration to anything else, if its still used.
People use livestatus usually for Thruk, but icingaweb might be fine as well for those.