similar to: upslog patch

oops, this wasn't supposed to make it into the trunk yet. I can revert it until further testing, but has anyone else tried running with this patch? http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-April/003821.html On Mon, May 4, 2009 at 10:05 PM, Charles Lepple <clepple-guest at alioth.debian.org> wrote: > Author: clepple-guest > Date: Tue May 5 02:05:09 2009 > New

On 11/8/2014 6:54 AM, thomas schorpp wrote: > Dear Ted, > > Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: >> On 11/3/2014 9:25 PM, thomas schorpp wrote: >>> Hi Ted, >>> >>> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>>> >>> >>>> Note that since the UPS relies on the voltage from the battery pack to

Hi Ted, Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: > > Note that since the UPS relies on the voltage from the battery pack to > determine state of charge, it is quite useful to add in the battery pack > voltage to the logs as such: > > --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 > +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 > @@ -50,6 +50,7

Hi Thanks for a very nice piece of software. I have a tiny suggestion for upslog.c. It adds a signal handler for the USR1 signal, which simply triggers it to abort the current sleep and log the requested now. I find it useful because my upssched-cmd can then killall -USR1 upslog to ensure that there is an entry in the log for brief power dropouts which would otherwise be unrecorded (because

Dear Ted, Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: > On 11/3/2014 9:25 PM, thomas schorpp wrote: >> Hi Ted, >> >> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>> >> >>> Note that since the UPS relies on the voltage from the battery pack to >>> determine state of charge, it is quite useful to add in the battery pack >>>

On 11/3/2014 9:25 PM, thomas schorpp wrote: > Hi Ted, > > Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >> > >> Note that since the UPS relies on the voltage from the battery pack to >> determine state of charge, it is quite useful to add in the battery pack >> voltage to the logs as such: >> >> --- upslog.c.orig 2012-07-31 10:38:58.000000000

Hi, Trying to rotate the ups.log on a FreeBSD 7.0 system and its not being nice about it. I tried the "quick and dirty" way by doing : mv /var/log/ups.log ${DATEDDIRECTORY}/ups.log kill -1 `cat /var/db/nut/upslog.pid` I get : Sep 17 10:57:20 valhalla upslog[81972]: could not reopen logfile /var/log/ups.log: Permission denied So I stop upslog, remove the file, and start it

On Aug 13, 2015, at 12:45 PM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 > NUT is apparently 2.4.1 > It was installed by tar. > > Monitoring a lot of apc UPS units?mostly Smart-UPS of various flavors, also a Silcon DP380E. > > Normally works just fine? ?upslog? writes status log every 30 seconds with

Hi Charles, On 10/12/14 14:27, Charles Lepple wrote: > Hi Andy, > > On Dec 8, 2014, at 7:07 PM, Andy Juniper <ajuniper at freeuk.com> wrote: > >> It adds a signal handler for the USR1 signal, which simply triggers it to abort the current sleep and log the requested now. > I will admit that I'm not an expert on how signals interrupt system calls on all systems, but

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

[please keep the list CC'd, thanks] > On Aug 14, 2015, at 10:27 AM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Would it put NA in the log files if maxage was too short? I think so. I haven't tried it, but if snmp-ups polls every 30 seconds, and MAXAGE is 15, then with a random polling interval, 50% of the time the data would be more than 15 seconds old. In

Hi Andy, On Dec 8, 2014, at 7:07 PM, Andy Juniper <ajuniper at freeuk.com> wrote: > It adds a signal handler for the USR1 signal, which simply triggers it to abort the current sleep and log the requested now. I will admit that I'm not an expert on how signals interrupt system calls on all systems, but for what it's worth, the code looks good to me. Is it correct to assume that

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack

Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 NUT is apparently 2.4.1 It was installed by tar. Monitoring a lot of apc UPS units-mostly Smart-UPS of various flavors, also a Silcon DP380E. Normally works just fine... "upslog" writes status log every 30 seconds with various parameters.. Every so often, one of the UPS units has a log entry of:

On Wed, Oct 1, 2008 at 7:30 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> Definitely seems like a permissions problem. >> >> It's been a while since I messed with USB on FreeBSD. What do the >> permissions look like on /dev/ugen*? What modifications did you make >> to /etc/devfs.rules? > > Thanks a lot Charles! I think I managed to get NUT

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

Thanks for your help! In red below. Cheers simone On Thu, Jun 4, 2015 at 2:45 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 3, 2015, at 11:45 AM, Simone Severini <severini.simone at gmail.com> > wrote: > > Hi everybody! > It has been a journey but I almost manage to make my UPS properly > communicate. > > This is the config: > > UPS

Hello, My entry for newsyslog in /etc/crontab is: 0 * * * * root newsyslog -t \%Y-\%m-\%d_\%H:\%M And I get: newsyslog: Could not convert time string to time value: No such file or directory I try to use the newsyslog from head to to avail. This solution was working a month ago (see Revision 248776) My file system is zfs version 28. Henri

I finally got around to writing myself a NUT UPS monitoring tool. NUT's UPS monitoring CGI tools provide a detailed instantaneous view of the UPS's state at any moment, but provide no history. The attached tool, upswatch, uses Kiss Gabor's UPS::Nut module and Tobi Oetiker's rrdtool to provide a graphical history of the major UPS operating parameters via a web browser.