similar to: Two UPS with same vendor ID

Hi all, I'm trying to configure Nut to connect to an APC BackUPS Pro 900VA. This ups uses a serial port on which _simple_ or _smart_ signaling should be spoken. I've connected the UPS to a serial port using the original 940_0128A cable from APC. Unfortunately I've not yet managed to read any data from the ups. If I try to load the apcsmart driver it tells me that it cannot communicate

Hello world! Please, help me :-) I have a APC RS-800 usb and it don't shutdown. I try every things but nothing: don't shutdown. Uhmmmm My actual situation: tux:/home/effem# uname -a Linux tux 2.6.26-1-686 #1 SMP Wed Aug 20 12:56:41 UTC 2008 i686 GNU/Linux tux:/home/effem# wajig policy nut nut: Installato: 2.2.2-6 Candidato: 2.2.2-6 Tabella versione: 2.2.2-7 0 -20

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial =

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575

On Apr 25, 2013, at 9:42 AM, Christian Wiese wrote: > I created a pull request #27 which is fixing the issue. > > # nut-scanner -qNU > [nutdev1] > driver = "usbhid-ups" > port = "auto" > vendorid = "051D" > productid = "0002" > product = "Back-UPS ES 700G FW:871.O2 .I USB FW:O2" > serial = "5B1243T01934"

Is NUT using the same SNMP v3 user as your SNMP Set or a different one? If it is a different one (e.g. an SNMP v1 or v2c string) does that user / community string have read/write access? tcpdump to listen for packets across UDP 161 is one way to check what is actually being sent. Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser

I'm in the process of trying to get NUT to manage an APC SmartUPS. Monitoring of the UPS is working fine: $ upsc nutdev1 at localhost Init SSL without certificate database ambient.1.humidity.alarm.high: 60.00 ambient.1.humidity.alarm.low: 30.00 ambient.1.temperature.alarm.high: 40.00 ambient.1.temperature.alarm.low: 10.00 battery.charge: 94.00 battery.charge.restart: 0 battery.current: 0.00

Hello, I have a xen server (xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p / kernel 2.6.24-28-xen). I have some domUs, one of them is a fli4l router, the others are eisfair domUs (fileserver, webserver and mailserver). All of the domUs are connected via vif network interface with a bridge in dom0. There is a problem invoking following command in every domU: openssl s_client -connect

I like to think of myself as reasonably intelligent when it comes to systems (MS in Comp Sci, albeit a few hundred moons ago), but I seem to be missing something when it comes to installing NUT on a 64 bit windows XP system. I downloaded and attempted it install but the installer said I needed to install libusb manually. So I went and grabbed that, unpacked the ZIP file and ran the

Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite UPS. I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb gives: Bus 006 Device 002: ID 09ae:3016 Tripp Lite nut-scanner -U has no issues either: # nut-scanner -U Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "09AE" productid =

Hi all, Yesterday, I bought a UPS for the first time in my life, and was eager to dive into NUT. But not all is working as expected... I saw a similar thread started on 18 October, but it didn't help me. (I also spent a handful of hours searching the web for solutions, and of course read the manual and FAQ - "queequeg".) I tried shutting my UPS (APC "Back-UPS BX750MI

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:

Hi all, First of all, I would like to thank everyone who was involved in the development of NUT. Although it took me some time to set it up, now it appears to be working very well. Thanks for the good software! This is my success report for an APC Back-UPS RS 800: khali at mahadeva:~> upsc rs800 battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25

Is anyone using snmp-ups with the -k option successfully? This is really starting to look like a bug somewhere in nut, not a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x

The parts of klibc specific to the sparc architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 1b5c93603ed3460ed1fba9e5d453a6fa54d0ccce tree 7fb0a134b3add408c02b470616d440ad398d86d3 parent 94473ed85b00ec45ff8ee6cac62f60a368ff4534 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:47 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

I meant to send this to the list but evidently only sent it to David. Since sending it I've done a second test which shows what a successful snmpset looks like. First attachment, from the forwarded email, is nutout.txt. Second attachment is snmpout.txt. nomad -------- Forwarded Message -------- Subject: Re: [Nut-upsuser] [EXTERNAL] SNMP shutdown timing out Date: Mon, 4 May 2020 09:28:57

What exactly are the current limitations for using -O4 to create shared libraries with llvm/llvm-gcc-4.2 2.5? I tried a build of xplor-nih at -O4 with llvm-gcc, llvm-g++ and llvm-gfortran. The build fails to link shared libraries with errors such as... Building xplor-nih for platform: Darwin_9_x86 [ -d /Users/howarth/xplor-nih-2.21/bin.Darwin_9_x86/ ] || mkdir

On Thu, May 7, 2015 at 3:28 AM, Edgar E. Iglesias <edgar.iglesias at gmail.com> wrote: > > On Wed, May 06, 2015 at 03:51:48PM +0930, Rusty Russell wrote: > > "Edgar E. Iglesias" <edgar.iglesias at gmail.com> writes: > > > From: "Edgar E. Iglesias" <edgar.iglesias at xilinx.com> > > > > > > Signed-off-by: Edgar E. Iglesias

On Thu, May 7, 2015 at 3:28 AM, Edgar E. Iglesias <edgar.iglesias at gmail.com> wrote: > > On Wed, May 06, 2015 at 03:51:48PM +0930, Rusty Russell wrote: > > "Edgar E. Iglesias" <edgar.iglesias at gmail.com> writes: > > > From: "Edgar E. Iglesias" <edgar.iglesias at xilinx.com> > > > > > > Signed-off-by: Edgar E. Iglesias

I am seeing the same problems using 'llvm-ld' with llvm-gcc at -O4 on x86_64 Fedora 8 linux as on Darwin. Another example of this is building the scimark2_1c benchmark... http://math.nist.gov/scimark2/download_c.html as follows on x86_64 Fedora 8... /home/howarth/llvm-gcc42-work/bin/gcc -O4 -m64 -c FFT.c /home/howarth/llvm-gcc42-work/bin/gcc -O4 -m64 -c kernel.c