similar to: Added -f command line option to upsmon

>> Over the last couple months, we have had a couple incidents (luckily a= ll >> on weekends) where all 15 UPSs will mysteriously shut off, and we had = to >> manually power them back up. To top it off, there was nothing in syslo= g >> about any UPS going onto battery power and staying there - just a coup= le >> curious low-battery warnings from one of the UPSs. You

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not

charge, but instead will be raised a few seconds before the power will be cut by the UPS, either because of a low battery event or a user initiated shutdown (with delay) command. The thing I don't like about that, is that by that time the shutdown sequence has apparently already started by the UPS, which means that we have no control over when the power will be cut. Also, if it indeed only

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

Since reports received over the interrupt pipeline are a recurring problem for various types of UPS'es, I propose to simply ignore the data we receive there and only flush the respective report buffer. By doing so, at the time the interrupt reports are processed the first variable that is retreived will trigger a poll for the corresponding feature report and we should be fine. The impact on

Folks, I think the present megatec_usb.c deserves to be renamed to serial_usb.c. I think it potentially could serve many more UPS'es with built-in USB-to-serial converters, not limited to the megatec_usb driver (although that was the first one to use this). I also think a more layered approach would be nice, in the same fashion as the usbhid-ups driver with subdrivers. Which would mean that

Reporting current in milliAmps is not a good idea. This will lead to impractically large values, especially when we report them with two decimals resolution (10 microAmps). Even the laboratory measuring equipment that is standing right next to me now, doesn't offer this resolution in the range that is common for most UPS'es. I think you meant to write 'Ampere (A)' here

Hello, I'll be back with my MGE Evolution 2200 connected with RS232 I upgrade nut 2.0.1 in nut 2.2 + psp as you ask me PSP autodetect my UPS and autoconfigure NUT. not really diffcult ! So I didn't change anything but I always have in my syslog these event Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale Nov 13 11:09:27 mezenc upsmon[3865]: Poll

I'll be back one more time perhaps I found the reason of these errors Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale it happens when daemon upsd et upsmon are started after the boot obviously, there isn't any errors when upsd and upsmon are started at boot following later ... -----Message d'origine----- De : goudard sabine Envoy? : mardi

Hello, I installed NUT and configured it for 2 MGE UPS's connected via USB. Debian etch NUT package: # dpkg -l nut*|grep ^ii ii nut 2.0.4-3 The core system of the nut - Network UPS Tools ii nut-usb 2.0.4-4 USB Drivers subsystem for the nut - Network UP Separately, with only one UPS defined in ups.conf, each one works fine (I specified specific serial numbers for either, with

On 9/16/08 3:35 PM, "Arjen de Korte" <nut+users at de-korte.org> wrote: > Citeren tarbeite <tarbeite at fit.edu>: > >> Running opensuse 11 with two ups that can be seen via web interface and post >> messages on the console. > > Please post the contents of /etc/ups/upssched.conf here. Also make > sure that the directory mentioned in PIPEFN and

I wrote: > The Solution: Make LLVM usable as a DLL or SLL in Windoze, > capable of generating a finished ready-to-execute .EXE or > .DLL file, without requiring that MinGW or Cygwin be > installed first. Michael T. Richter replied: > You will be welcomed with open arms by the LLVM community > when you write this. I look forward to your announcement > with bated breath.

(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

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

But /etc/nut/upsmon.conf has the correct username and password. returns: gene at coyote:/usr/share/doc/nut-doc/pdf$ upsmon myups at localhost Network UPS Tools upsmon 2.6.4 kill: Operation not permitted /etc/nut/upsmon.conf line 75: invalid directive [*****] /etc/nut/upsmon.conf line 76: invalid directive password = ************** /etc/nut/upsmon.conf line 77: invalid directive upsmon master UPS:

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

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

If you don't use 'CERTVERIFY 1', then this will at least make sure that nobody can sniff your sessions without a large effort (...) > So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? >> Can you reproduce such behaviour ? >> > > I'm not sure what is going on. Can you try running 'upsmon' with debugging > enabled? The following are

Hi; I have ran into an issue with the upsmon tool leaking memory over a two month period. It seems to be due to one of my UPS hosts offline. System is a debian stable with the default nut package. Here's the data so far: companyfs1:/var/log# ps aux | grep [n]ut nut 2439 0.0 3.6 380800 18800 ? S Jun05 6:41 /sbin/upsmon >From my logfiles its failing on one of my UPS

On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: > I don’t have the code in front of me at the moment, but my guess is that the > config parser stopped parsing at the “#” character. I suspected a rogue character was being interpreted and used `backticks`, 'single quotes' and then "double quotes", but all failed. I ended up removing the offending #