similar to: Logging using upslog problem

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

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

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

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:

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

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 differentiate them easily. -- Daniel

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

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

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

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

[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

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

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

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

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

All, I just bought a Belkin F6C1100-UNV and am trying to get it to work with NUT. I have tried many drivers ( "belkin", "belkinunv", "genericups upstype=4", and "genericups upstype=7", "bestups", "fentonups"). None of them seem to work. Does anyone have any experience with this device? If there is some utility that you all use to

Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>: > Discharged battery.voltage: > > 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%) > 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%) > 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%) > > -- Shutdown Occurred at < 3% -- Battery

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable

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