[Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.
Jason R Begley
jayray at digitalgoat.com
Tue Feb 25 03:29:14 UTC 2014
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 linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Network UPS Tools - Generic SNMP UPS driver 0.71 (2.7.1-signed-54-g348cd84)
0.000000 debug level is '2'
0.002156 SNMP UPS driver : entering upsdrv_initups()
0.002169 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.025430 SNMP UPS driver : entering load_mib2nut(auto)
0.025464 trying the new match_sysoid() method
0.028413 match_sysoid: device sysOID value = .1.3.6.1.4.1.850.1
0.028449 match_sysoid: checking MIB apcc
0.028474 match_sysoid: checking MIB mge
0.028497 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.705.1
0.028519 match_sysoid: checking MIB netvision
0.028544 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.4555.1.1.1
0.028566 match_sysoid: checking MIB pw
0.028589 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.534.1
0.028611 match_sysoid: checking MIB aphel_genesisII
0.028632 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.17373
0.028653 match_sysoid: checking MIB aphel_revelation
0.028675 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.534.6.6.6
0.028695 match_sysoid: checking MIB eaton_epdu
0.028717 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.534.6.6.7
0.028736 match_sysoid: checking MIB pulizzi_switched1
0.028758 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.20677.1
0.028779 match_sysoid: checking MIB pulizzi_switched2
0.028801 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.20677.2
0.028821 match_sysoid: checking MIB raritan
0.028843 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.13742
0.028864 match_sysoid: checking MIB baytech
0.028885 match_sysoid: checking MIB cpqpower
0.028907 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.232.165.3
0.028928 match_sysoid: checking MIB bestpower
0.028948 match_sysoid: checking MIB cyberpower
0.028969 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.3808
0.028988 match_sysoid: checking MIB delta_ups
0.029010 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.2254.2.4
0.029030 match_sysoid: checking MIB xppc
0.029052 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.4.1.935
0.029073 match_sysoid: checking MIB ietf
0.029095 match_sysoid: comparing .1.3.6.1.4.1.850.1 with
.1.3.6.1.2.1.33
0.029115 No matching MIB found for sysOID '.1.3.6.1.4.1.850.1'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
0.029148 load_mib2nut: trying classic method with 'apcc' mib
0.032571 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.318.1.1.1.1.1.1.0
0.032599 load_mib2nut: trying classic method with 'mge' mib
0.035518 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.705.1.1.1.0
0.035545 load_mib2nut: trying classic method with 'netvision' mib
0.038479 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.4555.1.1.1.1.1.1.0
0.038507 load_mib2nut: trying classic method with 'pw' mib
0.041429 [tripplite] unhandled ASN 0x80 received from
1.3.6.1.4.1.534.1.1.2.0
0.041456 load_mib2nut: trying classic method with
'aphel_genesisII' mib
0.044843 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.17373.3.1.1.0
0.044872 load_mib2nut: trying classic method with
'aphel_revelation' mib
0.047805 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.534.6.6.6.1.1.12.0
0.047832 load_mib2nut: trying classic method with 'eaton_epdu' mib
0.050761 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.534.6.6.7.1.2.1.2.0
0.050789 load_mib2nut: trying classic method with
'pulizzi_switched1' mib
0.054370 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.20677.1
0.054397 load_mib2nut: trying classic method with
'pulizzi_switched2' mib
0.057324 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.20677.1
0.057352 load_mib2nut: trying classic method with 'raritan' mib
0.060284 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.13742.1.1.12.0
0.060312 load_mib2nut: trying classic method with 'baytech' mib
0.063645 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.4779.1.3.5.2.1.24.1
0.063673 load_mib2nut: trying classic method with 'cpqpower' mib
0.066593 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.232.165.3.1.1.0
0.066620 load_mib2nut: trying classic method with 'bestpower' mib
0.069557 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.2947.1.1.2.0
0.069584 load_mib2nut: trying classic method with 'cyberpower' mib
0.073180 [tripplite] unhandled ASN 0x80 received from
.1.3.6.1.4.1.3808.1.1.1.1.1.1.0
0.073209 load_mib2nut: trying classic method with 'delta_ups' mib
Program received signal SIGSEGV, Segmentation fault.
0xb7da9470 in __strchr_sse2_bsf () from /usr/lib/libc.so.6
(gdb) bt
#0 0xb7da9470 in __strchr_sse2_bsf () from /usr/lib/libc.so.6
#1 0xb7f05758 in snmp_parse_oid () from /usr/lib/libnetsnmp.so.30
#2 0x0804afd8 in ?? ()
#3 0x0804b261 in ?? ()
#4 0x0804bab6 in ?? ()
#5 0x0804be7b in ?? ()
#6 0x0804bfd2 in ?? ()
#7 0x08049fb4 in ?? ()
#8 0xb7d2f993 in __libc_start_main () from /usr/lib/libc.so.6
#9 0x0804a469 in ?? ()
On 2/24/2014 8:00 PM, Charles Lepple wrote:
> 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 it in gdb and get a backtrace? That will probably be something like this:
>
> $ gdb snmp-ups
> (gdb) run -a <UPS-name> -DD
> ...
> (gdb) bt
>
>> SNMP-Walk:
> NUT ends up using the numeric OIDs internally. Could you please follow the steps here:
>
> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_creating_a_subdriver
>
> Either "mode 1" or "mode 2" should work, but if you run into trouble with "mode 1", just dump the files as mentioned in "mode 2", gzip them, and post them to the list. For the "-n" flag, I'd recommend "trippups1", as that seems to be one of the more common names for that MIB.
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trippups1.tar.gz
Type: application/gzip
Size: 1490 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140224/4902c3b1/attachment-0001.bin>
More information about the Nut-upsuser
mailing list