similar to: NUT on openSUSE 12.3 requires additional systemd service unit

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

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 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/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

Hi, I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT model). I am trying to make this configuration work for automatic shutdown/restart but it seems that it completely ignores /etc/killpower presence. I know the APC SMT models are problematic but it looks like I could not even make the simplest

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

Hi, I have CentOS 7, two node system which allows live VM migration between them. Live migration triggered from virsh is happily happening. I am using GlusterFS for replicating VM disk files. Now I want to automatically do the live migration at the time of reboot/shutdown/halt of the host node and for this I have written a systemd service unit [vPreShutdownHook.service] and placed the live

I've got a fresh CentOS 7 test machine, fully patched. The command: shutdown -h now surprisingly does not halt the machine. Instead it reboots it. WTF? I found the following Debian discussion which seems to be the same issue: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766338> However, removing kexec-tools in this case did not solve the problem. Nor does

On Dec 14, 2013, at 4:19 AM, David C. Rankin wrote: > lsusb shows: > > Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS I am guessing that 'ls -l /dev/bus/usb/004/002' shows that the device node is not owned by the NUT gid? > Why doesn't > "upsdrvctl start" allow nut to find the UPS when it can find it without a > problem with

On Wed Sep 11 10:45:48 PDT 2013 Lennart Poettering wrote: > So, it's a really bad idea to turn off UPS from userspace, simply > because you will race against the kernel's fs sync() code, and you never > know what will finish first: your UPS shutdown timeout or your fs > sync(). Doing this from userspace is hence racy. > If you want to use a hack like this then at least

Hi Charles, On Wednesday, July 13, 2016 11:40:09 PM Charles Lepple wrote: > On Jul 12, 2016, at 5:27 PM, Ivan Adzhubey <iadzhubey at rics.bwh.harvard.edu> > wrote: > > I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 > > LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT > > model). I am trying to make this configuration

also in /etc/sysctl.d/ On Thu, Dec 24, 2015 at 8:58 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 12/23/2015 05:08 AM, Ofer Hasson wrote: > >> By running "systemctl status systemd-sysctl" I also receive the same >> output, but a simple "cat /proc/sys/vm/swappiness" returns the default >> value, and not the one set by my conf file.

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

Hi all, I'm trying to resize a journal on my root filesystem. This is Ext3, kernel 2.4.19, latest e2fsprogs + htree patch. I've remounted my root filesystem as ext2, but still when I 'tune2fs -O ^has_journal' I get ---- The has_journal flag may only be cleared when the filesystem is unmounted or mounted read-only. ---- So, how can I increase the size of the journal? I

Ok, I did read www.freedesktop.org/software/systemd/man/systemd.unit.html and am still confused. What is it? If it helps, let' suse a real application: I create in /etc/systemd/system/ the home-ducker.{,auto}mount files. Where does this unit file go with respect to them? Is it one of them?

Hi 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? I saw: ups.delay.shutdown: 20 ups.delay.start: 30 is it something related? thanks min On Sat, May 7, 2016 at 3:44 PM, Roger Price <roger at rogerprice.org> wrote: > On Sat, 7 May 2016, Min Wang wrote: > > Hi

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. 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?

Hello, I'm using Archlinux x86_64 with linux-nouveau kernel (based on linux-mainline (that is linux-3.6)). I've installed nut-2.6.5. I first tried to use new systemctl .service scripts, but they are problematic. So I start and stop nut from /etc/rc.c script. This way, it "woks". Here are my config files : nut.conf : MODE=netserver ups.conf : [ellipse] driver = usbhid-ups

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