similar to: New Mac OS X UPS monitoring driver

Hi all, Thought I'd forward this on, as the apcsmart driver doesn't appear to have any support for this (admittedly obscure) setting and it doesn't seem to be listed at http://www.networkupstools.org/protocols/apcsmart.html. Hope someone finds it useful. Later, Russ -- Russell Odom http://www.gloomytrousers.co.uk/ Fast, cheap, good: pick two. -------- Original Message --------

> The Buildbot has detected a new failure of Ubuntu-lucid-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-lucid-x86/builds/78 If I understand this correctly, there are multiple copies of some of the man page names in the automake variables: /usr/bin/install -c -m 644 ../../../docs/man/nut.conf.5

I've been working on a meta-driver that tries to address one of the difficulties of using NUT on a Mac OS X system which has built-in drivers for several USB-connected UPSes. On a stock OS X system, after you plug in a system-supported UPS, a new "UPS" tab shows up in the "Energy Saver" system preferences panel. Basic status information is presented there, and

Is there any way to "automate" kerberos authentication on Mac OS X? Here's the problem: When a user wants to access samba-3.0.2a -server from a Mac, he/she has to run "kinit" to get the principal ticket. If this is not done, Mac's tools (Finder) will try to authenticate with NTLM, which is and will be disabled on our servers. Of course, this fails miserably. I

Hi, [ There is also a github issue about this here: https://github.com/networkupstools/nut/issues/2347 ] I have an APC Back-UPS BX1600MI purchased in January, attached by its supplied USB cable to a Debian 10 machine. Initially using the nut packaged in Debian 10 (2.7.4-8) this was unusable as the usbhid-ups driver kept disconnecting every few seconds. I upgraded to the git HEAD of nut and

> The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/39 Looks like the nutscan-snmp.h file has not been checked into the branch: make[3]: Entering directory `/var/lib/buildbot/buildbot-slave-cayenne/

Arnaud, I was finally able to get back to this issue and would recommend adding these items to the FAQ #37 about recalibrating the UPS: 1a. It's important that the UPS be at 100% charge before starting the procedure; starting at lower will not work at all, not just produce inaccurate numbers. ? ? ? [I started the procedure when the UPS was at 91% charge. After that it would never report

> > The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/32 > > Buildbot URL: http://buildbot.networkupstools.org/public/nut/ > > Buildslave for this Build: cayenne Fred, I had a few spare cycles and tried building

Michal, I ran across this Debian bug today: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223 It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04), but I was wondering if it was still applicable for the latest code? "nut reports 100% battery charge after unplugging the battery on a Smart-UPS 2200 RM (SUA2200RMI2U) using apcsmart. Powerchute correctly

Dear Nick, thanks for writing. I no longer work on development of UPS drivers; you will probably get a more up-to-date answer from the nut-upsuser mailing list (cc'd). I don't know if the Back-UPS 550 has similar commands to the Back-UPS ES 650. If it has a USB connection, then the answer is probably yes. The UPS will automatically turn itself back on after a power failure; this is the

OK. I'll try it, but it really puzzles me how the battery could have gone bad for just 15 months. The online power is pretty stable, so the battery hasn't gone through many charge/discharge cycles... Regards, -- Georgi On 11.1.2020 at 14:24, Manuel Wolfshant wrote: > > indicates that the UPS thought that battery was close to depleted and decided to shutdown. I suggest to fully

I got my USB ups reporting on macOS, but it was quite a while ago, I’ll have to dig into how I did it.. I do remember is wasn’t simple.. ( actually is was long drawn out pain in the …. ) Maybe search for posts from me, I’ll check what I did on the weekend and get back to you.. Or, buy an APC.. as they will just appear in Energy Saver.. > On 6 Jun 2018, at 15:41, Charles Lepple

Hi all, First of all, I would like to thank everyone who was involved in the development of NUT. Although it took me some time to set it up, now it appears to be working very well. Thanks for the good software! This is my success report for an APC Back-UPS RS 800: khali at mahadeva:~> upsc rs800 battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25

Folks, I've asked this question on the FreeNAS forum but there are no ideas there as it looks like it's a NUT issue. Original question: https://forums.freenas.org/index.php?threads/apc-ups-reporting-wrong-input-voltage.60888/ the nut driver is reporting the wrong input voltage. I am in the UK, 230V but it's reporting circa 108. If I connect it to the laptop and run powerchute it

Hi all, In light of issue #2666 ( https://github.com/networkupstools/nut/issues/2666#issue-2623441838), I "sniffed" USB traffic from APC's `PowerChute Serial Shutdown` software (with the help of this guide (https://www.youtube.com/watch?v=0MC-D_oNzbk)). I hope to be able to find out the shutdown command for my APC "Back-UPS BX750MI FW:295202G -302202G". APC's

OK, my UPS turned out to be older that I thought. I apparently bought and installed it in September 2016 (not 2017 as I initially wrote). That makes for over 3 years of work, which is over the life expectancy of the batteries, so I ordered new battery pack. However, how could I make a full charge/discharge test? Should I disable SHUTDOWNCMD in upsmon.conf? Or is there any other way to ignore

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

OK, so yesterday evening I done a real test cutting of the power to the UPS. And it went good... the UPS supported my server for 28:50 minutes (i.e. the expected runtime with this load), before forcing shutdown. The batteries could still hold as charge was 30 % with about 15 minutes run time. And the UPS did hold for another full 10 minutes before powering off. These are the relevant lines

>> 7. No they didn?t restart. I know there is a setting on the NAS to activate this. I will check and try again. > > Not sure for the NAS, but for the Mac, it is probably something like this: > > sudo pmset -a autorestart 1 > > There is also usually a checkbox in the Energy Saver panel in the System Preferences GUI. Under System Preferences, Energy Saver, there is a

On January 11, 2020 1:18:27 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote: >Hello, > >I'm experiencing a strange early shutdown behavior with the following >system: > > * */OS/*: Slackware Linux 14.2 x86_64 > * */NUT/*: 2.7.4 (from my own package > <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) > * */UPS/*: MGE