After upgrading our icinga2 to the version : 2.12.4 we are facing an issue with the deployment of new configurations…
About our monitoring : we have 2 pollers in a zone (master - master) with 1 deployment endpoint. We have 1 web server that host icingaweb2 and icingadirector and we have a database server that host all of our databases for icinga, director… All these servers are on Gentoo Linux, icingaweb2 is on version 2.11.3 and icingadirector in 1.8.0.
Since the update the behaviour is like this :
Normal run : both icinga2 services are fine, 3 process per server are working properly and everything is fine.
When we push our first modifications via icingadirector, new processes are created on both icinga2 servers and replace the old process as it should be according to the documentation.
But after that first deployment our issue kick in: if we push a second configuration via icingadirector, some process are created BUT then are stucked… the only solution is to “kill -9” on thoses “stuck” processes to get the deployment back…
Can anyone help debug this issue please ?