similar to: APC Back-UPS XS1300 battery behaviour on test shutdown

Ok, so just a follow-up to my last email; still following that guide, which is great…. Just stuck on getting the nut-server service starting automatically.  Got everything else working.  I’ve been able to get the nut-client starting up automatically at boot up (I had a missing “1” in upsmon.conf.  Oooops!)  However, I cannot get nut-server service to start-up automatically still. proton at

For directory permissions, the "x" priv determines if you can access the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---) pretty much locks out access to the dir. Myself, I'd go back to 555. 640 essentially locks the group "nut" out . . . - Tim On August 11, 2020 11:11:22 PM CDT, Todd Benivegna <todd at benivegna.com> wrote: >Ok, so just a

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

Sorry, I forgot this: torsten at raspberrypi:/ $ sudo /lib/nut/usbhid-ups -a UPS -x vendorid=051d -DD Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.004718 upsdrv_initups... 0.007534 Checking device (051D/0002) (001/004) 0.008910 - VendorID: 051d 0.010030 - ProductID: 0002 0.011196

Dear list, since some days I own an APC Back-UPS BX1400U. Now I try to connect my Raspberry Pi to it using NUT, but ... ;) The UPS is connected via an USB-cable, and "lsusb" shows an APC device. NUT is installed via "sudo apt-get install nut". My goal: a Synology DiskStation DS1515+ should "read" UPS-data provided from the Raspberry an shut-down itselt at 30%

Thanks Manuel.  I’m following that guide but am now stuck when checking to make sure the nut-sever and nut-client are up and working.  I got this: proton at proton:~$ service nut-server status nut-server.service - Network UPS Tools - power devices information server      Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)      Active: failed (Result:

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

Hi, I'm setting up NUT on a raspberry pi 4, following the guide here: https://melgrubb.com/2016/12/11/rphs-v2-ups/ OS version: Raspian Buster NUT version: 2.7.4.8 Installed via: apt package install Device: Legrand Keor Multiplug connected via USB The problem I am experiencing is that *NOTIFYCMD* never runs. I can connect to the device via *upsc*, and I receive WALL messages when I connect

>I just went through the same issue. Take a look at my thread. >Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. Thanks for the response, can you link to it? I'm not finding it in the search. I'm not using /sbin/upssched, I have NOTIFYCMD set up as: NOTIFYCMD /home/pi/Documents/scripts/ups-log.py and it's not commented out. On Tue, Feb 11, 2020

I just went through the same issue. Take a look at my thread. Double check that upsmon.conf:NOTIFYCMD /sbin/upssched is not still commented. On Tue, Feb 11, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe via the World Wide

> When you run that command, does "some text" appear in the system log? When I run Documents/scripts/ups-log.py manually I do see the expected text echo'ed to the command line. It actually appends to a Google Sheet, not the internal log files. When I would expect to see it triggered by NOTIFYCMD, I don't see any text printed and nothing shows up at the google sheets. If

Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:

On May 2, 2019, at 4:08 PM, Mathias Passow wrote: > > Hi, the following UPS isnt supported by the driver „usbhid-ups“. > > Manufacturer: APC > Model: Back-UPS 950 (https://www.apc.com/shop/de/de/products/APC-BACK-UPS-950VA-230V-AVR-Schuko-Sockets/P-BX950U-GR) > > Config: > [USV] > driver = usbhid-ups > port = auto > desc = "USV"

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

On Feb 16, 2016, at 12:57 AM, T. Ermlich <pelegrine at gmail.com> wrote: > > Sorry for the email only send to you, Charles! > Here's the one for the list. I realize it is no longer a common list configuration. Feel free to use "Reply All" in Gmail - I won't get two copies. > torsten at raspberrypi ~ $ uname -a > Linux raspberrypi 4.1.13-v7+ #826 SMP

On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote: > > I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time. > > I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

On May 31, 2016, at 1:11 AM, Tomas Tang <myhnet at gmail.com> wrote: > > Hi All, > > > > I get very strange UPS problem from RspberryPI mode B (both version 2 and 3). > > > > Here is our environment: > > > > OS: Raspbian 8.0, Ubuntu 16.04 and Ubuntu 14.04 > >

Hello Charles, Thank you for all of your help this far. I have made some great progress. I was hung up with all sorts of USB problems which we can chalk up to a "blonde moment" for me (or more accurately, a *bald* moment). In all my starting over and screwing around, I had forgotten to reinstall libusb-compat. Duh! I am now to a point that I think we can dig a little deeper. The

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver