Nut upsuser - Nov 2025 - Debian 13 (NUT 2.8.1) fixes upssched bug, but floods systemctl log

I installed Debian 13.1 and was provided with NUT 2.8.1.  The good news is that 
this fixes the upssched habit of running a tight loop generating full cpu 
load.?[1]

My ups.conf includes

 [heartbeat]
        driver = dummy-ups
        port = heartbeat.conf
        mode = dummy-loop
        desc = "Heart beat validation of NUT" 

and my heartbeat.conf specification is 

 # heartbeat.conf   10 minute heartbeat. Time unit is the second
 ups.status: OL 
 TIMER 300
 ups.status: OB
 TIMER 300

The heart-beat now runs correctly, but the command 

 root at titan /etc/nut systemctl status nut-monitor 
 ? nut-monitor.service - Network UPS Tools - power device monitor and shutdown 
   controller
     Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled; 
             preset: enabled)

(lines skipped)

     Active: active (running) since Thu 2025-11-27 16:27:32 CET; 1 day 16h ago
             ??87562 /lib/nut/upsmon -F
             ??87566 /usr/sbin/upssched "UPS heartbeat at localhost: On
battery
                                         +++ Onduleur sur batterie"

 Nov 29 07:40:57 titan nut-monitor[98134]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:45:57 titan nut-monitor[98161]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:51:02 titan nut-monitor[98181]: Network UPS Tools upsmon 2.8.1
 Nov 29 07:56:02 titan nut-monitor[98190]: Network UPS Tools upsmon 2.8.1
 Nov 29 08:01:02 titan nut-monitor[98229]: Network UPS Tools upsmon 2.8.1
 ...

fills the systemctl log with reminders every 300 seconds that this is indeed NUT
2.8.1 .  It's good to have at least 2.8.1 in Debian, but is there some way
of
skipping the 300 second reminders??

Roger

[1]?https://www.mail-archive.com/nut-upsuser at
alioth-lists.debian.net/msg02422.html

Cheers,

  I think the message comes from upssched starting (as your NOTIFYCMD)
every 10 minutes to report the notification. So in a way this serves as
confirmation that this call-out does happen.

  There is a toggle for this, but starting from NUT v2.8.3 - per its part
in NEWS.adoc or
https://networkupstools.org/docs/release-notes.chunked/NUT_Release_Notes.html#_release_notes_for_nut_2_8_3_what_8217_s_new_since_2_8_2
:
> - A new `NUT_QUIET_INIT_BANNER` envvar (presence or "true" value)
can now
>   prevent the tool name and NUT version banner from being unilaterally
>   printed out when NUT programs start. [issues #1789 vs. #316; #2573]
  On a side note, if you run `upsmon` with debug, there may be confusing
(border-line misleading) messages about stopping the daemon and tearing
down some resources. I tracked those down to the forked processes for
notifications, which indeed are also upsmon's as far as the system was
concerned, and to upssched forking off a timer daemon from the CLI program
which it initially launches. Current versions deal with identifying those
children and grandchildren better, both for resource management and for
logging (a tag with process role is added near debug level number in
reports).

Jim Klimov


On Sat, Nov 29, 2025 at 9:19?AM Roger Price <roger at rogerprice.org>
wrote:
> I installed Debian 13.1 and was provided with NUT 2.8.1.  The good news is
> that
> this fixes the upssched habit of running a tight loop generating full cpu
> load. [1]
>
> My ups.conf includes
>
>  [heartbeat]
>         driver = dummy-ups
>         port = heartbeat.conf
>         mode = dummy-loop
>         desc = "Heart beat validation of NUT"
>
> and my heartbeat.conf specification is
>
>  # heartbeat.conf   10 minute heartbeat. Time unit is the second
>  ups.status: OL
>  TIMER 300
>  ups.status: OB
>  TIMER 300
>
> The heart-beat now runs correctly, but the command
>
>  root at titan /etc/nut systemctl status nut-monitor
>  ? nut-monitor.service - Network UPS Tools - power device monitor and
> shutdown
>    controller
>      Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled;
>              preset: enabled)
>
> (lines skipped)
>
>      Active: active (running) since Thu 2025-11-27 16:27:32 CET; 1 day 16h
> ago
>              ??87562 /lib/nut/upsmon -F
>              ??87566 /usr/sbin/upssched "UPS heartbeat at localhost:
On
> battery
>                                          +++ Onduleur sur batterie"
>
>  Nov 29 07:40:57 titan nut-monitor[98134]: Network UPS Tools upsmon 2.8.1
>  Nov 29 07:45:57 titan nut-monitor[98161]: Network UPS Tools upsmon 2.8.1
>  Nov 29 07:51:02 titan nut-monitor[98181]: Network UPS Tools upsmon 2.8.1
>  Nov 29 07:56:02 titan nut-monitor[98190]: Network UPS Tools upsmon 2.8.1
>  Nov 29 08:01:02 titan nut-monitor[98229]: Network UPS Tools upsmon 2.8.1
>  ...
>
> fills the systemctl log with reminders every 300 seconds that this is
> indeed NUT
> 2.8.1 .  It's good to have at least 2.8.1 in Debian, but is there some
way
> of
> skipping the 300 second reminders ?
>
> Roger
>
> [1]
> https://www.mail-archive.com/nut-upsuser at
alioth-lists.debian.net/msg02422.html
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251129/b891874d/attachment.htm>

Roger Price <roger at rogerprice.org> writes:
> fills the systemctl log with reminders every 300 seconds that this is
indeed NUT
> 2.8.1 .  It's good to have at least 2.8.1 in Debian, but is there some
way of
> skipping the 300 second reminders??
Debian not having the latest release is a Debian bug that should be
addressed to Debian :-)

I suggest installing the latest.  Surely there's some reasonable away to
do that by taking the control files and moving them forward and
building, or taking a package from unstable, or ?