On 3/23/26 5:03 AM, Łukasz Michalski wrote:
Hi,
A little warning after my 3h debugging nut debugging session:
After upgrading nut from 2.8.2 to 2.8.4 /usr/lib/systemd/system-
shutdown/nutshutdown script will stop working if MODE in /etc/nut/
ups.conf is not set.
I have a running standalone configuration with nut driver, server and
monitor on single machine and I didn't set MODE in ups.conf.
Due to this commit:
https://github.com/jimklimov/nut/commit/
cccbd8774b1f7d4c749c114e649e6924cba2adc6
in 2.8.4 without MODE system shutdown will not issue a shutdown command
to UPS anymore.
Regards,
Łukasz
I upgraded a few days ago and going through old/new configs just
happen to catch the unset value and I changed it to standalone before
starting all the services (I was upgrading from and OLD 2.7 version with
config still in /etc/ups)
The wiki should be updated to note this. I just went through the wiki
setup and it does not mention the MODE setting at all.
There were a number of tenuous config changes with my update. But
with MODE set, the version has been working well, though I did have a
commanded shutdown when the driver lost contact with the UPS (and this
was a server). This seemed to be the result of removal/uninstall of the
prior version leaving the USB device in an inconsistent state.
After kernel update and full reboot, that hasn't reoccurred.
--
David C. Rankin, J.D.,P.E.
