similar to: Same Box, Moved install to different drive, now get Connection failure: Connection refused??

Arjen, all, Just dropping a note on two points. First, Voltages are perfect in 2.4.1 for the Cyberpower ups's. Glad to see I'm not pushing 20+ any more: http://www.3111skyline.com/nut/ Second, even though the changes to where the monitor lines go in the configs and changes from ACCEPT, etc.. to LISTEN are fairly old now, the documentation for setting up monitoring for multiple UPSs

(Arjen - I apologize if you get two copies, I sent the first one to the old de-korte.org address) Arjen, all, I've run into a usbhid-ups problem with nut on Arch Linux with the new 2.6.35 kernels. (latest is 2.6.35.4-1) For some reason when you get to the udev events on boot and it tries to load the usbhid-ups driver, it hangs until the 120 sec timeout occurs and then boot continues but

Thanks for the quick response! On Sat, Jun 27, 2020, at 22:17, Manuel Wolfshant wrote: > On 6/28/20 4:25 AM, Scott Colby wrote: > > Hello, > > > > I am having difficulty using NUT to shut down my Netgate SG-1100 > > (a pfSense router) when the power level of the UPS gets critically > > low. > > > > Here is some relevant information: > > - OS:

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,

This is new install on Ubuntu 16.04, using packages from Synaptic, *Network UPS Tools upsd 2.7.2 I am getting these messages in the terminal: Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): UPS CyberUPS1 at localhost is unavailable I am still unclear on where to set when nut shutdowns system. I see nut-client and nut server are automatically starting from SystemD.

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

On 6/28/20 4:25 AM, Scott Colby wrote: > Hello, > > I am having difficulty using NUT to shut down my Netgate SG-1100 > (a pfSense router) when the power level of the UPS gets critically > low. > > Here is some relevant information: > - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) > - NUT version: 2.7.4 > - Installed from: pfSense package 2.7.4_7 > - UPS:

On 10/01/2015 00:45, Charles Lepple wrote: > On Jan 8, 2015, at 11:43 PM, Graham Menhennitt > <graham at menhennitt.com.au <mailto:graham at menhennitt.com.au>> wrote: > >> Hello Nutters, >> >> I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) >> with an APC Back-UPS CS 350 connected via USB. I get persistent >> (every few

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?

Thanks again for your patience. I'm still learning how to deal with systemctl myself (and starting from, I'm sure, a much lower level of understanding), so if I've neglected to restart or start something, please let me know. I made the change to /etc/nut/upsd.conf. I restarted upsdrvctl, which reported back: Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic

I'm testing a Powercom UPS (branded as Control System 2 STD80S: http://www.cs2.it/home.php?goto=prodotti&cat=0&idp=2&subid=0) with NUT. It is a USB HID device, with ID 0d9f:0004. I configured nut-server to use driver usbhid-ups and it works almost correctly: upsd communicates right with the device, upsmon catches its events... But when I try to perform a Forced Shutdown, UPS pauses

My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. I have tried using a different USB port and using a brand new USB cable. I have not had success by changing config parameters like pollfreq/pollinterval/etc. What is causing the UPS to keep disconnecting?

Hi UPS List members, I have purchased a number of Emerson Power / Liebert GXT4 UPS units. I have these working correctly under nut, but limited detsils are being reported. I am happy to supply information on the USB communications to improve the reported details I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPS Please advise the best way I can

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

Thanks for the reply. However these two FAQ are unfortunately not describing the situation. - The first issue is that NUT switches off the UPS upon reboot on low battery (not that it dies because of low battery) - The second issue is that the UPS does not recognise being online again (not that the PC does not restart) Sent from my iPhone > On 11 Jun 2019, at 02:03, Charles Lepple <clepple

Hello, I have been using NUT for a short period of time and have some questions regarding the UPS reboot signal that I can't figure out. Have tried some googling and reading the DOCs but I am struggling to understand how some variables / things are supposed to work, so would appreciate any help with any of the following questions. I am running NUT on standalone mode on a linux machine

Hello. Not listed as supported, so here is some info, [root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.001318 upsdrv_initups... 0.074753 Checking device (0529/0001) (003/002) 0.074835 Failed to open device, skipping. (Permission denied)

To all, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas