similar to: sysOID for SMART-UPS 2200 RM XL

Hello all, Thank you in advance for a great FOSS project. Also, thank you for reading my question. I have a CyberPower OR1500LCDRTXL2U with an RMCARD205. There are a handful of devices plugged into the UPS. I received a message today saying to send upsc output to NUT developers after this message: "No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'" root at

Is there a way to DRY this up a bit? named_scope :has_valid_sysoid, lambda{|sysoid| (sysoid.nil?) ? {:conditions => ["nodesysoid IS NOT NULL AND nodelabel LIKE ''%-to-%''"], :include => [:ipinterface, :alarm]} : {:conditions => ["nodesysoid IS NOT NULL AND nodelabel LIKE ''%-to-%'' AND nodesysoid = ? ", sysoid], :include =>

I have nut/trusty,now 2.7.1-1ubuntu1 and nut-snmp/trusty,now 2.7.1-1ubuntu1 up and running from packages, but during the configuration process, upsdrvctl start included this output: No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.27'! Please report it to NUT developers, with an 'upsc' output for your device. As such, I am trying to report this to any developer who may be

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

Hi Guys, 2012/3/12 Michal Soltys <soltys at ziu.info>: > On 12-03-09 00:21, Greg A. Woods wrote: >> >> >> I had independently made a similar change to the apcsmart driver to keep >> it from failing when tcgetattr() reported some irrelevant differences in >> the port settings. ?What's actually in the patch now is my merge of the >> change from

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

Hi, This appears to be related to a thread from January 2010: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-January/004470.html NB: This is on an HP-UX 11.31 box, using a self compiled and packaged version of NUT 2.6.3, and net-snmp v5.7.1. Therefore some of the search paths and things like that may well be wrong because I've done something dumb. I'm also only just getting

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer"

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

Hi List, i've installed the network ups tool on one of my windows machine (server 2012 r2). My ups is an APC Back-UPS Pro 550 which is connected via USB to an Synology Diskstation DS414. I found this video https://www.youtube.com/watch?v=0l54n_37M_k My config: *nut.conf* MODE=standalone *ups.conf* [ups] driver = snmp-ups port = 192.168.2.5 community = public *upsd.users* [monuser]

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

Hey, I'm scheduling a 2.6.2 release for max. September 15. The content will be lighter than first expected with 2.8.0 (see below). This includes the current trunk plus: - merge the nut-scanner branch, - some snmp-ups improvements (sysOID matching for init stage) and some more MIBs, - a first complete version of the nut-ipmipsu driver, - the new jNut Java binding, - preliminary support of

All, I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a

On 2/24/2014 11:10 PM, Charles Lepple wrote: > 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?

I have an APC 9210 PDU in my rack. It's connected to the network and is configurable by web access. I'd like to control it in combination with my ups. Unfortunately I cannot get NUT to recognise this PDU. Here's my ups.conf section: [apc] driver = snmp-ups port = 192.168.10.21 mibs = auto community = public snmp_version = v1 running upsdrvctl gives this: $ sudo

Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Driver exited abnormally Network UPS Tools - Generic SNMP UPS driver 0.70 (2.7.1) kill: No such process No matching MIB found for sysOID '.1.3.6.1.4.1.674.10902.2'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to

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

[please use reply-all to include the list.] > On Oct 12, 2015, at 4:52 PM, Daniel Green <ddgreen at gmail.com> wrote: > > I recently connected my UPS to my NAS. The NAS detected the UPS, and I checked the "Enable network UPS server" option and added relevant IPs to the "Permitted DiskStation devices" option. The NAS is running DSM 5.2-5592 Update 4, with a NUT

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

Hi, I'm trying to setup a Raspberry Pi to monitor our UPSes, and gracefully shutdown our servers, as per this guide: https://openschoolsolutions.org/shutdown-servers-case-power-failure%e2%80%8a-%e2%80%8aups-nut-co/ https://hackernoon.com/how-to-shutdown-your-servers-in-case-of-power-failure-ups-nut-co-34d22a08e92 This is on Raspbian 10, running on a Raspberry Pi. NUT is version 2.7.4 and