similar to: [systemd-devel] Trying to turn off a UPS with home-made service unit

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

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

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

Hello, I have decided to upgrade my home server by turning it into an ESXi host and have also added an APC CS650 UPS. My plan was to have NUT version 2.6.4 running in a Debian 7.7.0 virtual machine, NUT installed using apt. I configured NUT to run as a netserver, installed the ESXi nut .vib, configured the shutdowncmd in the VM to do nothing, so that the ESXi host would close that virtual machine

On Jan 7, 2015, at 6:11 PM, DatGingerCat <dat.ginger.cat at gmail.com> wrote: > Hello, > > I have decided to upgrade my home server by turning it into an ESXi host and have also added an APC CS650 UPS. > My plan was to have NUT version 2.6.4 running in a Debian 7.7.0 virtual machine, NUT installed using apt. > I configured NUT to run as a netserver, installed the ESXi nut

The serial number looks completely different, but the firmware seems to be the same. Pasting upsc output: battery.charge: 80 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2013/12/04 battery.mfr.date: 2013/12/04 battery.runtime: 1781 battery.runtime.low: 120 battery.temperature: 29.2 battery.type: PbAc battery.voltage: 13.5 battery.voltage.nominal: 12.0 device.mfr: American Power

On Jan 22, 2015, at 9:53 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi Charles, > > Thanks so much for your quick and detailed reply! I've added my answers and details inline. Sorry this reply wasn't as quick. > On 22.1.2015 04:46, Charles Lepple wrote: >> On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote:

On Aug 10, 2013, at 5: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 > >

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

On Mar 13, 2015, at 10:14 AM, Rob Groner <rgroner at RTD.com> wrote: >> >> The documentation isn't explicit about this, but 'upsdrvctl shutdown' is >> meant to be run after all of the other processes on the system have been >> killed, real filesystems have been unmounted, and the kernel shutdown >> syscall is about to be called. Usually the init

while finishing some work on the HAL integration (I'm now mapping DBus method with NUT commands, to allow at least the final UPS poweroff), I was horrified to realize (and so late) the changes in usbhid-ups->upsdrv_shutdown(). We've lost a lot there, but making a generic code, instead of keeping the subdrivers delegation. For example, the shutdown.return command (which is or should be

Hi Roger, Hi all,   > Does upsmon.conf specify a shutdown on LB? I think so. You mean SHUTDOWNCMD? The relevant parts of my upsmon.conf (notifications removed): MONITOR ups at localhost 1 upsmaster secret master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 2 HOSTSYNC 15 DEADTIME 40 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 1800

Hi Charles, Thanks so much for your quick and detailed reply! I've added my answers and details inline. On 22.1.2015 04:46, Charles Lepple wrote: > On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> > wrote: > >> First issue: whatever I set as the offdelay, seems to be ignored and >> the UPS just cuts the power about 2sec after receiving

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). How does this work in conjunction with the UPS hardware? Does NUT immediately send a command to the UPS to wait for 300 seconds and then shut

Welcome, Acctualy, I'm try to poweroff my ESXi (6.7). Virtual machine with Ubuntu and redirected USB port with APC Back UPS CS 650, have nut-server and send info to ESXi. When battery is low, ESXi poweroff gracefully all VM and same ESX go down. This work fine and don't have any problem. But important to me, is set to more offdelay on UPS than the default 60 sec. (cut off power socket

Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower

Nut will monitor the ups and shutdown Linux when the ups goes to low battery as it should. But the UPS is not shut down so the system will restart when the power is restored. If I switch the UPS off , restore power and switch the UPS on the system will restart. I have not been able to get nut to switch the UPS off after it brings the system down. I can get the UPS to switch off with upscmd

The purpose of this posting is to summarize the FreeBSD installation procedure from the beginning till the very end. 1. Follow the instructions provided in the How-To prepared by Thierry Thomas (http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt). Please note the following: a) if you are using an USB device, as of NUT 2.2 usbhid-ups completely replaces the legacy hidups driver and provides

> > How does this work in conjunction with the UPS hardware? Does NUT > > immediately send a command to the UPS to wait for 300 seconds and then > > shut itself down, thereby allowing the server enough time to safely > > shut itself down as well? > > Yes. Very good, thank you. > The command is "upsdrvctl shutdown". That's what I thought, but I