similar to: Smart1500LCD USB and usbhid-ups

nothing appens. The output is exactly the same as below (attached screen with freenas config) [image: Immagine in linea 2] 2014-04-03 13:16 GMT+02:00 Charles Lepple <clepple at gmail.com>: > please reply to the list. thanks! > > See below. > > On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > > thanks for your reply.* I'm running the latest version of

Nice! it seems to works. Later this evening when I'll be back to my home I'll try to unplug the power chord from my ups. Apr 3 14:08:11 archivio notifier: nut not running? (check > /var/db/nut/upsd.pid). > Apr 3 14:08:11 archivio notifier: nut_upsmon not running? (check > /var/db/nut/upsmon.pid). > Apr 3 14:08:11 archivio notifier: nut_upslog not running? (check >

please reply to the list. thanks! See below. On Apr 3, 2014, at 3:10 AM, Daniele Borghesi wrote: > thanks for your reply. I'm running the latest version of FreeNAS based on 9.2 with NUT 2.7.1 > > [root at archivio ~]# uname -a > FreeBSD archivio.dannyb78.home 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+ > 38751c8: Thu

Hello, I need help configuring my USB connected UPS "Emerson Power Liebert PowerSure PSI 1440" to my freebsd machine, using NUT. here's the manufacturer's product page http://www.emersonnetworkpower.com/en-US/Products/ACPower/Pages/LiebertPowerSurePSILineInteractiveUPS10003000VA.aspx I'm not a BSD expert, so please ask me for any information you need. regards Daniele

On Apr 3, 2014, at 7:24 AM, Daniele Borghesi wrote: > nothing appens. The output is exactly the same as below (attached screen with freenas config) > What happens without the leading "-x"? (just "productid=0004") The "-x" is what you would add if you were running the driver from the command line. -- Charles Lepple clepple at gmail

On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have to stop and restart NUT, that is a different story. What

I am running NUT as part of FreeNAS 9.2.0. I have looked through the manuals, but I don't see how to address my issue. The box has 4 NIC's in a LACP LAGG group. It takes a while for LACP to finish, and NUT tries to start before packets are flowing. NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS. If I stop NUT and restart

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be.

Hello all, I've got an MGE Pulsar Ellipse Premium 800 powering a couple of FreeBSD systems. Driver used is mge-shut, I don't know what the new mge-shut driver offers, but I follow the "if it works, don't fix it" dogma here. :) I also had a nut server installed on the master, with the /usr/local/etc/rc.d/nut script slightly modified to include a couple of upsrw commands

On Dec 8, 2019, at 5:46 PM, Layne Fowler <layne.fowler at gmail.com> wrote: > > 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

Charles, thank you for that link to David's earlier message. I tried adding those udev rules and changing the pollinterval. I need to do some tinkering but I don't think the part RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl start" is working right. If I manually run the commands then the USB disconnects stop and there are no kernel messages. Running "sudo /lib/nut/usbhid-ups

[when responding, please use reply-all - the list does not mangle the reply-to header] > On Aug 21, 2017, at 12:45 AM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120 TrippLiteUPS at localhost" and confirmed the value with "upsc TrippLiteUPS at localhost" Still the UPS

Layne Fowler writes: > On Mon, Dec 9, 2019 at 12:58 AM Marco Walther > <<URL:mailto:marco at sonic.net>marco at sonic.net> wrote: > > Lite information I can help with, let me know. > > We had that discussion about the SMART1500LCDT  & USB a long time ago:-( I Ditto. > bought mine in 2013 (still going strong on the second set of batteries) >

Hi, Layne. I had a similar problem with my Tripp-Lite BCPERS450. You can see the previous correspondence by searching for site:alioth-lists.debian.net/pipermail/nut-upsuser BCPERS450 shutdown with Google. In particular, I fixed (well, worked around) the problem, as I wrote in https://alioth-lists.debian.net/pipermail/nut-upsuser/2018-March/011082.html I've been running with this code for

From: Layne Fowler <layne.fowler at gmail.com> Date: Fri, 3 Jan 2020 16:22:10 -0500 I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? I didn't, because I don't use that functionality, though it does look as though it should be modified in just the same way. This might

Hi, Layne. Glad my changes helped. It's not surprising that there are some remaining race conditions. I'm afraid I can't remember whether I have this particular problem or not. My variable settings shown by upsc are below. I think the general plan should be to run the system on the UPS for as long as possible, then shut it down with the shortest delay possible that still allows for

Hi, David. Thanks for the offer of help. I have BCPERS450 serial number 2701DVHBC809300177. Unfortunately I'm about to go on a trip and will be away until the end of the month, so I don't have much time to discuss these things at the moment, but maybe Layne will have something to say. My understanding from when I was working on this a couple years ago is that the main problem in

On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp > Lite information I can help with, let me know. > We had that discussion about the SMART1500LCDT  & USB a long time ago:-( I bought mine in 2013 (still going strong on the second set of batteries) and in August 2016 we had some discussions about the USB

On Aug 21, 2017, at 1:35 PM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I ran it again on battery and upsd running, set upsrw ok and then shutdown.return gave an "ERR CMD-NOT-SUPPORTED" Odd thing is after running that I am getting random timed ups powering off for one or two seconds then turns back on even on battery. Server then starts shutting down. Some