search for: upslog

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 to get a clean/fresh file. It shows me : -rw-r--r-- 1 root wheel 36 Sep 17 10:59 /var/log/ups.log So I change my script to...

Hi, I have a system which monitors 2 UPSs, and it runs upslog twice. I had a problem with newsyslog rotating the log file because upslog keeps it open (arguably a bug IMO), but it also has no way of changing the PID file so newsyslog can't HUP it when log rotating. Attached is a patch which allows you to specify the argument for writepid() so you can...

...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 Revision: 1837 > > Log: > upslog patch for PID basename > > Modified: > trunk/clients/upslog.c > > Modified: trunk/clients/upslog.c > ============================================================================== > --- trunk/clients/upslog.c Tue May 5 01:32:47 2009 (r1836) > +++ trunk/clients...

...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 @@ >>> static flist_t *fhead = NULL; >>> >>> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ >&...

...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 @@ >> static flist_t *fhead = NULL; >> >> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ >> + "%VAR bat...

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 u...

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 @@ > static flist_t *fhead = NULL; > > #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ > + &qu...

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: 20150812+035542+NA+NA+NA+[NA]+NA+NA+NA When it normally looks like: 20150813+114309+100.00+115.00+39.00+[OL]+25.00+60.00+1020.00 What does it mean when it puts NA in the...

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...

...g 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 you are using this on Linux? > 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 the power is only off for a few seconds). Agreed, that sounds very useful. I don't think we have a standard format for documenting the signals that the various NUT components resp...

...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 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 @@ static flist_t *fhead = NULL; #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.charge% " \ + "%VAR battery.voltage% %VAR...

...r stale Where else can I look to find out what really happened? -Bob -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: Thursday, August 13, 2015 9:52 PM To: Bob Brown Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] occassional problem wtih upslog and apc ups units via snmp ... [NA] status 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 Sm...

...the sleep which returns with (quoting from the manual page): RETURN VALUE Zero if the requested time has elapsed, or the number of seconds left to sleep, if the call was interrupted by a signal handler. >> 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 the power is only off for a few seconds). > Agreed, that sounds very useful. > > I don't think we have a standard format for documenting the signals that the various NUT co...

...$bcharge, $bvolts, $load, $graphctr, $uid, $gid); set_defaults(); open (LOG, ">>$logfile") unless ($opts{foreground}); select((select(LOG), $| = 1)[0]); (undef,undef,$uid,$gid) = getpwnam($runuser); create_files($uid,$gid); POSIX::setgid($gid) || upslog("Could not set GID!\n"); POSIX::setuid($uid) || upslog("Could not set UID!\n"); create_rrds($rrd_file) unless (-e $rrd_file); $graphctr = create_graphs(); while (1) { $ups = UPS::Nut->new(NAME => $opts{upsname},...

...n 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 various parameters.. > > Every so often, one of the UPS units has a log entry of: > > 20150812+035542+NA+NA+NA+[NA]+NA+NA+NA > > When it normally looks like: > > 20150813+114309+100.00+115.00+39.00+[OL]+25.00+60.00+1020.00 &gt...

...gt;> >>> >>>> 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 @@ >>>> static flist_t *fhead = NULL; >>>> >>>> #define DEFAULT_LOGFORMAT "%TIME @Y at m@d @H at M@S% %VAR battery.ch...

...measured battery voltage under load here and the value the UPS is reporting at the same time. There probably won't be much of a difference for the float (fully charged) voltage, but there will be when it is (almost) empty. Probably the easiest way to measure this, would be to run 'upslog' while at the same time looking at the voltage on your multimeter. You'll need to watch the battery.voltage parameter, which is not in the default set of variables that is monitored by 'upslog'. The following line should report this: upslog -l- -i 10 -f "%TIME @H:@M:@...

...sily kept the servers up and online. > > As far as I can tell, the upscode2 driver does not use the battery > voltage to determine when to shut down - it uses one of the UPS > status bits from the STAT or STMF responses. > Really! I was afraid of that. With this blip, this is what upslog was showing: 20140212 032546 65.9 119.30 60.9 [OL] NA NA 20140212 032626 62.8 119.10 55.5 [FSD OL] NA NA 20140212 043722 NA NA NA [WAIT] NA NA 20140212 044222 67.7 118.90 54.4 [OL] NA NA 20140212 044722 65.9 119.20 52.4 [OL] NA NA The blip obviously took place between 3:25:46 and 3:26:26, I was l...

...houldn't be a problem. > -Bob > > -----Original Message----- > From: Charles Lepple [mailto:clepple at gmail.com] > Sent: Friday, August 14, 2015 8:28 AM > To: Bob Brown > Cc: nut-upsuser at lists.alioth.debian.org > Subject: Re: [Nut-upsuser] occassional problem wtih upslog and apc ups units via snmp ... [NA] status > > On Aug 14, 2015, at 8:53 AM, Bob Brown <bbrown at harpercollege.edu> wrote: >> >> I see this in syslog: >> Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver > > I don't have...

...This VID:PID combination should be handled by blazer_usb. In NUT 2.7.1 and later, this would be covered by nutdrv_qx as well. > I am running all the ups programs as root, i.e. "ps -aux" shows: > > root 39901 0.0 0.0 22388 3860 ?? Is 12:57AM 0:00.00 /usr/local/bin/upslog -s UPSonic at localhost -l /var/log/ups.log -i 300 -u root > root 39976 0.0 0.0 22392 3804 ?? Is 12:57AM 0:00.00 /usr/local/sbin/upsmon -u root localhost > root 39978 0.0 0.0 22392 3900 ?? S 12:57AM 0:00.01 /usr/local/sbin/upsmon -u root localhost The key p...