Icinga2 agent on Ubutnu Semaphore Usage

I have Icinga2 2.13.3-1 running on Ubuntu 18. On two servers it is fine but I’ve just set it up on a third and when running it keeps using Semaphores and not releasing them. I have to stop Icinga2 and manually remove them. After 1 hour of running it’s using 4000. By comparison the other ubuntu hosts, running the same version, have been online for months and they are using 9…

Any ideas??

# icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: r2.13.3-1)

Copyright (c) 2012-2023 Icinga GmbH (https://icinga.com/)
License GPLv2+: GNU GPL version 2 or later <https://gnu.org/licenses/gpl2.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

System information:
  Platform: Ubuntu
  Platform version: 18.04.6 LTS (Bionic Beaver)
  Kernel: Linux
  Kernel version: 4.15.0-206-generic
  Architecture: x86_64

Build information:
  Compiler: GNU 8.4.0
  Build host: runner-hh8q3bz2-project-298-concurrent-0
  OpenSSL version: OpenSSL 1.1.1  11 Sep 2018

Application information:

General paths:
  Config directory: /etc/icinga2
  Data directory: /var/lib/icinga2
  Log directory: /var/log/icinga2
  Cache directory: /var/cache/icinga2
  Spool directory: /var/spool/icinga2
  Run directory: /run/icinga2

Old paths (deprecated):
  Installation root: /usr
  Sysconf directory: /etc
  Run directory (base): /run
  Local state directory: /var

Internal paths:
  Package data directory: /usr/share/icinga2
  State path: /var/lib/icinga2/icinga2.state
  Modified attributes path: /var/lib/icinga2/modified-attributes.conf
  Objects path: /var/cache/icinga2/icinga2.debug
  Vars path: /var/cache/icinga2/icinga2.vars
  PID path: /run/icinga2/icinga2.pid

are you trying to create a “three master”-setup?
that’s not supported

Also not supported for any other zone besides the master zone as well.

1 Like

Only one master - the systems I was talking about are all running agents (the master is a seperate server).

Two of the agents work fine but the third keeps consuming and not releasing semaphores. OS and Icinga code and even configuration are the same on all three.

Every Agent is in it’s own zone?

It is - but only because that was the way I got it working a few years ago - I wasn’t sure if it was the right way or not…

It is the right way as you can have only 2 nodes per zone and all endpoints need to belong to a zone:

Master Zone: master1 [& master2]

[Satellite X Zone: satellite_X_1 [& satellite_X_2]]

Agent Y Zone: agent_Y
[ ] means optional

So in the end I also only have one zone per agent and I call both the endpoint and the zone by the FQDN of the host the agent is running on.