After upgrading an Icinga2 satellite server, which is only used to execute checks in a separate monitoring zone, from Debian Buster (10) to Bullseye (11), the checks were not executed anymore.
Even though the Icinga 2 master node confirmed that the satellite can be spoken to (the cluster check command can be used for this purpose), no new log entries appeared on the satellite server. Even a forced "check now" on a service check would not return any new result.
This problem is difficult to spot, because you don't see an actual problem in the Icingaweb2 interface!
The reason for this is the same problem already written about twice:
The cause? The package naming. Although reported a looong time ago, Icinga 2 still uses the Ubuntu and Debian release names (e.g. bionic or buster) as package appendix. The APT package manager uses alphabetic ordering in this case and thinks that buster packages are newer than bullseye packages, because the S comes later than the L in the alphabet.
After the Debian upgrade, the Icinga packages are still tagged with the "buster" appendix:
root@satellite:~# dpkg -l|grep icinga
ii icinga2-bin 2.13.4-1.buster amd64 host and network monitoring system - daemon
ii icinga2-common 2.13.4-1.buster all host and network monitoring system - common files
As this is a satellite server and not holding any actual Icinga 2 (monitoring) configurations, the fix is very easy. Just tell apt to enforce an installation with the bullseye appendix:
root@satellite:~# apt-get install icinga2-bin=2.13.4-1.bullseye icinga2-common=2.13.4-1.bullseye
The following additional packages will be installed:
libboost-context1.74.0 libboost-coroutine1.74.0 libboost-filesystem1.74.0 libboost-program-options1.74.0 libboost-regex1.74.0
libboost-thread1.74.0
The following NEW packages will be installed:
libboost-context1.74.0 libboost-coroutine1.74.0 libboost-filesystem1.74.0 libboost-program-options1.74.0 libboost-regex1.74.0
libboost-thread1.74.0
The following packages will be DOWNGRADED:
icinga2-bin icinga2-common
0 upgraded, 6 newly installed, 2 downgraded, 0 to remove and 1 not upgraded.
Need to get 5,994 kB of archives.
After this operation, 16.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Note: A master server might require additional steps, check out the mentioned articles above.
After another Icinga 2 restart on the Satellite, the checks started working again.
root@satellite:~# systemctl restart icinga2
Falko from wrote on Aug 10th, 2022:
Did mostly work, but had to use:
`apt-get install icinga2-bin=2.13.4-1.bullseye icinga2-common=2.13.4-1.bullseye icinga2=2.13.4-1.bullseye`
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb Icingaweb2 Influx Internet Java KVM Kibana Kodi Kubernetes LVM LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder