similar to: "Halt then reboot" script with systemd

First of all, please forgive me is this question has already been covered in these mailing lists; the "Search mailing list" link is dead, and I've only read the most recent monthly archives. I often have a situation where, for one of many possible reasons, the UPS always thinks that its battery is critical. And I'm even fine with a situation when it's an emergency

I've been wrasslin' with a problem on a CentOS 7 host that I'm using as my main NUT server. When the battery gets low while the server is shutting down it is supposed to signal the UPS to shut down as well. This is clear, well documented, 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

On 08/15/2013 10:02 PM, Roger Price wrote: > On Wed, 14 Aug 2013, Michal Hlavinka wrote: > >>> The service unit consists of a new file >>> /etc/systemd/system/ups-delayed-shutdown.service >> >> 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. you

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

On Wed, 14 Aug 2013, Michal Hlavinka wrote: >> The service unit consists of a new file >> /etc/systemd/system/ups-delayed-shutdown.service > > 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) >

On 08/10/2013 11:43 PM, Roger Price wrote: > 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

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 covering all

Hello, It seems that halt (reboot also) init script from SuSE 9.0 is not working with Xen. Has anyone stumbled onto such problem, disregarding the actual distribution, and found a working init script? ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit

Hi all, Is there any possibility (using libvirt C API or whatever else) to "propagate" shutdown events (reboot, halt, power off) to a host? The API seems to lack this functionality - there exists function virConnectDomainEventRegisterAny, but the virDomainEventStoppedDetailType enum does not distinguish between these 3 different situations. Moreover, while rebooting a machine, an

Yesterday I took two machines (both running Xen) down. When I booted them back up I had a whole mess of problems. First (which I finally got solved), is that the domains were saved, but the saved state got corrupted. This caused the machines to go into a continuous cycle of reboots. Second, I found out that I cannot shutdown or reboot my machines. I have not run into this problem other then

Roger, Thanks for the idea to add additional items to the notifyflag. That proved the monitor was indeed working as expected and led me to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here

Hi, I need some help to understand a backtrace. The situation is as follows: A diskless system acting as a kind of bandwithshaping firewall with both ipfw2 and ipfilter active at the same time. Ipfilter is used for port adress translation. The system panics about once every 6 hours. The network load is very low, only one Windows XP machine is connected but not actively used. I added a disk

On Tue, 31 Dec 2019, David White wrote: > ... But it did not actually turn off the UPS at all. The UPS kept > beeping and I had to turn it off manually. > > I thought that NUT would handle this. But perhaps it cannot for my unit? Or > perhaps I have things improperly configured? Any suggestions? Thanks and > happy new year! > ########### /etc/nut/upsmon.conf

While I was tying down a supernet to the discard interface, the box crashed on me. Its a STABLE box from June 4th. I was in zebra at the time and thought I would route a /24 to ds0 instead of to the IP on ds0 (which I had done for a number of other aggregate routes). The only other "strange" thing about the box is that ds0 is loaded via kld. I will see if I can reproduce it on a

Hi, I have a CyberPower UPS connected to a Ubuntu karmic machine. All functions are working well. I can use upsc to see all the UPS parameters, power loss and battery low events are correctly detected, and shutdown is correctly initiated. If I run upsdrvctl shutdown, the UPS cuts power immediately. However, if I simulate a shutdown with upsmon -c fsd, the UPS fails to cut power. The

On Sat, 7 May 2016, Min Wang wrote: > I am using centos 6.3, and?nut-2.6.5-2.el6.x86_64. > could you explain why not sending "a delayed command to the UPS to turn it off" may cause that issue? ? You need to stop the UPS from beeping. Only then can you get a clear restart when power returns. To stop the UPS from beeping, you must turn it off. > ups.delay.shutdown: 20 >

On 1/1/2020 2:21 AM, Roger Price wrote: > On Tue, 31 Dec 2019, David White wrote: > >> ... But it did not actually turn off the UPS at all. The UPS kept >> beeping and I had to turn it off manually. >> >> I thought that NUT would handle this. But perhaps it cannot for my >> unit? Or perhaps I have things improperly configured? Any suggestions? >> Thanks

Every few days now I get a panic like the one shown in the attached backtrace. I've made sure my filesystem is clean with fsck and even turned off write caching on my IDE drive. Maybe someone here can figure out what is wrong. Let me know if you need more information. Michael -------------- next part -------------- root@taco /usr/src/sys/compile/ZOE> gdb -k -c /opt/savecore/vmcore.0

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 #