usbhid-ups high cpu usage

[pollocluck]

Hello! I couldn't find a discussion or forum anywhere, so I hope this is the right place to post this. I recently tried to edit my NUT configuration so it would run a bash script when the UPS (Back-UPS ES 600M1) reached ~60%. I used Gemini to give me a clear answer, but after a day of implementing the changes, my server's CPU usage was idling at 16-17% instead of 0-3% and i verified it was being caused by usbhid-ups. When I undid my previous changes the CPU usage went back to normal.

I edited the upsmon.conf, upssched.conf, and upssched-cmd files. I am running Ubuntu Server LTS. I am new to this, so please correct me!

upsmon.conf:

RUN_AS_USER root

MONITOR myups@localhost 1 admin theman0205 master


# Network UPS Tools: example upsmon configuration
#
# This file contains passwords, so keep it secure.

# --------------------------------------------------------------------------
# RUN_AS_USER <userid>
#
# By default, upsmon splits into two processes.  One stays as root and
# waits to run the SHUTDOWNCMD.  The other one switches to another userid
# and does everything else.
#
# The default unprivileged user is set at compile-time with the option
#   'configure --with-user=...'
#
# You can override it with '-u <user>' when starting upsmon, or just
# define it here for convenience.
#
# Note: if you plan to use the reload feature, this file (upsmon.conf)
# must be readable by this user!  Since it contains passwords, DO NOT
# make it world-readable.  Also, do not make it writable by the upsmon
# user, since it creates an opportunity for an attack by changing the
# SHUTDOWNCMD to something malicious.
#
# For best results, you should create a new normal user like "nutmon",
# and make it a member of a "nut" group or similar.  Then specify it
# here and grant read access to the upsmon.conf for that group.
#
# This user should not have write access to upsmon.conf.
#
# (Unprivileged) OS account to run as:
# RUN_AS_USER nut

# --------------------------------------------------------------------------
# MONITOR <system> <powervalue> <username> <password> ("primary"|"secondary")
#
# List systems you want to monitor.  Not all of these may supply power
# to the system running upsmon, but if you want to watch it, it has to
# be in this section.
#
# You must have at least one of these declared.
#
# <system> is a UPS identifier in the form <upsname>@<hostname>[:<port>]
# like ups@localhost, su700@mybox, etc.
#
# Examples:
#
#  - "su700@mybox" means a UPS called "su700" on a system called "mybox"
#
#  - "fenton@bigbox:5678" is a UPS called "fenton" on a system called
#    "bigbox" which runs upsd on port "5678".
#
# The UPS names like "su700" and "fenton" are set in your ups.conf
# in [brackets] which identify a section for a particular driver.
#
# If the ups.conf on host "doghouse" has a section called "snoopy", the
# identifier for it would be "snoopy@doghouse".
#
# <powervalue> is an integer - the number of power supplies that this UPS
# feeds on this system.  Most personal computers only have one power supply,
# so this value is normally set to 1, while most modern servers have at least
# two.  You need a pretty big or special box to have any other value here.
#
# You can also set this to 0 for a system that doesn't take any power
# from the MONITORed supply, which you still want to monitor (e.g. for an
# administrative workstation fed from a different circuit than the datacenter
# servers it monitors). Use <powervalue> if 0 when you want to hear about
# changes for a given UPS without shutting down when it goes critical.
#
# <username> and <password> must match an entry in that system's
# upsd.users.  If your NUT username is "monuser" and your password is
# "blah", the upsd.users would look like this:
#
#	[monuser]
#		password  = blah
#		upsmon primary 	# (or secondary)
#
# "primary" means this system will shutdown last, allowing the secondary
# systems time to shutdown first.
#
# "secondary" means this system shuts down immediately when power goes
# critical and less than MINSUPPLIES power sources have reliable input feeds.
#
# The general assumption is that the "primary" system is the one with direct
# connection to an UPS (such as serial or USB cable), so the primary system
# runs the NUT driver and 'upsd' server locally and can manage the device,
# and it would often tell the UPS to completely power itself off as a step
# in power-race avoidance (see POWERDOWNFLAG for details).
#
# Also, since the primary system stays up the longest, it suffers higher risks
# of ungraceful shutdown if the estimation of remaining runtime (or of the
# time it takes to shut down this system) was guessed wrong. By consequence,
# the "secondary" systems typically monitor the power environment state
# through the 'upsd' processes running on the remote (often "primary") systems
# and do not directly interact with an UPS (no local NUT drivers are running
# on the secondary systems). As such, secondaries typically shut down as
# soon as there is a sufficiently long power outage, or a low-battery alert
# from the UPS, or a loss of connection to the primary while the power was
# last known to be missing.
#
# This assumption and configuration can also make sense for networked UPSes,
# where a rack full of servers might overload the communications capacity
# of the networked management card on the UPS - in this case you might either
# reduce the 'snmp-ups' or 'netxml-ups' driver polling rate, or dedicate a
# "primary" server and set up the rest as "secondary" systems.
#
# In case of such large setups as mentioned above, beware also that shutdown
# times of the rack done all at once can substantially differ from smaller
# scale experiments with single-server shutdowns, since systems can compete
# for shared storage and other limited resources as they go down (and also
# not everyone may safely shut down simultaneously - e.g. a NAS or DB server
# would better go down after all its clients). You would be well served by
# higher-end UPSes with manageable thresholds to declare a critical state.
#
# Examples:
#
# MONITOR myups@bigserver 1 upswired blah primary
# MONITOR su700@server.example.com 1 monuser secretpass secondary
# MONITOR myups@localhost 1 monuser pass primary	# (or secondary)

# --------------------------------------------------------------------------
# MINSUPPLIES <num>
#
# Give the number of power supplies that must be receiving power to keep
# this system running.  Most systems have one power supply, so you would
# put "1" in this field.
#
# Large/expensive server type systems usually have more, and can run with
# a few missing.  Some of these can run with 2 out of 4, for example,
# so you'd set that to 2.  The idea is to keep the box running as long
# as possible, right?
#
# Obviously you have to put the redundant supplies on different UPS circuits
# for this to make sense!  See big-servers.txt in the docs subdirectory
# for more information and ideas on how to use this feature.

MINSUPPLIES 1

# --------------------------------------------------------------------------
# SHUTDOWNCMD "<command>"
#
# upsmon runs this command when the system needs to be brought down.
#
# This should work just about everywhere ... if it doesn't, well, change it,
# perhaps to a more complicated custom script.
#
# Note that while you experiment with the initial setup and want to test how
# your configuration reacts to power state changes and ultimately when power
# is reported to go critical, but do not want your system to actually turn
# off, consider setting the SHUTDOWNCMD temporarily to do something benign -
# such as posting a message with 'logger' or 'wall' or 'mailx'. Do be careful
# to plug the UPS back into the wall in a timely fashion.
#
# For Windows setup use something like:
# SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0"
# If you have command line using space character you have to add double quote to them, like this:
# SHUTDOWNCMD "\"C:\\Program Files\\some command.bat\" -first_arg -second_arg"
# Or use the old DOS 8.3 file name, like this:
# SHUTDOWNCMD "C:\\PROGRA~1\\SOMECO~1.bat -first_arg -second_arg"

#"/sbin/shutdown -h +0"
SHUTDOWNCMD "/usr/local/bin/upsshutofflowbat.sh"
NOTIFYCMD /sbin/upssched
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC

# --------------------------------------------------------------------------
# SHUTDOWNEXIT <boolean|num>
#
# After initiating shutdown, should this upsmon daemon itself exit?
# By doing so NUT secondary systems can tell the NUT primary that
# it can proceed with its own shutdown and eventually tell the UPS
# to cut power for the load. ("Yes" by default)
#
# Some "secondary" systems with workloads that take considerable time
# to stop (e.g. virtual machines or large databases) can benefit from
# reporting (by virtue of logging off the data server) that they are
# ready for the "primary" system to begin its own shutdown and eventually
# to tell the UPS to cut the power - not as soon as they have triggered
# their own shutdown, but at a later point (e.g. when the upsmon service
# is stopped AFTER the heavier workloads).
#
# Note that the actual ability to complete such shutdown depends on the
# remaining battery run-time at the moment when UPS power state becomes
# considered critical and the shutdowns begin. You may also have to tune
# HOSTSYNC on the NUT primary to be long enough for those secondaries to
# stop their services. In practice, it may be worthwhile to investigate
# ways to trigger shutdowns earlier on these systems, e.g. by setting up
# `upssched` integration, or `dummy-ups` driver with overrides for stricter
# `battery.charge` or `battery.runtime` triggers than used by the rest of
# your servers.
#
# This option supports Boolean-style strings (yes/on/true or no/off/false)
# or numbers to define a delay (in seconds) between calling SHUTDOWNCMD
# and exiting the daemon. Zero means immediate exit (default), negative
# values mean never exiting on its own accord.
#
#SHUTDOWNEXIT yes

# --------------------------------------------------------------------------
# NOTIFYCMD <command>
#
# upsmon calls this to send messages when things happen
#
# This command is called with the full text of the message (from NOTIFYMSG)
# as one argument.
#
# The environment string NOTIFYTYPE will contain the type string of
# whatever caused this event to happen.
#
# The environment string UPSNAME will contain the name of the system/device
# that generated the change.
#
# Note that this is only called for NOTIFY events that have EXEC set with
# NOTIFYFLAG.  See NOTIFYFLAG below for more details.
#
# Making this some sort of shell script might not be a bad idea.
# Alternately you can use the upssched program as your NOTIFYCMD for some
# more complex setups (e.g. to ease handling of notification storms).
# For more information and ideas, see docs/scheduling.txt
#
# Example:
# NOTIFYCMD /bin/notifyme

# --------------------------------------------------------------------------
# POLLFREQ <n>
#
# Polling frequency for normal activities, measured in seconds.
#
# Adjust this to keep upsmon from flooding your network, but don't make
# it too high or it may miss certain short-lived power events.

POLLFREQ 5

# --------------------------------------------------------------------------
# POLLFREQALERT <n>
#
# Polling frequency in seconds while UPS on battery.
#
# You can make this number lower than POLLFREQ, which will make updates
# faster when any UPS is running on battery.  This is a good way to tune
# network load if you have a lot of these things running.
#
# The default is 5 seconds for both this and POLLFREQ.

POLLFREQALERT 5

# --------------------------------------------------------------------------
# HOSTSYNC - How long upsmon will wait before giving up on another upsmon
#
# The primary upsmon process uses this number when waiting for secondary
# systems to disconnect once it has set the forced shutdown (FSD) flag.
# If they don't disconnect after this many seconds, it goes on without them.
#
# Similarly, upsmon secondary processes wait up to this interval for the
# primary upsmon to set FSD when an UPS they are monitoring goes critical -
# that is, on battery and low battery.  If the primary doesn't do its job,
# the secondaries will shut down anyway to avoid damage to the file systems.
#
# This "wait for FSD" is done to avoid races where the status changes
# to critical and back between polls by the primary.

HOSTSYNC 15

# --------------------------------------------------------------------------
# DEADTIME - Interval to wait before declaring a stale ups "dead"
#
# upsmon requires a UPS to provide status information every few seconds
# (see POLLFREQ and POLLFREQALERT) to keep things updated.  If the status
# fetch fails, the UPS is marked stale.  If it stays stale for more than
# DEADTIME seconds, the UPS is marked dead.
#
# A dead UPS that was last known to be on battery is assumed to have gone
# to a low battery condition.  This may force a shutdown if it is providing
# a critical amount of power to your system.
#
# Note: DEADTIME should be a multiple of POLLFREQ and POLLFREQALERT.
# Otherwise you'll have "dead" UPSes simply because upsmon isn't polling
# them quickly enough.  Rule of thumb: take the larger of the two
# POLLFREQ values, and multiply by 3.

DEADTIME 15

# --------------------------------------------------------------------------
# POWERDOWNFLAG - Flag file for forcing UPS shutdown on the primary system
#
# upsmon will create a file with this name in primary mode when it's time
# to shut down the load.  You should check for this file's existence in
# your shutdown scripts and run 'upsdrvctl shutdown' if it exists, to tell
# the UPS(es) to power off.
#
# See the config-notes.txt file in the docs subdirectory for more information.
# Refer to the section:
# [[UPS_shutdown]] "Configuring automatic shutdowns for low battery events"
# or refer to the online version.
#
# For Windows setup use something like:
# POWERDOWNFLAG "C:\\killpower"
#
# For Unix/Linux systems the legacy default is:
# POWERDOWNFLAG /etc/killpower
POWERDOWNFLAG "/etc/killpower"

# --------------------------------------------------------------------------
# NOTIFYMSG - change messages sent by upsmon when certain events occur
#
# You can change the default messages to something else if you like.
#
# NOTIFYMSG <notify type> "message"
#
# NOTIFYMSG ONLINE	"UPS %s on line power"
# NOTIFYMSG ONBATT	"UPS %s on battery"
# NOTIFYMSG LOWBATT	"UPS %s battery is low"
# NOTIFYMSG FSD		"UPS %s: forced shutdown in progress"
# NOTIFYMSG COMMOK	"Communications with UPS %s established"
# NOTIFYMSG COMMBAD	"Communications with UPS %s lost"
# NOTIFYMSG SHUTDOWN	"Auto logout and shutdown proceeding"
# NOTIFYMSG REPLBATT	"UPS %s battery needs to be replaced"
# NOTIFYMSG NOCOMM	"UPS %s is unavailable"
# NOTIFYMSG NOPARENT	"upsmon parent process died - shutdown impossible"
# NOTIFYMSG CAL		"UPS %s: calibration in progress"
# NOTIFYMSG OFF		"UPS %s: administratively OFF or asleep"
# NOTIFYMSG NOTOFF	"UPS %s: no longer administratively OFF or asleep"
# NOTIFYMSG BYPASS	"UPS %s: on bypass (powered, not protecting)"
# NOTIFYMSG NOTBYPASS	"UPS %s: no longer on bypass"
#
# Note that %s is replaced with the identifier of the UPS in question.
#
# Possible values for <notify type>:
#
# ONLINE   : UPS is back online
# ONBATT   : UPS is on battery
# LOWBATT  : UPS has a low battery (if also on battery, it's "critical")
# FSD      : UPS is being shutdown by the primary (FSD = "Forced Shutdown")
# COMMOK   : Communications established with the UPS
# COMMBAD  : Communications lost to the UPS
# SHUTDOWN : The system is being shutdown
# REPLBATT : The UPS battery is bad and needs to be replaced
# NOCOMM   : A UPS is unavailable (can't be contacted for monitoring)
# NOPARENT : The process that shuts down the system has died (shutdown impossible)

# --------------------------------------------------------------------------
# NOTIFYFLAG - change behavior of upsmon when NOTIFY events occur
#
# By default, upsmon sends walls (global messages to all logged in users)
# and writes to the syslog when things happen.
# Except for Windows where upsmon only writes to the syslog by default.
# You can change this.
#
# NOTIFYFLAG <notify type> <flag>[+<flag>][+<flag>] ...
#
# NOTIFYFLAG ONLINE	SYSLOG+WALL
# NOTIFYFLAG ONBATT	SYSLOG+WALL
# NOTIFYFLAG LOWBATT	SYSLOG+WALL
# NOTIFYFLAG FSD	SYSLOG+WALL
# NOTIFYFLAG COMMOK	SYSLOG+WALL
# NOTIFYFLAG COMMBAD	SYSLOG+WALL
# NOTIFYFLAG SHUTDOWN	SYSLOG+WALL
# NOTIFYFLAG REPLBATT	SYSLOG+WALL
# NOTIFYFLAG NOCOMM	SYSLOG+WALL
# NOTIFYFLAG NOPARENT	SYSLOG+WALL
#
# Possible values for the flags:
#
# SYSLOG - Write the message in the syslog
# WALL   - Write the message to all users on the system
# EXEC   - Execute NOTIFYCMD (see above) with the message
# IGNORE - Don't do anything
#
# If you use IGNORE, don't use any other flags on the same line.

# --------------------------------------------------------------------------
# OFFDURATION - put "OFF" state into effect if it persists for this many seconds
#
# NUT supports an "administrative OFF" for power devices which can be managed to
# turn off their application workload, while the UPS or ePDU remains accessible
# for monitoring and management. This toggle allows to delay propagation of such
# state into a known loss of a feed (possibly triggering FSD on `upsmon` clients
# which `MONITOR` the device and are in fact still alive -- e.g. with multiple
# power sources or because they as the load are not really turned off), because
# when some devices begin battery calibration, they report "OFF" for a few seconds
# and only then they might report "CAL" after switching all the power relays --
# thus causing false-positives for `upsmon` FSD trigger.
#
# A negative value means to disable decreasing the counter of working power
# supplies in such cases, and a zero makes the effect of detected "OFF" state
# immediate. Built-in default value is 30 (seconds).

OFFDURATION 30

# --------------------------------------------------------------------------
# RBWARNTIME - replace battery warning time in seconds
#
# upsmon will normally warn you about a battery that needs to be replaced
# every 43200 seconds, which is 12 hours.  It does this by triggering a
# NOTIFY_REPLBATT which is then handled by the usual notify structure
# you've defined above.
#
# If this number is not to your liking, override it here.

RBWARNTIME 43200

# --------------------------------------------------------------------------
# NOCOMMWARNTIME - no communications warning time in seconds
#
# upsmon will let you know through the usual notify system if it can't
# talk to any of the UPS entries that are defined in this file.  It will
# trigger a NOTIFY_NOCOMM by default every 300 seconds unless you
# change the interval with this directive.

NOCOMMWARNTIME 300

# --------------------------------------------------------------------------
# POLLFAIL_LOG_THROTTLE_MAX - device poll failure logging throttle
#
# upsmon normally reports polling failures for each device that are in place
# for each POLLFREQ loop (e.g. "Data stale" or "Driver not connected") to
# system log as configured.  If your devices are expected to be AWOL for an
# extended timeframe, you can use this throttle to reduce the stress on
# syslog traffic and storage, by posting these messages only once in every
# several loop cycles, and when the error condition has changed or cleared.
# A negative value means standard behavior, and a zero value means to never
# repeat the message (log only on start and end/change of the failure state).
#
#POLLFAIL_LOG_THROTTLE_MAX 100

# --------------------------------------------------------------------------
# FINALDELAY - last sleep interval before shutting down the system
#
# On a primary, upsmon will wait this long after sending the NOTIFY_SHUTDOWN
# before executing your SHUTDOWNCMD.  If you need to do something in between
# those events, increase this number.  Remember, at this point your UPS is
# almost depleted, so don't make this too high.  If needed, on high-end UPS
# devices you can usually configure when the low-battery state is announced
# based on estimated remaining run-time or on charge level of the batteries.
#
# Alternatively, you can set this very low so you don't wait around when
# it's time to shut down.  Some UPSes don't give much warning for low
# battery and will require a value of 0 here for a safe shutdown.
#
# Note: If FINALDELAY on the secondary is greater than HOSTSYNC on the
# primary, the primary will give up waiting for that secondary system
# to disconnect.

FINALDELAY 5

# --------------------------------------------------------------------------
# CERTPATH - path to certificates (database directory or directory with CA's)
#
# When compiled with SSL support, you can enter the certificate path here.
#
# With NSS:
# Certificates are stored in a dedicated database (split into 3 files).
# Specify the path of the database directory.
#
# CERTPATH /etc/nut/cert/upsmon
#
# With OpenSSL:
# Directory containing CA certificates in PEM format, used to verify
# the server certificate presented by the upsd server. The files each
# contain one CA certificate. The files are looked up by the CA subject
# name hash value, which must hence be available.
#
# CERTPATH /usr/ssl/certs
#
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# --------------------------------------------------------------------------
# CERTIDENT - self certificate name and database password
# CERTIDENT <certificate name> <database password>
#
# When compiled with SSL support with NSS, you can specify the certificate
# name to retrieve from database to authenticate itself and the password
# required to access certificate related private key.
#
# CERTIDENT "my nut monitor" "MyPasSw0rD"
#
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# --------------------------------------------------------------------------
# CERTHOST - security properties for an host
# CERTHOST <hostname> <certificate name> <certverify> <forcessl>
#
# When compiled with SSL support with NSS, you can specify security directive
# for each server you can contact.
# Each entry maps server name with the expected certificate name and flags
# indicating if the server certificate is verified and if the connection
# must be secure.
#
# CERTHOST localhost "My nut server" 1 1
#
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# --------------------------------------------------------------------------
# CERTVERIFY - make upsmon verify all connections with certificates
# CERTVERIFY 1
#
# When compiled with SSL support, make upsmon verify all connections with
# certificates.
# Without this, there is no guarantee that the upsd is the right host.
# Enabling this greatly reduces the risk of man in the middle attacks.
# This effectively forces the use of SSL, so don't use this unless
# all of your upsd hosts are ready for SSL and have their certificates
# in order.
# When compiled with NSS support of SSL, can be overridden for host
# specified with a CERTHOST directive.


# --------------------------------------------------------------------------
# FORCESSL - force upsmon to use SSL
# FORCESSL 1
#
# When compiled with SSL, specify that a secured connection must be used
# to communicate with upsd.
# If you don't use 'CERTVERIFY 1', then this will at least make sure
# that nobody can sniff your sessions without a large effort.  Setting
# this will make upsmon drop connections if the remote upsd doesn't
# support SSL, so don't use it unless all of them have it running.
# When compiled with NSS support of SSL, can be overridden for host
# specified with a CERTHOST directive.

# --------------------------------------------------------------------------
# DEBUG_MIN - specify minimal debugging level for upsmon daemon
# e.g. DEBUG_MIN 6
#
# Optionally specify a minimum debug level for `upsmon` daemon, e.g. for
# troubleshooting a deployment, without impacting foreground or background
# running mode directly, and without need to edit init-scripts or service
# unit definitions. Note that command-line option `-D` can only increase
# this verbosity level.
#
# NOTE: if the running daemon receives a `reload` command, presence of the
# `DEBUG_MIN NUMBER` value in the configuration file can be used to tune
# debugging verbosity in the running service daemon (it is recommended to
# comment it away or set the minimum to explicit zero when done, to avoid
# huge journals and I/O system abuse). Keep in mind that for this run-time
# tuning, the `DEBUG_MIN` value *present* in *reloaded* configuration files
# is applied instantly and overrides any previously set value, from file
# or CLI options, regardless of older logging level being higher or lower
# than the newly found number; a missing (or commented away) value however
# does not change the previously active logging verbosity.`

upssched.conf:

# Network UPS Tools - upssched.conf sample file
#
# ============================================================================
#
# CMDSCRIPT <scriptname>
#
# This script gets called to invoke commands for timers that trigger.
# It is given a single argument - the <timername> in your
# AT ... START-TIMER defines.
#
# *** This must be defined *before* the first AT line.  Otherwise the
#     program will complain and exit without doing anything.
#
# A shell script with a big case..esac construct should work nicely for this.
# An example has been provided to help you get started.

CMDSCRIPT /bin/upssched-cmd

PIPEFN /run/nut/upssched.pipe
LOCKFN /run/nut/upssched.lock
AT LOWBATT * EXECUTE lowbattsignal

upssched-cmd:

#! /bin/sh
#
# This script should be called by upssched via the CMDSCRIPT directive.
# 
# Here is a quick example to show how to handle a bunch of possible
# timer names with the help of the case structure.
#
# This script may be replaced with another program without harm.
#
# The first argument passed to your CMDSCRIPT is the name of the timer
# from your AT lines.

case $1 in
	onbattwarn)
		# Send a notification mail
		echo "The UPS has been on battery for awhile" \
		| mail -s"UPS monitor" bofh@pager.example.com
		# Create a flag-file on the filesystem, for your own processing
		/usr/bin/touch /some/path/ups-on-battery
		;;
	ups-back-on-power)
		# Delete the flag-file on the filesystem
		/bin/rm -f /some/path/ups-on-battery
		;;
	upsgone)
		logger -t upssched-cmd "The communication with UPS has been gone for awhile"
		;;
        lowbattsignal)
                logger -t upssched-cmd "UPS battery is low, running custom script"
                /usr/local/bin/upsshutofflowbat.sh
                ;;
	*)
		logger -t upssched-cmd "Unrecognized command: $1"
		;;
esac

[jimklimov]

Hello, this is quite the correct place to ask questions :)

In the report above you did not mention the NUT version you have - it may be important, as bugs here and there are found and fixed over the years, and distros tend to be 2-5 years behind development.

You also did not post the /usr/local/bin/upsshutofflowbat.sh script which you would call both as SHUTDOWNCMD in upsmon.conf (typically triggered for onbatt+lowbatt situation) and as an event handler in upssched. For all I know so far, you could be doing something to the driver there (maybe restart it in infinite loops like when a manually-executed run conflicts with the systemd wrapping?) that would cause its CPU usage to spike (probably as ever-different process IDs, if you do indeed loop-restart it).

It may help to see journal excerpts of your NUT services, especially if you would bump debug verbosity for the driver and maybe other daemons (see wiki).

You also probably don't need RUN_AS_USER root for upsmon (a stub process generally remains running as root to execute just SHUTDOWNCMD if/when needed). Although it might help if you were to initiate shutdowns from upssched, but generally calling upsmon -c fsd from it is more idiomatic and may be safer (by running less code as root). Needs a suitable SHUTDOWNCMD thiugh :)

[pollocluck]

Thanks for the reply! I'm not sure how to check the nut version, but I installed it earlier this month using the methods featured in this video. (sudo apt install nut nut-client nut-server libusb-1.0-0 libusb-1.0-0-dev)

Here is my upsshutofflowbat.sh file:

#!/bin/bash
docker container stop homeassistant music-assistant-server matter-server freshrss mealie nginx-proxy paperlessngx paperlessngx-broker-redis homarr
umount /dev/sda
umount /dev/sdb
umount /dev/sdc
sudo shutdown now #or /sbin/shutdown -h now

Here is the output of the journal-ctl -u nut-server:

-- Boot 88ac9cc8236d483180038b852ac9be90 --
Feb 06 02:49:28 myserver systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Feb 06 02:49:28 myserver systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Feb 06 02:49:29 myserver nut-server[974]: fopen /run/nut/upsd.pid: No such file or directory
Feb 06 02:49:29 myserver nut-server[974]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Feb 06 02:49:29 myserver upsd[974]: listening on 127.0.0.1 port 3493
Feb 06 02:49:29 myserver nut-server[974]: listening on 127.0.0.1 port 3493
Feb 06 02:49:29 myserver nut-server[974]: Connected to UPS [myups]: usbhid-ups-myups
Feb 06 02:49:29 myserver nut-server[974]: Found 1 UPS defined in ups.conf
Feb 06 02:49:29 myserver upsd[974]: Connected to UPS [myups]: usbhid-ups-myups
Feb 06 02:49:29 myserver upsd[974]: Found 1 UPS defined in ups.conf
Feb 06 02:49:29 myserver nut-server[974]: Running as foreground process, not saving a PID file
Feb 06 02:49:29 myserver nut-server[974]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 06 02:49:29 myserver upsd[974]: Running as foreground process, not saving a PID file
Feb 06 02:49:29 myserver upsd[974]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 21 23:44:39 myserver systemd[1]: Reloading nut-server.service - Network UPS Tools - power devices information server...
Feb 21 23:44:39 myserver nut-server[2909869]: Network UPS Tools upsd 2.8.1
Feb 21 23:44:39 myserver nut-server[974]: mainloop: Interrupted system call
Feb 21 23:44:39 myserver systemd[1]: Reloaded nut-server.service - Network UPS Tools - power devices information server.
Feb 21 23:44:39 myserver nut-server[974]: SIGHUP: reloading configuration
Feb 21 23:44:39 myserver upsd[974]: mainloop: Interrupted system call
Feb 21 23:44:39 myserver upsd[974]: SIGHUP: reloading configuration
Feb 21 23:44:39 myserver nut-server[974]: Applying debug level 0 from original command line arguments
Feb 21 23:44:39 myserver upsd[974]: Applying debug level 0 from original command line arguments
Feb 21 23:45:02 myserver systemd[1]: Reloading nut-server.service - Network UPS Tools - power devices information server...
Feb 21 23:45:02 myserver nut-server[2910066]: Network UPS Tools upsd 2.8.1
Feb 21 23:45:02 myserver upsd[974]: mainloop: Interrupted system call
Feb 21 23:45:02 myserver nut-server[974]: mainloop: Interrupted system call
Feb 21 23:45:02 myserver nut-server[974]: SIGHUP: reloading configuration
Feb 21 23:45:02 myserver nut-server[974]: Applying debug level 0 from original command line arguments
Feb 21 23:45:02 myserver upsd[974]: SIGHUP: reloading configuration
Feb 21 23:45:02 myserver upsd[974]: Applying debug level 0 from original command line arguments
Feb 21 23:45:02 myserver systemd[1]: Reloaded nut-server.service - Network UPS Tools - power devices information server.
Feb 22 00:08:25 myserver upsd[974]: mainloop: Interrupted system call
Feb 22 00:08:25 myserver nut-server[974]: mainloop: Interrupted system call
Feb 22 00:08:25 myserver nut-server[974]: Signal 15: exiting
Feb 22 00:08:25 myserver upsd[974]: Signal 15: exiting
Feb 22 00:08:25 myserver systemd[1]: Stopping nut-server.service - Network UPS Tools - power devices information server...
Feb 22 00:08:25 myserver nut-server[974]: Network UPS Tools upsd 2.8.1
Feb 22 00:08:25 myserver systemd[1]: nut-server.service: Deactivated successfully.
Feb 22 00:08:25 myserver systemd[1]: Stopped nut-server.service - Network UPS Tools - power devices information server.
Feb 22 00:08:25 myserver systemd[1]: nut-server.service: Consumed 2min 28.214s CPU time, 1.3M memory peak, 236.0K memory swap peak.
-- Boot 46502e4dcb2d43979b89b59aca32f331 --
Feb 22 00:10:39 myserver systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Feb 22 00:10:39 myserver systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Feb 22 00:10:39 myserver nut-server[1386]: fopen /run/nut/upsd.pid: No such file or directory
Feb 22 00:10:39 myserver nut-server[1386]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Feb 22 00:10:39 myserver nut-server[1386]: listening on 127.0.0.1 port 3493
Feb 22 00:10:39 myserver upsd[1386]: listening on 127.0.0.1 port 3493
Feb 22 00:10:39 myserver nut-server[1386]: Connected to UPS [myups]: usbhid-ups-myups
Feb 22 00:10:39 myserver nut-server[1386]: Found 1 UPS defined in ups.conf
Feb 22 00:10:39 myserver upsd[1386]: Connected to UPS [myups]: usbhid-ups-myups
Feb 22 00:10:39 myserver upsd[1386]: Found 1 UPS defined in ups.conf
Feb 22 00:10:39 myserver nut-server[1386]: Running as foreground process, not saving a PID file
Feb 22 00:10:39 myserver nut-server[1386]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 22 00:10:39 myserver upsd[1386]: Running as foreground process, not saving a PID file
Feb 22 00:10:39 myserver upsd[1386]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 22 00:32:48 myserver systemd[1]: Reloading nut-server.service - Network UPS Tools - power devices information server...
Feb 22 00:32:48 myserver nut-server[7385]: Network UPS Tools upsd 2.8.1
Feb 22 00:32:48 myserver upsd[1386]: mainloop: Interrupted system call
Feb 22 00:32:48 myserver nut-server[1386]: mainloop: Interrupted system call
Feb 22 00:32:48 myserver nut-server[1386]: SIGHUP: reloading configuration
Feb 22 00:32:48 myserver nut-server[1386]: Applying debug level 0 from original command line arguments
Feb 22 00:32:48 myserver upsd[1386]: SIGHUP: reloading configuration
Feb 22 00:32:48 myserver upsd[1386]: Applying debug level 0 from original command line arguments
Feb 22 00:32:48 myserver systemd[1]: Reloaded nut-server.service - Network UPS Tools - power devices information server.
Feb 23 04:00:21 myserver upsd[1386]: mainloop: Interrupted system call
Feb 23 04:00:21 myserver nut-server[1386]: mainloop: Interrupted system call
Feb 23 04:00:21 myserver nut-server[1386]: Signal 15: exiting
Feb 23 04:00:21 myserver nut-server[1386]: Network UPS Tools upsd 2.8.1
Feb 23 04:00:21 myserver upsd[1386]: Signal 15: exiting
Feb 23 04:00:21 myserver systemd[1]: Stopping nut-server.service - Network UPS Tools - power devices information server...
Feb 23 04:00:21 myserver systemd[1]: nut-server.service: Deactivated successfully.
Feb 23 04:00:21 myserver systemd[1]: Stopped nut-server.service - Network UPS Tools - power devices information server.
Feb 23 04:00:21 myserver systemd[1]: nut-server.service: Consumed 3.673s CPU time, 1.5M memory peak, 0B memory swap peak.
-- Boot 68c09862329b447a992b8352ef05f2e2 --
Feb 23 04:00:51 myserver systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Feb 23 04:00:51 myserver systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Feb 23 04:00:51 myserver nut-server[1402]: fopen /run/nut/upsd.pid: No such file or directory
Feb 23 04:00:51 myserver nut-server[1402]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Feb 23 04:00:51 myserver nut-server[1402]: listening on 127.0.0.1 port 3493
Feb 23 04:00:51 myserver upsd[1402]: listening on 127.0.0.1 port 3493
Feb 23 04:00:51 myserver nut-server[1402]: Connected to UPS [myups]: usbhid-ups-myups
Feb 23 04:00:51 myserver nut-server[1402]: Found 1 UPS defined in ups.conf
Feb 23 04:00:51 myserver upsd[1402]: Connected to UPS [myups]: usbhid-ups-myups
Feb 23 04:00:51 myserver upsd[1402]: Found 1 UPS defined in ups.conf
Feb 23 04:00:51 myserver nut-server[1402]: Running as foreground process, not saving a PID file
Feb 23 04:00:51 myserver nut-server[1402]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:00:51 myserver upsd[1402]: Running as foreground process, not saving a PID file
Feb 23 04:00:51 myserver upsd[1402]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:24:46 myserver nut-server[1402]: mainloop: Interrupted system call
Feb 23 04:24:46 myserver nut-server[1402]: Signal 15: exiting
Feb 23 04:24:46 myserver nut-server[1402]: Network UPS Tools upsd 2.8.1
Feb 23 04:24:46 myserver systemd[1]: Stopping nut-server.service - Network UPS Tools - power devices information server...
Feb 23 04:24:46 myserver upsd[1402]: mainloop: Interrupted system call
Feb 23 04:24:46 myserver upsd[1402]: Signal 15: exiting
Feb 23 04:24:46 myserver systemd[1]: nut-server.service: Deactivated successfully.
Feb 23 04:24:46 myserver systemd[1]: Stopped nut-server.service - Network UPS Tools - power devices information server.
-- Boot c2fb593b61cf4a6c85d460d324c42548 --
Feb 23 04:25:39 myserver systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Feb 23 04:25:39 myserver systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Feb 23 04:25:40 myserver nut-server[934]: fopen /run/nut/upsd.pid: No such file or directory
Feb 23 04:25:40 myserver nut-server[934]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Feb 23 04:25:40 myserver upsd[934]: listening on 127.0.0.1 port 3493
Feb 23 04:25:40 myserver nut-server[934]: listening on 127.0.0.1 port 3493
Feb 23 04:25:40 myserver nut-server[934]: Connected to UPS [myups]: usbhid-ups-myups
Feb 23 04:25:40 myserver nut-server[934]: Found 1 UPS defined in ups.conf
Feb 23 04:25:40 myserver upsd[934]: Connected to UPS [myups]: usbhid-ups-myups
Feb 23 04:25:40 myserver upsd[934]: Found 1 UPS defined in ups.conf
Feb 23 04:25:40 myserver nut-server[934]: Running as foreground process, not saving a PID file
Feb 23 04:25:40 myserver nut-server[934]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:25:40 myserver upsd[934]: Running as foreground process, not saving a PID file
Feb 23 04:25:40 myserver upsd[934]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it

[jimklimov]

Thanks for the log, at least now we know you have a (moderately old) NUT v2.8.1. There don't seem to be any relevant fixes for usbhid-ups CPU hogging after that, at least upon cursory history review.

It can still be helpful to see also the journal of nut-driver@myups.service (notably to see if it was frequently restarting etc. at the time your CPU was stressed). If there's nothing apparent from existing logs, see https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity about getting more info from these programs.

On another note, if you have a modern general-purpose Ubuntu Server, the upsshutofflowbat.sh seems superficial: the usual OS shutdown procedures should take care of stopping the services and un-mounting the file systems after nobody uses them.

Here it might suffice to not use upssched from upsmon.conf at all, just specify SHUTDOWNCMD "/sbin/shutdown -h +0" or similar (so it works both for default reaching of OL OB flags in ups.status, as well as for upsmon -c fsd calls to trigger the UPS-related shutdown including an attempt to power it off in the end, or power-cycle if wall power has returned).

The upssched approach is more useful for people who aim to shut down not based on device status reports, but after e.g. spending a minute on battery (so it is not a short-lived glitch) and keeping most of the charge in the UPS. Then they set up a TIMER rule for that.

[pollocluck]

Thank you again for the response! Looking at that log again I apologize for not noticing the version number. Is there a reason for the apt version of nut being so behind? It seems like many of the popular nut tutorials utilize this method.

The main reason why I wanted to use that bash script is when I shut down the 24.04.4 LTS server without manually unmounting external drives, the folders appear empty after booting up which causes issues for some of my services if I don't remove them with rm -r, remount the drives, and restart the services. I probably could write a different script to counteract this, but I was hoping that current script would make managing the server easier in case the UPS battery went below 60% when I wasn't physically around.

Regarding the upssched point you made, how would I utilize the SHUTDOWNCMD if a battery limit is met, such as 60?

Edit: Just to confirm, since my low battery threshold has been overridden to 60%, will it automatically run the SHUTDOWNCMD when that is hit? I apologize if I'm asking a question that has an obvious answer im not understanding.

Here are the logs for that service:

-- Boot 2e1293e4194f44aebec78239cd49b01e --
Feb 06 02:47:34 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 06 02:47:34 myserver nut-driver@myups[878]: Using subdriver: APC HID 0.100
Feb 06 02:47:34 myserver nut-driver@myups[878]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 06 02:47:34 myserver nut-driver@myups[878]: USB communication driver (libusb 1.0) 0.46
Feb 06 02:47:34 myserver usbhid-ups[914]: Startup successful
Feb 06 02:47:34 myserver systemd[1]: Started nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 06 02:47:34 myserver nut-driver@myups[758]: Network UPS Tools - UPS driver controller 2.8.1
Feb 06 02:47:34 myserver usbhid-ups[914]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 06 02:47:34 myserver usbhid-ups[914]: sock_connect: enabling asynchronous mode (auto)
Feb 06 02:49:10 myserver systemd[1]: Stopping nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 06 02:49:10 myserver usbhid-ups[914]: Signal 15: exiting
Feb 06 02:49:10 myserver usbhid-ups[914]: WARNING: send_to_all: write 38 bytes to socket 10 failed (ret=-1), disconnecting: Broken pipe
Feb 06 02:49:11 myserver nut-driver@myups[1923]: fopen /run/nut/usbhid-ups-myups.pid: No such file or directory
Feb 06 02:49:11 myserver nut-driver@myups[1923]: Network UPS Tools - UPS driver controller 2.8.1
Feb 06 02:49:11 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 06 02:49:11 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
-- Boot 88ac9cc8236d483180038b852ac9be90 --
Feb 06 02:49:28 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 06 02:49:28 myserver nut-driver@myups[857]: Using subdriver: APC HID 0.100
Feb 06 02:49:28 myserver nut-driver@myups[857]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 06 02:49:28 myserver nut-driver@myups[857]: USB communication driver (libusb 1.0) 0.46
Feb 06 02:49:28 myserver nut-driver@myups[755]: Network UPS Tools - UPS driver controller 2.8.1
Feb 06 02:49:28 myserver usbhid-ups[970]: Startup successful
Feb 06 02:49:28 myserver usbhid-ups[970]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 06 02:49:28 myserver systemd[1]: Started nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 06 02:49:29 myserver usbhid-ups[970]: sock_connect: enabling asynchronous mode (auto)
Feb 20 00:14:11 myserver usbhid-ups[970]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want>
Feb 20 00:14:13 myserver usbhid-ups[970]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want>
Feb 20 00:14:15 myserver usbhid-ups[970]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want>
Feb 20 00:14:17 myserver usbhid-ups[970]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want>
Feb 21 23:44:39 myserver usbhid-ups[970]: sock_connect: enabling asynchronous mode (auto)
Feb 21 23:44:39 myserver usbhid-ups[970]: Handling requested live reload of NUT driver configuration for [myups]
Feb 21 23:44:39 myserver usbhid-ups[970]: Applying debug level 0 from original command line arguments
Feb 21 23:44:39 myserver usbhid-ups[970]: Completed requested live reload of NUT driver configuration for [myups]: 0
Feb 21 23:45:02 myserver usbhid-ups[970]: sock_connect: enabling asynchronous mode (auto)
Feb 21 23:45:02 myserver usbhid-ups[970]: Handling requested live reload of NUT driver configuration for [myups]
Feb 21 23:45:02 myserver usbhid-ups[970]: dstate_setflags: base variable (battery.charge.low) is immutable
Feb 21 23:45:02 myserver usbhid-ups[970]: Applying debug level 0 from original command line arguments
Feb 21 23:45:02 myserver usbhid-ups[970]: Completed requested live reload of NUT driver configuration for [myups]: 0
Feb 22 00:08:25 myserver systemd[1]: Stopping nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 22 00:08:25 myserver usbhid-ups[970]: Signal 15: exiting
Feb 22 00:08:25 myserver usbhid-ups[970]: WARNING: send_to_all: write 38 bytes to socket 10 failed (ret=-1), disconnecting: Broken pipe
Feb 22 00:08:26 myserver nut-driver@myups[2913892]: fopen /run/nut/usbhid-ups-myups.pid: No such file or directory
Feb 22 00:08:26 myserver nut-driver@myups[2913892]: Network UPS Tools - UPS driver controller 2.8.1
Feb 22 00:08:26 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 22 00:08:26 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 22 00:08:26 myserver systemd[1]: nut-driver@myups.service: Consumed 33min 24.475s CPU time, 2.2M memory peak, 256.0K memory swap peak.
-- Boot 46502e4dcb2d43979b89b59aca32f331 --
Feb 22 00:10:37 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 22 00:10:38 myserver nut-driver@myups[934]: Using subdriver: APC HID 0.100
Feb 22 00:10:38 myserver nut-driver@myups[934]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 22 00:10:38 myserver nut-driver@myups[934]: USB communication driver (libusb 1.0) 0.46
Feb 22 00:10:38 myserver nut-driver@myups[934]: using 'battery.charge' to set battery low state
Feb 22 00:10:38 myserver usbhid-ups[934]: using 'battery.charge' to set battery low state
Feb 22 00:10:38 myserver nut-driver@myups[934]: using 'battery.runtime' to set battery low state
Feb 22 00:10:38 myserver usbhid-ups[934]: using 'battery.runtime' to set battery low state
Feb 22 00:10:38 myserver usbhid-ups[1034]: Startup successful
Feb 22 00:10:38 myserver usbhid-ups[1034]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 22 00:10:38 myserver usbhid-ups[1034]: Signal 15: exiting
Feb 22 00:10:38 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 22 00:10:38 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 22 00:10:39 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 22 00:10:39 myserver nut-driver@myups[1374]: Using subdriver: APC HID 0.100
Feb 22 00:10:39 myserver nut-driver@myups[1374]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 22 00:10:39 myserver nut-driver@myups[1374]: USB communication driver (libusb 1.0) 0.46
Feb 22 00:10:39 myserver nut-driver@myups[1374]: using 'battery.charge' to set battery low state
Feb 22 00:10:39 myserver nut-driver@myups[1374]: using 'battery.runtime' to set battery low state
Feb 22 00:10:39 myserver usbhid-ups[1374]: using 'battery.charge' to set battery low state
Feb 22 00:10:39 myserver usbhid-ups[1374]: using 'battery.runtime' to set battery low state
Feb 22 00:10:39 myserver usbhid-ups[1383]: Startup successful
Feb 22 00:10:39 myserver usbhid-ups[1383]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 22 00:10:39 myserver nut-driver@myups[1339]: Network UPS Tools - UPS driver controller 2.8.1
Feb 22 00:10:39 myserver systemd[1]: Started nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 22 00:10:39 myserver usbhid-ups[1383]: sock_connect: enabling asynchronous mode (auto)
Feb 22 00:32:48 myserver usbhid-ups[1383]: sock_connect: enabling asynchronous mode (auto)
Feb 22 00:32:48 myserver usbhid-ups[1383]: Handling requested live reload of NUT driver configuration for [myups]
Feb 22 00:32:48 myserver usbhid-ups[1383]: dstate_setflags: base variable (battery.charge.low) is immutable
Feb 22 00:32:48 myserver usbhid-ups[1383]: Applying debug level 0 from original command line arguments
Feb 22 00:32:48 myserver usbhid-ups[1383]: Completed requested live reload of NUT driver configuration for [myups]: 0
Feb 23 04:00:21 myserver systemd[1]: Stopping nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 23 04:00:21 myserver usbhid-ups[1383]: WARNING: send_to_all: write 29 bytes to socket 10 failed (ret=-1), disconnecting: Broken pipe
Feb 23 04:00:21 myserver usbhid-ups[1383]: Signal 15: exiting
Feb 23 04:00:22 myserver nut-driver@myups[217964]: fopen /run/nut/usbhid-ups-myups.pid: No such file or directory
Feb 23 04:00:22 myserver nut-driver@myups[217964]: Network UPS Tools - UPS driver controller 2.8.1
Feb 23 04:00:22 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 23 04:00:22 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 23 04:00:22 myserver systemd[1]: nut-driver@myups.service: Consumed 1d 2h 58min 55.984s CPU time, 2.7M memory peak, 0B memory swap peak.
-- Boot 68c09862329b447a992b8352ef05f2e2 --
Feb 23 04:00:49 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 23 04:00:50 myserver nut-driver@myups[916]: Using subdriver: APC HID 0.100
Feb 23 04:00:50 myserver nut-driver@myups[916]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 23 04:00:50 myserver nut-driver@myups[916]: USB communication driver (libusb 1.0) 0.46
Feb 23 04:00:50 myserver nut-driver@myups[916]: using 'battery.charge' to set battery low state
Feb 23 04:00:50 myserver nut-driver@myups[916]: using 'battery.runtime' to set battery low state
Feb 23 04:00:50 myserver usbhid-ups[916]: using 'battery.charge' to set battery low state
Feb 23 04:00:50 myserver usbhid-ups[916]: using 'battery.runtime' to set battery low state
Feb 23 04:00:50 myserver usbhid-ups[1006]: Startup successful
Feb 23 04:00:50 myserver usbhid-ups[1006]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:00:50 myserver usbhid-ups[1006]: Signal 15: exiting
Feb 23 04:00:50 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 23 04:00:50 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 23 04:00:51 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 23 04:00:51 myserver nut-driver@myups[1390]: Using subdriver: APC HID 0.100
Feb 23 04:00:51 myserver nut-driver@myups[1390]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 23 04:00:51 myserver nut-driver@myups[1390]: USB communication driver (libusb 1.0) 0.46
Feb 23 04:00:51 myserver nut-driver@myups[1390]: using 'battery.charge' to set battery low state
Feb 23 04:00:51 myserver nut-driver@myups[1390]: using 'battery.runtime' to set battery low state
Feb 23 04:00:51 myserver usbhid-ups[1390]: using 'battery.charge' to set battery low state
Feb 23 04:00:51 myserver usbhid-ups[1390]: using 'battery.runtime' to set battery low state
Feb 23 04:00:51 myserver usbhid-ups[1399]: Startup successful
Feb 23 04:00:51 myserver usbhid-ups[1399]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:00:51 myserver nut-driver@myups[1355]: Network UPS Tools - UPS driver controller 2.8.1
Feb 23 04:00:51 myserver systemd[1]: Started nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 23 04:00:51 myserver usbhid-ups[1399]: sock_connect: enabling asynchronous mode (auto)
Feb 23 04:24:46 myserver systemd[1]: Stopping nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 23 04:24:46 myserver usbhid-ups[1399]: Signal 15: exiting
Feb 23 04:24:46 myserver usbhid-ups[1399]: WARNING: send_to_all: write 38 bytes to socket 10 failed (ret=-1), disconnecting: Broken pipe
Feb 23 04:24:47 myserver nut-driver@myups[17686]: fopen /run/nut/usbhid-ups-myups.pid: No such file or directory
Feb 23 04:24:47 myserver nut-driver@myups[17686]: Network UPS Tools - UPS driver controller 2.8.1
Feb 23 04:24:47 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 23 04:24:47 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
-- Boot c2fb593b61cf4a6c85d460d324c42548 --
Feb 23 04:25:39 myserver systemd[1]: Starting nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 23 04:25:39 myserver nut-driver@myups[855]: Using subdriver: APC HID 0.100
Feb 23 04:25:39 myserver nut-driver@myups[855]: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 23 04:25:39 myserver nut-driver@myups[855]: USB communication driver (libusb 1.0) 0.46
Feb 23 04:25:39 myserver usbhid-ups[855]: using 'battery.charge' to set battery low state
Feb 23 04:25:39 myserver nut-driver@myups[855]: using 'battery.charge' to set battery low state
Feb 23 04:25:39 myserver nut-driver@myups[855]: using 'battery.runtime' to set battery low state
Feb 23 04:25:39 myserver usbhid-ups[855]: using 'battery.runtime' to set battery low state
Feb 23 04:25:39 myserver nut-driver@myups[773]: Network UPS Tools - UPS driver controller 2.8.1
Feb 23 04:25:39 myserver usbhid-ups[877]: Startup successful
Feb 23 04:25:39 myserver usbhid-ups[877]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Feb 23 04:25:39 myserver systemd[1]: Started nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 23 04:25:40 myserver usbhid-ups[877]: sock_connect: enabling asynchronous mode (auto)
Feb 23 05:15:01 myserver usbhid-ups[877]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration' option)? Note that some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact offline/on-battery (perhaps you want to set 'onlinedischarge' option).
Feb 23 09:39:11 myserver usbhid-ups[877]: ups_status_set: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration' option)? Note that some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact offline/on-battery (perhaps you want to set 'onlinedischarge' option).
Feb 23 11:48:30 myserver usbhid-ups[877]: seems that UPS [myups] is in OL+DISCHRG state now. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration' option)? Note that some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact offline/on-battery (perhaps you want to set 'onlinedischarge' option).
Feb 24 23:46:29 myserver systemd[1]: Stopping nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'...
Feb 24 23:46:29 myserver usbhid-ups[877]: Signal 15: exiting
Feb 24 23:46:29 myserver usbhid-ups[877]: WARNING: send_to_all: write 38 bytes to socket 10 failed (ret=-1), disconnecting: Broken pipe
Feb 24 23:46:30 myserver nut-driver@myups[224823]: fopen /run/nut/usbhid-ups-myups.pid: No such file or directory
Feb 24 23:46:30 myserver nut-driver@myups[224823]: Network UPS Tools - UPS driver controller 2.8.1
Feb 24 23:46:30 myserver systemd[1]: nut-driver@myups.service: Deactivated successfully.
Feb 24 23:46:30 myserver systemd[1]: Stopped nut-driver@myups.service - Network UPS Tools - device driver for NUT device 'myups'.
Feb 24 23:46:30 myserver systemd[1]: nut-driver@myups.service: Consumed 1min 9.886s CPU time, 2.2M memory peak, 0B memory swap peak.

[wow1633]

Also seeing the same issue with NUT 2.8.1 on Debian 13.3. Also did an update and not seeing a newer version of NUT.

[jimklimov]

Also did an update and not seeing a newer version of NUT.

Bring this bit up with the distro. NUT v2.8.4 is out since August, expecting 2.8.5 any time now.

Also seeing the same issue

Also with upssched, and similar scripts? Specifically usbhid-ups process is spiking? Is this the same PID consuming CPU for a long time, or is the driver restarting for whatever reason and re-initializing (device walk etc.) frequently? Any debug logs to share?

• https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity
• https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests

[Miyamoto72]

Just noticed my CPU is being fried by usbhid-ups process from NUT 2.8.1 in Debian stable.
Compiled 2.8.4 from the sources in Debian unstable - no more rampaging of the usbhid-ups process.