similar to: Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS

On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had any luck getting this to work again. I disabled upd at

On 09/11/14 21:43, Charles Lepple wrote: > On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had

On 09/19/14 07:23, Charles Lepple wrote: > On Sep 19, 2014, at 7:26 AM, Stan Gammons <sg063015 at gmail.com> wrote: > >> --enable-debug-log was in the original makefile. I added --enable-debug. At this point I guess trying to build from source or go back to OpenBSD 5.5 are the only options left. > Ah, my confusion was that --enable-debug-log was wrapped in ".ifdef

On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > Looks like this patch fixed the problem. I see the status change now. Good to hear. I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? -- Charles Lepple clepple at gmail

* Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > Looks like this patch fixed the problem. I see the status change now. > Good to hear. > I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? no, 5.6 is already cut.

On 09/11/14 22:34, Charles Lepple wrote: > On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I see a libusb_get_interrupt message in the log. Could that be the problem? > Yes, it seems related. > > 1.126896 upsdrv_initinfo... > 1.126906 upsdrv_updateinfo... > 1.127023 libusb_get_interrupt: Function not implemented >

On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo...

On Sep 19, 2014 5:55 AM, "Charles Lepple" <clepple at gmail.com> wrote: > > On Sep 18, 2014, at 10:09 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > > > On 09/17/14 22:31, Charles Lepple wrote: > >> Can you rebuild the libusb1 pkg as a port, with the DEBUG flag turned on? > > > > > > Is --enable-debug the way one turns it

On 09/17/14 22:31, Charles Lepple wrote: > On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> On 09/11/14 22:34, Charles Lepple wrote: >>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >>> >>>> I see a libusb_get_interrupt message in the log. Could that be the problem? >>> Yes, it

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is

On Sep 18, 2014, at 10:09 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > On 09/17/14 22:31, Charles Lepple wrote: >> Can you rebuild the libusb1 pkg as a port, with the DEBUG flag turned on? > > > Is --enable-debug the way one turns it on? I modified the Makefile as shown below, then did a make and make install. I am not sure how to tell OpenBSD to use that

On Sep 19, 2014, at 7:26 AM, Stan Gammons <sg063015 at gmail.com> wrote: > --enable-debug-log was in the original makefile. I added --enable-debug. At this point I guess trying to build from source or go back to OpenBSD 5.5 are the only options left. Ah, my confusion was that --enable-debug-log was wrapped in ".ifdef DEBUG", which I suspect is not enabled by default. On the

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I see a libusb_get_interrupt message in the log. Could that be the problem? Yes, it seems related. 1.126896 upsdrv_initinfo... 1.126906 upsdrv_updateinfo... 1.127023 libusb_get_interrupt: Function not implemented 1.127030 Got 0 HID objects... 1.127036 Quick update... Come to think of it, this

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

The nut ups daemons seem to be communicating with the UPS but upscmd gives me no joy. Running commands do nothing and produce no output. Using the web interface returns an authentication failure and that is the only clue I have. I believe I have everything setup correctly but it's not working. Can someone review this and give me clues as to what I should research next?

Hello ! I'm totally new with Linux, just migrating from NetWare. Our brand new server runs SuSE Linux Enterprise Server 11 Service Pack 1 SLED11 ships with NUT 2.2.2-69.11 I'm trying to setup NUT to communicate with our UPS over the USB cable. First, I've tried with a "standard" ups.conf. Error message : device is (or not yet) supported. Second attempt, including productid

[Please use reply-all to keep the discussion on the list, thanks] On Nov 6, 2014, at 10:19 PM, Charles Lepple <clepple at gmail.com> wrote: > On Nov 6, 2014, at 12:48 PM, Steve Read <sd_read at hotmail.com> wrote: > >> I am presently upgrading my servers. The old ones are running Suse 10.1 and I am upgrading to the most recent Debian. > > What version of NUT on

Hi, what does Centos 7 do with UPD packets having invalid checksums? Are such packets inevitably dropped? Does a network card drop them when it does checksum verification in hardware even before the packets go anywhere? In general, if someone were to send me UPD packets with invalid checksums over the internet, how far would such packets get? In particular, how likely it is that SRTP

Hello!! I have a APC Back-UPS RS 800 and I'm using NUT v2.2.2 on a PowerPC powered NAS. With WinNut, I found the ups.load value strange, so I've done a "upsc ups" and got this results: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2007/12/28 battery.runtime: 997 battery.runtime.low: 120 battery.temperature: