Hi, I'm new to nut, just installed it. I configured it using the hidups driver to work with my APC BackUPS: # upsc apc350@localhost battery.charge: 100 battery.runtime: 885 battery.voltage: 13.5 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.delay.shutdown: -1 ups.delay.start: 0 ups.load: 660 ups.mfr: American Power Conversion ups.model: Back-UPS CS 350 FW:807.q3.I USB FW:q3 ups.serial: BB0348021310 ups.status: OL it seems to work OK, but I get loads of Unhandled event entries in my syslog when the driver is running: Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840058 (6) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500d1 (1) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840068 (0) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x850043 (0) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840073 (0) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x85004b (0) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840065 (0) Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500db (0) Jul 1 16:30:07 tower hidups[16960]: Ignoring x86 page event 0xff860080 (0) How can I relax these syslog entries? Akos
Arnaud Quette
2006-Jul-03 13:25 UTC
[Nut-upsuser] Unhandled event when using APC BackUPS Pro
2006/7/1, ?kos Mar?y <darkeye@tyrell.hu>:> > Hi, > > I'm new to nut, just installed it. I configured it using the hidups > driver to work with my APC BackUPS: > > # upsc apc350@localhost > battery.charge: 100 > battery.runtime: 885 > battery.voltage: 13.5 > driver.name: hidups > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.0.0 > ups.delay.shutdown: -1 > ups.delay.start: 0 > ups.load: 660 > ups.mfr: American Power Conversion > ups.model: Back-UPS CS 350 FW:807.q3.I USB FW:q3 > ups.serial: BB0348021310 > ups.status: OL > > > it seems to work OK, but I get loads of Unhandled event entries in my > syslog when the driver is running: > > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840058 (6) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500d1 (1) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840068 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x850043 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840073 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x85004b (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840065 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500db (0) > Jul 1 16:30:07 tower hidups[16960]: Ignoring x86 page event 0xff860080 > (0) > > > > How can I relax these syslog entries? >no way apart from tweaking / recompiling the driver. moreover, newhidups is superceding hidups as of 2.0.3. The sad point is the 2.0.3 version of newhidups has a serious bug, that's already fixed, but which need nut 2.0.4 to be released... Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060703/0f9ebed8/attachment.htm
Arnaud Quette
2006-Jul-03 13:48 UTC
[Nut-upsuser] Unhandled event when using APC BackUPS Pro
2006/7/1, ?kos Mar?y <darkeye@tyrell.hu>:> > Hi, > > I'm new to nut, just installed it. I configured it using the hidups > driver to work with my APC BackUPS: > > # upsc apc350@localhost > battery.charge: 100 > battery.runtime: 885 > battery.voltage: 13.5 > driver.name: hidups > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.0.0 > ups.delay.shutdown: -1 > ups.delay.start: 0 > ups.load: 660 > ups.mfr: American Power Conversion > ups.model: Back-UPS CS 350 FW:807.q3.I USB FW:q3 > ups.serial: BB0348021310 > ups.status: OL > > > it seems to work OK, but I get loads of Unhandled event entries in my > syslog when the driver is running: > > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840058 (6) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500d1 (1) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840068 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x850043 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840073 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x85004b (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x840065 (0) > Jul 1 16:30:07 tower hidups[16960]: Unhandled event: 0x8500db (0) > Jul 1 16:30:07 tower hidups[16960]: Ignoring x86 page event 0xff860080 > (0) > > > > How can I relax these syslog entries? >no way apart from tweaking / recompiling the driver. moreover, newhidups is superceding hidups as of 2.0.3. The sad point is the 2.0.3 version of newhidups has a serious bug, that's already fixed, but which need nut 2.0.4 to be released... Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060703/a99e782b/attachment.html