Package: nagios4
Version: 4.4.6-4.1
Severity: important
Dear Maintainer,
The problem occurred on Armbian running on an ODROID-MC1 Solo.
I upgraded my system from bookworm to trixie, and noticed Nagios
consuming most or all available CPU resources.
I verified that the system has the correct time. Nagios itself also
shows the correct time in other contexts. Next scheduled check of each
service is near the present time.
I purged nagios4{,-cgi,-common,-conf} and my nagios configuration, then
installed nagios4 again, installed only my password database so I could
log in to the web interface, and observed the default localhost entry.
It had the same condition, with last check reported as 1970, and next
check scheduled in the present. So I don't think this is a problem with
my particular configuration.
I performed a clean install of trixie and ran my deployment scripts to
redeploy nagios with my old configuration. The issue persisted. So I
don't think this is a result of the OS upgrade.
I configured bookworm package sources and installed the version of
nagios4 from bookworm (which brought along nagios4-{cgi,common,core}
from bookworm) and adjusted apt pinning to keep it there for now. The
system is otherwise on trixie. nagios4 is at version 4.4.6-4, and the
problem is not happening. Last check times are shown in the present
year, and Nagios is not thrashing the CPUs. The problem seems specific
to nagios4 version 4.4.6-4.1.
While the newer package was installed and the problem was ongoing, I set
debug_level=16 ("Host/service checks") and debug_verbosity=2 ("Very
detailed") in nagios.cfg. /var/log/nagios4/nagios.debug received a
rapid stream of messages. I am pasting an excerpt below. I notice that
for each service check, there is a line saying, "Rescheduling next check
of service", which specifies a time in 1970, followed by a line saying,
"Scheduling a non-forced, active check of service", which specifies a
time near the present.
Other than that, I notice both the incorrect timestamps in the log and
the "last checked" entries in the web interface seem to be specifically
in late February and early March of 1970, not right on the epoch.
I will be happy to engage the broken version and gather more logs, if
that helps. Just let me know what you want to see.
[0.1766210301] [000.803042] [pid=0] Parsing check output...
Short Output: Debian update: Critical! Last update returned 1 at 13 hours, 17
minutes, and 38 seconds ago.
Long Output: NULL
Perf Data: NULL
[0.1766210301] [000.803067] [pid=0] Service is in a non-OK state!
[0.1766210301] [000.803087] [pid=0] Host is currently UP, so we'll recheck its
state to make sure...
[0.1766210301] [000.803106] [pid=0] Service not ok, host is up, using cached
host data
[0.1766210301] [000.803128] [pid=0] Service was NOT OK at last check (CRITICAL).
[0.1766210301] [000.803148] [pid=0] Service is still in a non-OK state
(CRITICAL)!
[0.1766210301] [000.803167] [pid=0] Service state type is hard, sending a
notification
[0.1766210301] [000.803187] [pid=0] Checking service 'Debian update' on host
'synapse' for flapping...
[0.1766210301] [000.803208] [pid=0] LFT=5.00, HFT=20.00, CPC=0.00, PSC=0.00%
[0.1766210301] [000.803244] [pid=0] Service is not flapping (0.00% state
change).
[0.1766210301] [000.803268] [pid=0] Checking host 'synapse' for flapping...
[0.1766210301] [000.803291] [pid=0] LFT=5.00, HFT=20.00, CPC=0.00, PSC=0.00%
[0.1766210301] [000.803321] [pid=0] Host is not flapping (0.00% state change).
[0.1766210301] [000.803412] [pid=0] Rescheduling next check of service at Sun
Mar 8 05:54:12 1970
[0.1766210301] [000.803522] [pid=0] Scheduling a non-forced, active check of
service 'Debian update' on host 'synapse' @ Sat Dec 20 00:58:21 2025
[0.1766210301] [000.803554] [pid=0] Scheduling new service check event.
[0.1766210301] [000.803662] [pid=0] STATE: 2, TYPE: HARD, CUR: 5, MAX: 5,
LAST_STATE: 2, LAST_HARD: 2, NOTIFY: 1, LOGGED: 0, HANDLED: 0
[0.1766210301] [000.803770] [pid=0] Attempting to run scheduled check of
service 'Debian update' on host 'synapse': check options=0, latency=0.000192
[0.1766210301] [000.803859] [pid=0] Checking service 'Debian update' on host
'synapse'...
[0.1766210301] [000.803903] [pid=0] Raw Command Input:
/usr/local/bin/check_debian_update $HOSTADDRESS$
[0.1766210301] [000.803926] [pid=0] Expanded Command Output:
/usr/local/bin/check_debian_update $HOSTADDRESS$
[0.1766210301] [000.860666] [pid=0] Processing check result for service
'HTTP+SSL' on host 'gateway'
[0.1766210301] [000.860732] [pid=0] ** Handling ACTIVE async check result for service 'HTTP+SSL' on host 'gateway' from 'Core Worker 17150'... current state 0 last_hard_state 0
[0.1766210301] [000.860751] [pid=0] * OPTIONS: 0, SCHEDULED: 1, RESCHEDULE: 1, EXITED OK: 1, RETURN CODE: 0, OUTPUT:
HTTP OK: HTTP/1.1 200 OK - 715 bytes in 0.106 second response time
|time=0.106101s;;;0.000000;10.000000 size=715B;;;0;
[0.1766210301] [000.860777] [pid=0] Parsing check output...
Short Output: HTTP OK: HTTP/1.1 200 OK - 715 bytes in 0.106 second response time
Long Output: NULL
Perf Data: time=0.106101s;;;0.000000;10.000000 size=715B;;;0;
[0.1766210301] [000.860794] [pid=0] Service is OK
[0.1766210301] [000.860810] [pid=0] Service was OK at last check.
[0.1766210301] [000.860825] [pid=0] Service is still OK.
[0.1766210301] [000.860842] [pid=0] Checking service 'HTTP+SSL' on host
'gateway' for flapping...
[0.1766210301] [000.860860] [pid=0] LFT=5.00, HFT=20.00, CPC=0.00, PSC=0.00%
[0.1766210301] [000.860946] [pid=0] Service is not flapping (0.00% state
change).
[0.1766210301] [000.860967] [pid=0] Checking host 'gateway' for flapping...
[0.1766210301] [000.860989] [pid=0] LFT=5.00, HFT=20.00, CPC=0.00, PSC=0.00%
[0.1766210301] [000.861011] [pid=0] Host is not flapping (0.00% state change).
[0.1766210301] [000.861077] [pid=0] Rescheduling next check of service at Mon
Mar 9 01:51:00 1970
[0.1766210301] [000.861170] [pid=0] Scheduling a non-forced, active check of
service 'HTTP+SSL' on host 'gateway' @ Sat Dec 20 00:58:21 2025
[0.1766210301] [000.861196] [pid=0] Scheduling new service check event.
[0.1766210301] [000.861221] [pid=0] STATE: 0, TYPE: HARD, CUR: 1, MAX: 5,
LAST_STATE: 0, LAST_HARD: 0, NOTIFY: 0, LOGGED: 0, HANDLED: 0
[0.1766210301] [000.861298] [pid=0] Attempting to run scheduled check of
service 'HTTP+SSL' on host 'gateway': check options=0, latency=0.000083
[0.1766210301] [000.861359] [pid=0] Checking service 'HTTP+SSL' on host
'gateway'...
[0.1766210301] [000.861385] [pid=0] Raw Command Input:
/usr/lib/nagios/plugins/check_http --ssl -H '$HOSTADDRESS$' -I '$HOSTADDRESS$'
'$ARG1$'
[0.1766210301] [000.861403] [pid=0] Expanded Command Output:
/usr/lib/nagios/plugins/check_http --ssl -H '$HOSTADDRESS$' -I '$HOSTADDRESS$'
'$ARG1$'
[0.1766210301] [000.876401] [pid=0] Processing check result for service 'Tor
system service' on host 'neuron-mail'
[0.1766210301] [000.876533] [pid=0] ** Handling ACTIVE async check result for service 'Tor system service' on host 'neuron-mail' from 'Core Worker 17147'... current state 0 last_hard_state 0
[0.1766210301] [000.876566] [pid=0] * OPTIONS: 0, SCHEDULED: 1, RESCHEDULE: 1, EXITED OK: 1, RETURN CODE: 0, OUTPUT:
"service 'tor' status" returned 0.
-- System Information:
Debian Release: 13.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'oldstable')
Architecture: armhf (armv7l)
Kernel: Linux 6.6.113-current-odroidxu4 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nagios4 depends on:
ii nagios4-cgi 4.4.6-4.1
ii nagios4-common 4.4.6-4.1
ii nagios4-core 4.4.6-4.1
nagios4 recommends no packages.
Versions of packages nagios4 suggests:
pn nagios-nrpe-plugin <none>
-- no debconf information
--
Aaron Bugher
