search for: nutshutdown

...when the main electrical power is >> back. >> > > It sounds as if you are not sending a delayed command to the UPS to turn > it off. Are you using a GNU/Linux distribution with systemd? Which > version of nut are you using? Do you have > /usr/lib/systemd/system-shutdown/nutshutdown enabled? > > Roger > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > -------------- next part -------------- An HTML attachment was scrubb...

...24 ########### /etc/nut/upsd.users ########### [local_mon] password = ********* upsmon master ########### /etc/nut/upsmon.conf ########### MONITOR belkinusb at localhost 1 local_mon ********* master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /home/android/nutShutdown.sh POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYFLAG ONBATT WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 ########### /etc/nut/upssched.conf ########### CMDSCRIPT /bin/upssched-cmd...

...d, and The Right and True Thing to Do<tm>. However, the default scripts provided in the EPEL RPM aren't actually doing it. The host halts as expected but the UPS never gets the message. After a lot of false leads and frustration I narrowed it down to the /usr/lib/systemd/system-shutdown/nutshutdown script. It _appears_ that the calls to "upsmon -K" and "upsdrvctl shutdown" can't actually do anything because the USB device is in use. This _implies_ to me that nut-driver is still running, even this late in the shutdown process. I've "fixed" this problem by...

...t; What exactly is this supposed to do? The proposed service unit fixes an openSUSE 12.3 problem, in which the UPS is not powered off on system shutdown. > When system is shutting down because of power failure (and low battery) > ups should be powered off with /lib/systemd/system-shutdown/nutshutdown > script. In openSUSE 12.3 there is no directory /lib/systemd/system-shutdown, and no script "nutshutdown". I am guessing that you use Fedora. > That's also the correct location for ups shutdown script. My original script was in /lib/systemd and I was told in the systemd-d...

P.S. To articulate better what I am unclear about from your message: `nutshutdown` seems to run `@SBINDIR@/upsdrvctl shutdown`. >From my understanding, this would command - all - `ups.conf` UPS to shutdown. So this would already include the UPS monitored by any failover/multiplexing driver. In contrast, `upsdrvctl shutdown` would start up all these drivers again, respectively...

...ings improperly configured? Any suggestions? Thanks and > happy new year! > ########### /etc/nut/upsmon.conf ########### > MONITOR belkinusb at localhost 1 local_mon ********* master > MINSUPPLIES 1 > SHUTDOWNCMD "/sbin/shutdown -h +0" > NOTIFYCMD /home/android/nutShutdown.sh > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > NOTIFYMSG ONBATT "UPS %s on battery" > NOTIFYFLAG ONBATT WALL+EXEC > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > FINALDELAY 5 > ########### /et...

...SR 1500 USBS. 9 seconds after server poweroff, the > UPS powers off. When wall power returns the server restarts correctly. What exactly is this supposed to do? When system is shutting down because of power failure (and low battery) ups should be powered off with /lib/systemd/system-shutdown/nutshutdown script. That's also the correct location for ups shutdown script. It's executed after everything else. Using Before=umount.target is especially bad bad idea. It's not guaranteed that umount sync can finish in time, so you can have power down during filesystem sync with all the conseq...

...s.conf, I start up as follows without problems: [ups] driver = dummy-ups port = /etc/nut/5E.dev [ups2] driver = dummy-ups port = /etc/nut/APC.dev [failover] driver = failover port = dummy-ups-ups,dummy-ups-ups2 Is this what you had in mind? Appreciate any pointers regarding the `upsdrvctl` and `nutshutdown` specifics. Sebastian Am Mo., 12. Mai 2025 um 15:53 Uhr schrieb Jim Klimov < jimklimov+nut at gmail.com>: > Sounds great, thanks for the update! > > For communications with the other drivers (from failover or multiplexor), > I suggest using the local driver socket line the clon...

...n openSUSE 12.3 problem, in which the > UPS is not powered off on system shutdown. you mean regular shutdown or power failure shutdown? >> When system is shutting down because of power failure (and low >> battery) ups should be powered off with >> /lib/systemd/system-shutdown/nutshutdown script. > > In openSUSE 12.3 there is no directory /lib/systemd/system-shutdown, and > no script "nutshutdown". I am guessing that you use Fedora. That's odd, nutshutdown is part of upstream tarball and should be in place when nut is configured to use systemd http://anons...

...driver" or "upsdrvctl shutdown" (for all UPSes) should do these tricks. Jim On Mon, May 12, 2025 at 5:25?PM Sebastian Kuttnig via Nut-upsdev < nut-upsdev at alioth-lists.debian.net> wrote: > P.S. To articulate better what I am unclear about from your message: > > `nutshutdown` seems to run `@SBINDIR@/upsdrvctl shutdown`. > From my understanding, this would command - all - `ups.conf` UPS to > shutdown. > So this would already include the UPS monitored by any > failover/multiplexing driver. > In contrast, `upsdrvctl shutdown` would start up all these driver...

Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown # more /etc/init.d/ups #! /bin/bash # # ups: Starts the Network UPS Tools # # chkconfig: - 26 74 # description: Network UPS Tools is a collection of programs which provide a common \ # interface for monitoring and administering UPS hardware. # processname: upsd # config: /etc/ups/ # config: /etc/...

...gt; CC. Do you have a script in a systemd system-shutdown directory which calls > "upsdrvctl shutdown" ? > > ==> No Once the command "upsdrvctl shutdown" works, you will need to incorporate it in your shutdown process. NUT 2.7.4 includes file .../scripts/systemd/nutshutdown . Does Ubunti install this? > 5. File = notifycmd > #!/bin/bash > # > # NUT NOTIFYCMD script > PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin > trap "exit 0" SIGTERM > if [ "$NOTIFYTYPE" = "ONLINE" ]...

...(for all UPSes) should do these tricks. > > Jim > > > > On Mon, May 12, 2025 at 5:25?PM Sebastian Kuttnig via Nut-upsdev < > nut-upsdev at alioth-lists.debian.net> wrote: > >> P.S. To articulate better what I am unclear about from your message: >> >> `nutshutdown` seems to run `@SBINDIR@/upsdrvctl shutdown`. >> From my understanding, this would command - all - `ups.conf` UPS to >> shutdown. >> So this would already include the UPS monitored by any >> failover/multiplexing driver. >> In contrast, `upsdrvctl shutdown` would start...

...when power returns. To stop the UPS from beeping, you must turn it off. > ups.delay.shutdown: 20 > ups.delay.start: 30 > > is it something related? Yes, they are related: the two ups.delay values are used by the program which turns off the UPS. This program is called by by script nutshutdown which is part of the nut package. Do you have this script installed? What does command "systemctl status nutshutdown" report? Roger

On Thu, 1 Feb 2018, Lee Damon wrote: > I've "fixed" this problem by modifying the nutshutdown script: > #!/bin/sh > # stop nut driver to free up access to the device > /sbin/systemctl stop nut-driver > # make sure it has time to die > sleep 2 > # check to see if we need to actually shutdown the UPS then do it > /usr/sbin/upsmon -K >/dev/null 2>&1 &&...

On Thu, 18 Jul 2019, David White wrote: > NOTIFYCMD? /home/android/nutShutdown.sh > NOTIFYMSG? ONBATT? "USP %s on battery" > NOTIFYFLAG? ONBATT? EXEC Perhaps before plunging into upsmon debugging, and debugging your own custom NOTIFYCMD script, you could get the basic notifications of upsmon working using more complete NOTIFYFLAG and NOTIFYMSG declarations...

OpenSUSE 12.3 has fully embraced systemd, but to get NUT working correctly now requires some further systemd engineering in addition to the usual NUT configuration files. A new systemd service unit is needed to power off the UPS. The service unit consists of a new file /etc/systemd/system/ups-delayed-shutdown.service [Unit] Description=Initiate delayed UPS shutdown

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

...Any suggestions? >> Thanks and happy new year! > >> ########### /etc/nut/upsmon.conf ########### >> MONITOR belkinusb at localhost 1 local_mon ********* master >> MINSUPPLIES 1 >> SHUTDOWNCMD "/sbin/shutdown -h +0" >> NOTIFYCMD /home/android/nutShutdown.sh >> POLLFREQ 5 >> POLLFREQALERT 5 >> HOSTSYNC 15 >> DEADTIME 15 >> POWERDOWNFLAG /etc/killpower >> NOTIFYMSG ONBATT "UPS %s on battery" >> NOTIFYFLAG ONBATT WALL+EXEC >> RBWARNTIME 43200 >> NOCOMMWARNTIME 300 >> FI...