search for: process_status_info

...3. Start, powerfail and recovery detections, UPS shutdown work very well. Only continous scanning seems to fail. Following are the logs: [root@xa000000 root]# newhidups -a ups_on_usb -DD <...> Time range from 15mn to 6 hours, depending... upsdrv_updateinfo... Waiting for notifications... process_status_info: online process_status_info: !dischrg process_status_info: chrg process_status_info: !shutdownimm process_status_info: !lowbatt upsdrv_updateinfo... Waiting for notifications... process_status_info: online process_status_info: !dischrg process_status_info: chrg process_status_info: !shutdownimm Can...

...UPS > > Looking up PowerSummary > > Looking up PresentStatus > > Looking up ACPresent > > Report : (8 bytes) =3D> 00 00 9C F3 00 03 10 D2 > > hu_find_infoval: searching for value =3D 0 > > > > hu_find_infoval: found !online (value: 0) > > > > process_status_info: !online > > entering string_to_path() > > Looking up UPS > > Looking up PowerSummary > > Looking up PresentStatus > > Looking up Discharging > > Report : (8 bytes) =3D> 00 00 9C F3 00 03 10 D2 > > hu_find_infoval: searching for value =3D 0 > > &gt...

...to > reconnect with the error: > > *** glibc detected *** double free or corruption (fasttop): 0x08068268 *** > > Following is a copy&paste of the last lines of konsole output: > > /lib/nut/newhidups -a mge -DD -u nut > ---8<--- > Waiting for notifications... > process_status_info: online > process_status_info: !dischrg > process_status_info: chrg > process_status_info: !shutdownimm > process_status_info: !lowbatt > upsdrv_updateinfo... > Waiting for notifications... > Can't retrieve Report 1 (-32/32): Broken pipe > ===============================...

...e we receive VERY long output, the lust lines are: Entering libusb_get_report =>> Before exponent: 0, 0/0) =>> After conversion: 0.000000 (0), 0/0) Report : (8 bytes) => 02 00 E8 03 00 00 00 00 hu_find_infoval: searching for value = 0 hu_find_infoval: found !shutdownimm (value: 0) process_status_info: !shutdownimm entering string_to_path() parsing UPS Looking up UPS hid_lookup_usage: found 840004 parsing PowerSummary Looking up PowerSummary hid_lookup_usage: found 840024 parsing PresentStatus Looking up PresentStatus hid_lookup_usage: found 840002 parsing BelowRemainingCapacityLimit Looking up...

...ery level (a potentially risky situation if we get another power failure immediately) 3) The UPS therefore reports low battery status to newhidups for the first few cycles (actually maybe just once!), 4) The UPS reaches enough reserves and no longer reports low battery Question: Looking at process_status_info(), ups_status seems to be used cumulatively, and alternative states clear each other, but who clears low battery from ups_status? I have observed upsc report a status of OL+LB+CHRG on a well charged battery several times, and I have just accidentally created a short power interruption for a fu...

...860029 Path: UPS.ff86002a entering identify_ups(0x051d, 0x0001) Can't find object UPS.Battery.Temperature Can't find object UPS.Output.PercentLoad Can't find object UPS.PowerSummary.DelayBeforeShutdown Can't find object UPS.Battery.Test Can't find object UPS.Battery.Temperature process_status_info: OL Can't find object UPS.Input.Voltage Can't find object UPS.Output.Voltage Can't find object UPS.Output.ConfigVoltage Can't find object UPS.BatterySystem.Battery.Test Can't find object UPS.BatterySystem.Battery.Test Can't find object UPS.BatterySystem.Battery.Test Can'...

Arnaud, > first, even if your battery is full, and your ups is online, there is a > small amount of power drawn. So having always is CHRG status is normal. > In fact, these complementary status are more interesting for higher end > UPSs. > > second, these status need not to be handled like LB, as each one clears the > other. While LB had no pending event (!LB) before... >

...atching INFO_* value for this HID value (0) ups.status not affected Object: UPS.PowerSummary.PresentStatus.BatteryPresent = 1 ups.status not affected Object: UPS.PowerSummary.PresentStatus.ACPresent = 1 hu_find_infoval: searching for value = 1 hu_find_infoval: found OL (value: 1) ups.status = OL process_status_info: OL Object: UPS.PowerSummary.PresentStatus.Discharging = 0 hu_find_infoval: searching for value = 0 hu_find_infoval: no matching INFO_* value for this HID value (0) ups.status not affected Object: UPS.PowerSummary.PresentStatus.Charging = 0 hu_find_infoval: searching for value = 0 hu_find_infov...