ck 👨💻<p>After OS patching and reboot of a physical <a href="https://noc.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> server used for Icinga2 <a href="https://noc.social/tags/monitoring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>monitoring</span></a>, the Icinga 2 services did not work as expected. Well, actually they did - sort of. </p><p>Deeper analysis showed a time sync issue on the rebooted physical server, causing a hiccup in the two <a href="https://noc.social/tags/Icinga2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Icinga2</span></a> master nodes (running as a cluster). </p><p><a href="https://www.claudiokuenzler.com/blog/1476/monitoring-backend-icinga2-not-running-time-sync-issue" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">claudiokuenzler.com/blog/1476/</span><span class="invisible">monitoring-backend-icinga2-not-running-time-sync-issue</span></a></p>