similar to: Updated to 2.6.5, previously-working APC SmartUPS now fails completely

(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

On Tue, 8 Oct 2013, Philip Tait wrote: > 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() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

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

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

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

Hi, I have two UPS SMART-UPS 2200 RM both of them have the same configuration.One of them works fine, but the other one it doesn't, it output as follows: snmp-ups -D -a nutdev10 Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) 0.000000 debug level is '1' 0.001013 SNMP UPS driver : entering upsdrv_initups() 0.048606 trying the new match_sysoid() method

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

Hello, i'm trying to monitor a APC Smart-UPS 1000 behind a APC AP9630 Network Management Card via SNMPv3 using the AES Privacy Protocol. * OS name and version: Debian 10.1 * exact NUT version: 2.7.4 * NUT installation method: from debian package 2.7.4-8 * exact device name and related information * Model Number AP9630 * Hardware Revision 08 * Manufacture Date

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

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

Hello All ! Recently I have upgraded NUT to 2.4.1, and now I can't monitor old IMV LanPro S3 UPS with old SNMP board. Previously it is monitored OK, but now snmp-ups refuses to start: [root at perforce /usr/local/etc/nut]# /usr/local/libexec/nut/snmp-ups -a lanproups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) debug level is '7' SNMP UPS driver : entering

I'm following advice from Arjen de Korte and Charles Lepple (see http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-January/005829.html). I added a full update on the specifics of my situation: http://lists.alioth.debian.org/pipermail/nut-upsdev/2011-February/005255.html Would appreciate guidance on getting started generating a MIB-to-NUT mapping (tools, etc): OS: CentOS 5.5 NUT

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

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

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

Alle, We're running Dovecot V1.0.7 on RHEL5.5, using maildir. We would like to user per user quotas with an OpenLDAP (V2.3.43) backend. We have setup a default quota in /etc/dovecot.conf: quota = maildir:storage=10240:ignore=Trash And have the following userdb configs in /etc/doveconf.conf: userdb ldap { args = /etc/dovecot-ldap.conf } and the following user_attrs defined in