similar to: Thank you

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

I could not make the bestfortress driver 0.02 work for my Best Fortress LI675VA, so I have made a patch for the driver. The reason was, that all responses are preceded and terminated by CR LF, but the driver would discard everything after the first CR LF. The following patch discards everything up to the first LF. It also adds a debugging feature of displaying the accepted data (level 5 i.e. -D

I noticed that many configuration options (configure.txt) have environment variable overrides. However, an important one does not. In the configuration.txt file, there is one section: Directories used by NUT at run-time ----------------------------------- --with-pidpath=PATH Changes the directory where pid files are stored. By default this is /var/run. Certain programs like upsmon will

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

On Mon, 12 Sep 2016, Jonah Naylor wrote: > I have two linux servers both with static IPs not using NAT. This is rather ambiguous. I'm going to guess that you mean they have public IANA issued IPs that you are trying to use for nut. > My slave can't connect to my host. Whatever I try. That would be a sensible default for public IPs. > I have the same setup also on my LAN with

On Mon, 12 Sep 2016, Tim Dawson wrote: > Or just set up sane firewall rules to allow the two to talk, but block > external traffic. I have run this way for years - all add'rs ar IANA in a > subnet block, and just that block is open locally, and all other external > IP's severely restricted, and NUT works great . . . Yeah, but IANA ips are easy to spoof. With cjdns, you allow

Huh, must be an OpenDNS issue, it works from my phone. I wonder if I'm running into a similar defect on the PC UPS... I could try resetting the driver every few hours (this, in addition to replugging the cable fixes the issue temporarily), but that does feel like a hack that doesn't fix the root cause. I will try returning the unit and give APC a go. I've previously had good luck

On Mon, 10 Oct 2016, Lane Russell wrote: > I tried viewing your link, but it returns a 404 error. It also doesn't seem > to have a valid certificate. Could you send the correct link please? I tried from Texas, Miami, Virginia, and New York VPSes. Works fine. Maybe try again, or check your local DNS? > I was able to get it to run unattended with this hack: >

On Fri, 9 Dec 2016, Stuart D. Gathman wrote: > Hello fellow victim of Tripplite braindead USB! There is a solution! > > On Thu, 8 Dec 2016, dwilliss at inebraska.com wrote: > >> ??????????????? service nut-server stop >> ??????????????? service nut-server start >> >> Then everything is fine again for a while. I jumped the gun. Mine did not reset so

On Tue, 1 Jan 2019, Stuart D. Gathman wrote: > Our server has 2 UPS on 2 PSUs.  At 8am, someone unplugged one UPS.  At > 8:10, they plugged it back in, but turned off the load - presumably to stop > the beeping.   > So the system is still up on 1 PSU, and can talk to both UPS.  Can't I turn > on the load via USB? None of the supported commands seem to do the job. # upscmd -l

On Sat, 16 Feb 2019, James wrote: > These changed: > battery.runtime: > ups.load: > > Is the battery dead again? > Do I need a new UPS? Compare the upsc output with the screen/led display on the UPS. If they are in agreement, then there is no problem with NUT. Your issue is with the UPS or the battery. Aftermarket batteries can be .. substandard. We bought one in 2018 that

On Sat, 16 Feb 2019, James wrote: > Now it says: > battery.runtime: 1170 > The display on the UPS fluctuates between 16-19 minutes. > > ups.load says 30 constantly and The display on the UPS says 30% so I think > that is correct. battery.runtime is in seconds, so that agrees with the UPS display as well. > How you find out your battery was manufactured in 2012? APC

On Mon, 6 May 2019, Gareth Davies wrote: > Just another thing I wanted to mention... once I've resolved the > aforementioned issues, would it be possible for the system to run without > any maintenance or checking up on it? What I mean is, once I've plugged it > into my grandmother's house, I'd like to leave it running and forget about > it basically - in the

On Tue, 7 May 2019, Gene Heskett wrote: > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No such > file or directory Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs filesystem. Thus, any subdirectories must be created afresh each boot. The packager for nut may have neglected this. Try creating the /var/run/nut directory, make it writable but nut.

Hello fellow victim of Tripplite braindead USB! There is a solution! My blog on diagnosing the problem: https://gathman.org/2016/07/30/Standard_Schmandard/ My blog on packaging the solution: https://gathman.org/2016/11/09/Packaging/ Solution on github: https://github.com/sdgathman/trippfix Sadly, you will have to buy a USB standard conforming powered hub to make the Tripplite work. These are

The if() statement always evaluated to true. Detected by "cppcheck", not tested on real hardware. Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/rhino.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/rhino.c b/drivers/rhino.c index ca66169..e478bcb 100644 --- a/drivers/rhino.c +++ b/drivers/rhino.c @@ -187,7 +187,7

Or just set up sane firewall rules to allow the two to talk, but block external traffic. I have run this way for years - all add'rs ar IANA in a subnet block, and just that block is open locally, and all other external IP's severely restricted, and NUT works great . . . - Tim On September 12, 2016 11:47:28 AM CDT, "Stuart D. Gathman" <stuart at gathman.org> wrote: >On

Cheers, I don't think there is any particular strategy, at least not one I'd know of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers reasonably quiet, and sufficient info to see the logic progression at a given debug level (e.g. if major milestones of a routine are logged at level N, further traces like "I saw value X here" would be N+1 or more). De-facto

I am looking at bestfortress and trying to figure out and fix some things, which is causing me to try to improve logging first. A few questions: 0) The developer guide doesn't seem to address any of this, or did I miss it? 1) It seems upsdebugx prints to stdout instead of syslog if in foreground. That's great but I didn't figure it out from docs. 2) I didn't find a plan for

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index: