similar to: Patching CyberPower UPS drivers

Build from source, and done . . . wasting your time looking for a less out of date RPM is pointless. . . RPM, .deb, etc are almost always downrev. . . - Tim On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > I recently got an RMCARD205 for my Cyber UPS.... > >if I use no MIBS line in the config file, I get this: > > >> Network

On June 11, 2017 8:58:11 AM GMT+02:00, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: >On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >>Build from source, and done . . . wasting your time looking for a less >>out of date RPM is pointless. . . RPM, .deb, etc are almost always >>downrev. . . >> >>- Tim >>

On Jan 19, 2016, at 9:37 AM, Ben Kamen <ben at benkamen.net> wrote: > > Hey there, > > I got a new UPS (CyberPower PR1500LCDRTXL2Ua) and found the serial drivers don't quite work... [...] > Essentially, I rewrote powpan_status so it better tolerates strings of different lengths (although I only have the 1 UPS right now, so I can't test against another and different

Hey all, I recently got an RMCARD205 for my Cyber UPS.... if I use no MIBS line in the config file, I get this: > Network UPS Tools - UPS driver controller 2.6.5 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'! > Please report it to NUT developers, with an 'upsc' output for your device. >

On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >Build from source, and done . . . wasting your time looking for a less >out of date RPM is pointless. . . RPM, .deb, etc are almost always >downrev. . . > >- Tim > >On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >>Hey all, >> >> I recently got an

Hi, ? have a necron snmp ups. nut-scanner cant find it. i tried to add with these definition but it fails.. [test5-ups] driver = snmp-ups port = 10.9.40.19 community = asdf12 desc ="test" i run driver with debugging , result is , root at upsviewer-debian:/usr/local/ups/bin# ./snmp-ups -DDDDDDD -a test5-upsNetwork UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000

Hey all, I ended up picking up the module listed in Subject line. I switched over my config but apparently not all going smoothly. My config is: [office] driver = powerpanel port = /dev/ttyS0 desc = "Office UPS" When I test the driver running power-panel as a test, I get: > [root at cornelius init.d]# powerpanel -a office -D -D -D -D >

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD Starting program: /usr/bin/snmp-ups -a tripplite -DD warning: Could not load shared library symbols for

Updating an old thread. History here. http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html On Fri, 1 Feb 2013, Tim Rice wrote: [snip] > > In all my testing I discovered the APC AP9630 is kind of flaky when >

On Feb 24, 2014, at 6:57 PM, Jason R Begley wrote: > Segmentation fault That's not good. If you crank up the debug level past 2, does it provide any more detail about where it crashed? (We'd only need the last few lines, if they are different.) I don't know how Arch Linux does debug symbols, so the dmesg output doesn't pinpoint which function in libc got bad data. Can you run

I have been working with NUT to get this working since upgrading to a web snmp card in a UPS. I keep getting seg faults when running snmp-ups also. Below is the output. kernel: [1365065.178230] snmp-ups[1940]: segfault at 0 ip b7555470 sp bf8d89e8 error 4 in libc-2.18.so[b74c2000+1a9000] Running: Arch i686 current Nut is current git Device is Tripp Lite SU2200XLa with WEBSNMPCARD running

Here is the upsc output: # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

I did a bunch of work on this today. It should be all set to go. This patch is to add support for the Cyberpower RMCARD snmp cards. I basically copied the driver for bestpower, changed the name and updated the mib map. I have this running on two separate systems (two separate ups's) and it looks good. The only thing I could not figure out was updating the Makefile.am (my aclocal/libtools

I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS 5000 RM DL4 with a AP9619 network management card. NUT properly detects when the UPS goes on battery and initiates a shutdown after the configured time. The problem I have is that I am using a 208V unit on a 240V circuit. That means the normal state for the UPS is "TRIM". NUT doesn't treat that as an on line

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

Hey all, ?I'm feeling spunky... and want to update nut to handle the new v2.0 MIB from CyberPower. I've looked at the cyberpower v0.1 .c/.h and being new to working on nut to this level -- anything anyone has to offer on adding code besides the obvious? like: should the 0.1 and 2.0 coexist somehow? (maybe different files) (also, is there a list of all the parms I can match up from the

On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: > I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS > 5000 RM DL4 with a AP9619 network management card. NUT properly detects > when the UPS goes on battery and initiates a shutdown after the configured > time. The problem I have is that I am using a 208V unit on a 240V circuit. > That means the normal