search for: su_find_infoval

Displaying 8 results from an estimated 8 matches for "su_find_infoval".

Did you mean: hu_find_infoval
2013 Jul 17
2
HP R12000/3 UPS reports status as OL DISCHRG OB
Here's the first update of ups.status: 0.102449 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.102546 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.102646 nut_snmp_get(.1.3.6.1.4.1.232.165.3.4.5.0) 0.104539 SNMP UPS driver : entering su_status_set() 0.104641 su_find_infoval: found OL (value: 3) 0.104730 => value: 3 0.104823 getting data: ups.status (.1.3.6.1.4.1.232.165.3.2.5.0) 0.104919 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.2.5.0 0.105028 nut_snmp_get(.1.3.6.1.4.1.232.165.3.2.5.0) 0.107134 SNMP UPS driver : entering su_status_set() 0.107...
2014 Feb 27
2
snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card
...utput_phases 0.096136 Check output_phases 0.096142 Check output_phases 0.096149 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.096156 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.100990 SNMP UPS driver : entering su_status_set() 0.101016 su_find_infoval: found OL (value: 3) 0.101024 => value: 3 0.101032 getting data: ups.status (.1.3.6.1.4.1.232.165.3.2.5.0) 0.101039 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.2.5.0 0.107038 SNMP UPS driver : entering su_status_set() 0.107063 su_find_infoval: no matching INF...
2012 Apr 16
2
Snmp-ups/netvision driver for Socomec UPS
...4555.1.1.1.1.1.4.0) 0.037646 entering su_setinfo(ups.serial) 0.037662 getting data: ups.firmware.aux (.1.3.6.1.4.1.4555.1.1.1.1.1.2.0) 0.039497 entering su_setinfo(ups.firmware.aux) 0.039512 getting data: ups.status (.1.3.6.1.4.1.4555.1.1.1.1.2.1.0) 0.041373 su_find_infoval: found (value: 2) 0.041383 getting data: ups.status (.1.3.6.1.4.1.4555.1.1.1.1.4.1.0) 0.043248 su_find_infoval: found (value: 9) 0.043258 getting data: ups.load (.1.3.6.1.4.1.4555.1.1.1.1.4.4.1.4.1) 0.045975 entering su_setinfo(ups.load) 0.045987 getting d...
2019 Sep 23
0
warnung: base variable (battery.runtime.low) is immutable
...ib    0.147381    Detected                  on host x.x.x.x (mib: ietf 1.5)    0.147456    SNMP UPS driver: entering upsdrv_initinfo()    [...]    7.760191    entering su_setinfo(output.realpower.nominal)    7.760200    getting data: battery.runtime.low (1.3.6.1.2.1.33.1.9.7.0)    7.820735    su_find_infoval: no matching INFO_* value for this OID value (3)    7.820778    entering su_setinfo(battery.runtime.low)    7.820785    dstate_setflags: base variable (battery.runtime.low) is immutable    7.820789    getting data: ups.beeper.status (1.3.6.1.2.1.33.1.9.8.0)    7.856607    su_find_infoval: no...
2013 Jul 16
0
HP R12000/3 UPS reports status as OL DISCHRG OB
Sorry about that! Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: 16 July 2013 00:32 To: Pratt Chris Subject: Re: [Nut-upsuser] HP R12000/3 UPS reports status as OL DISCHRG OB On Jul 15, 2013, at 9:35 AM, Pratt Chris wrote: > Debug output
2010 Jun 22
1
snmp-ups 2.4.3 cannot talk to upsd
Hi all, I recently upgraded an ubuntu jaunty machine with nut 2.4.1 to lucid LTS. The previously working nut configuration is a no-go, but I got it up and running using the snmp-ups executable from the previous install. What it happens (from what I can see at least) is that the status has been changed and it's not read as before. In the 2.4.1 release I had an "OL" string (online, I
2013 Jul 15
4
HP R12000/3 UPS reports status as OL DISCHRG OB
Hi. Back before Christmas Arnaud sent me a patch for the snmp-ups driver for my HP R12000/3 UPS. Unfortunately shortly after I had to take quite a lot of sick leave so wasn't able to progress it, but I'm working on it again now. I'm at the point where I can start the driver with upsdrvctl and start the daemon with upsd. When I check the UPS status though it shows as OL DISCHRG OB,
2006 Jan 21
2
snmp-ups hacking
Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)