After OS patching and reboot of a physical #Linux server used for Icinga2 #monitoring, the Icinga 2 services did not work as expected. Well, actually they did - sort of.

Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two #Icinga2 master nodes (running as a cluster).

https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue

#icinga2 #icinga "You say “Eee-Chingaa”, I say “Aye-Singa” – but how do the Zulus say it? We consulted a couple Zulu speakers and even received a pronunciation guide from Megan Wells to help us all out. As she told us:
“The I in Icinga is actually a Romanized representation of the Zulu click. The easiest way to approximate the click is by putting your tongue behind your top teeth and pulling it down, kind of like a tsk-tsk noise. The vowels on either side of the click are “eee” noises, like in “see”. There is no hard “g” sound in Icinga – the “ng” is pronounced like the end of “sing”. Finally, the “a” is pronounced like the “a” in “father”."
https://icinga.com/blog/archive/a-lesson-in-zulu-icinga/

So, mein #icinga2-graphite-Problem war ein Bug. Den jemand 2023 gefixt hat, der es aber nicht in die Packages bei Ubuntu geschafft hat. *hmpf*

Wieder mal eine #icinga2-Frage: Wie generiert #Icingaweb2 die Aufrufe nach #Graphite? Wenn ich den GET von Icinga richtig tracke, bekommt es eine Grafik zurück. Aber darstellen tut es sie nicht... und ich bin ratlos wie ich das debuggen kann...

Mal wieder eine fachliche Frage: Ich habe für #icinga2 #graphite am Laufen. Die #whisper-Datenbank wird (auf dem Dateisystem) gefüllt, mit whisper-dump sehe ich Werte; einmal für carbon- und einmal für icinga-Daten. Graphite-Web findet die Carbon-Daten, aber der Icinga-Ordner ist leer. Was läuft da schief bzw. wo kann ich debuggen warum whisper die Daten zwar schreibt, aber Graphite sie nicht lesen/auswerten kann?

#monitoring-Fails: Um Reports aus #icinga2 zu erstellen, sollen #pdfs generiert werden - gut! Aber warum muss dafür ein Internetbrowser installiert werden? Warum kein #ghostscript? Das ist genau dafür gedacht...

#icinga2 released the fix for the latest #security #vulnerability

I'm using this on #FreeBSD with > 30 satellite nodes:

* pkg update -f --> fix not available yet
* but, port already updated, thanks to the maintainer!
* Had to compile package & install manually

Is there a team that focuses on updating packages with critical security vulnerabilities? No complaint , I want to understand how things are handled.

I also wonder if there's an icinga-on-freebsd user group.

https://icinga.com/blog/2024/11/12/critical-icinga-2-security-releases-2-14-3/

#icinga2 in Debian has command definitions not matching the Debian available check command binaries.

Icinga2 says - use "nagios plugins" which are not available in Debian. monitoring-plugins says modify the existing definitions.

I am puzzled that these 2 Maintainers have no interest in integrations between Icinga2 and corresponding check plugins.

I though that was the whole reason of packaging to get a "Distribution" work as a whole ...

Bug 1085355 & 1085411