Icinga critical/Socket: accept() failed with error code9, "Bad File Descriptor"

[samo.goljat (Samo)]

Problems with writing loges on Icinga, any solutions?

• Version used (icinga2 --version) - r2.14.3-1

• Operating System and version - AlmaLinux - 8.10 (Curelean Leopard)

• Enabled features (icinga2 feature list) -
  Disabled features: command compatlog debuglog elasticsearch influxdb influxdb2 journald opentsdb perfdata syslog
  Enabled features: api checker gelf graphite icingadb ido-pgsql livestatus mainlog notification

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

• Config validation (icinga2 daemon -C) Ok

  Icinga Web 2 Version	2.11.3
  Git commit	f917436a894c1f4148a9c3d6a27f9c20f204e44f
  PHP Version	8.0.30
  Git commit date	2022-12-14

  Get Icinga Support

  Icinga Community

  Report a bug

  Icinga Documentation

  Copyright © 2013-2026 Icinga GmbH

[apenning (Alvar)]

Please actually describe what does not work for you. The thread title alone is not really helpful.

Note: both your Icinga 2 and your Icinga Web 2 versions are both quite old and contain known security vulnerabilities.

[samo.goljat (Samo)]

The problem is that icinga2.logs are empty

[root@icinga icinga2]# cat icinga2.log-20260815 (for example)
[2026-08-14 08:08:27 +0200] critical/Socket: accept() failed with error code 9, “Bad file descriptor”
[2026-08-14 08:08:27 +0200] critical/LivestatusListener: Cannot accept new connection.

[samo.goljat (Samo)]

We are also experiencing deployment problems since this post, tryed to revert all the changes, but it seems the problem is not in Director config but elsewhere?

So tried to reverse all the changes made and still fails to deploy?

[bberg]

Well have you clicked on one of the failed deployments? It shows you an output of icinga2 daemon -C, which is pretty helpful to show you the problem in most cases.

[samo.goljat (Samo)]

Hi Bberg, I tried everything in the end reboot and manual restart of Icinga-director service helped.

[samo.goljat (Samo)]