search for: networkupstoolsnutandsystemd

...00 USBS. 9 seconds after server poweroff, the UPS powers off. When wall power returns the server restarts correctly. I still haven't messed with systemd yet, so I am in over my head here. Is this similar to what Kjell posted about? Or is it in addition to that? http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/ -- Charles Lepple clepple at gmail

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

Hi all, I was converting my gentoo box to systemd, and hit this 'HOWTO' on a blog. http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/ realy helpt me out starting my usb-ups. Made som tweeks as I'm not running a APC and have the pid file in another location. But it is well explained. Regards Kjell Claesson

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

...ile NUT relies on this script to run /etc/init.d/ups-monitor command which, in turn, checks for the presence of killpower flag and run "nut-server poweroff" command to cut the UPS load power, if that flag is found. I followed the instructions on this blog: https://www.kepstin.ca/blog/networkupstoolsnutandsystemd/ by creating the file /lib/systemd/system-shutdown/nutshutdown with the following commands in it: #!/bin/sh /sbin/upsmon -K >/dev/null 2>&1 && /sbin/upsdrvctl shutdown After that, NUT server would correctly process power loss events (both real and simulated) by cutting UPS po...

...while > tracking down permissions issues. Hopefully we can figure out the underlying > permissions issue, and we can table that question. > <snip> I found another really good article that describes writing the udev files to fix these issues. The url is: http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/ I will test with the new ubs dev permission and report back. Thank you for your help Charles. -- David C. Rankin, J.D.,P.E.

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

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