Negative timing on last execution time in UI

Icinga Web
1

There’s something “buggy” I only realized today. Icingaweb constantly seems to flap between negative (last state change?) times and “normal” times. This results in values showing up as -119m.

image
image609×119 7.7 KB

I’ve seen this across all kinds of services since this morning. Not sure since when exactly this shows up like this because it only seems to affect the “Check Statistics” in the Icingaweb UI, the timings in the overview seem to be correct.

  • Icinga Web 2 version: 2.14.0
  • Used modules and their versions (System - About): doc, icingadb, migrate
  • Web browser used: Firefox 153
  • Icinga 2 version used (icinga2 --version): 2.16.4-1
  • PHP version used (php --version): 8.4.24
  • Server operating system and version: Debian 12

The following GIF shows this flapping pretty cleary.

Peek 2026-08-04 14-33

I first expected a problem I’ve had in the past, when a monitoring server jumped into the future due to NTP issue ( Servertime in the future breaks check results processing · Issue #6797 · Icinga/icinga2 · GitHub ), but that isn’t the case. I verified the execution timestamps (from the state file) and none of them were in the future.

Or am I looking in the wrong spot and should focus on Icingadb instead?

Update: I just realized this “glitch” also shows up in the overview from time to time, but only for a couple of seconds!

image
image593×454 53 KB

2

I experienced the same bug when my browser’s time does not match the configured one in Icinga Web 2. This should be fixed via Reload on timezone/locale preference changes and after authentication by TheSyscall · Pull Request #5540 · Icinga/icingaweb2 · GitHub - at least applying this patch worked for me.

3

Interesting, thanks for the reply.

I had a look at this PR but can’t find the code to replace (e.g. oldlocale) in the current icingaweb library files.

What is also strange is that this happens only on one Icinga installation, out of multiple. I noticed that the package/library “icinga-php-legacy” has been removed recently during an upgrade. Could this cause this effect?

Update: You’re right. The relevant bug mentioned by the PR you posted shows the same description what I experienced. Negative Last Check Time · Issue #5535 · Icinga/icingaweb2 · GitHub

A refresh of the browser indeed “resolves” the issue, as described in the GitHub issue.

So let’s wait for 2.14.1.