Bug#322901: [Fwd: Re: Bug#322901: nut-usb: similar issue with newhidups]
Hi, 2007/2/2, Jean-Michel [EMAIL PROTECTED]: ... Feb 1 21:34:46 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale Feb 1 21:34:46 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost The situation has improved on the staleness management. Can you test the 2.2 release (2.2.0 is in testing) and report back if you still face this problem. Thanks, Arnaud -- Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322901: nut-usb: similar issue with newhidups
Arnaud Quette a écrit : can you also send me the output from upsc [EMAIL PROTECTED] ✄✄ upsc [EMAIL PROTECTED] battery.charge: 100 battery.charge.low: 80 battery.runtime: 668 driver.name: newhidups driver.parameter.port: auto driver.parameter.vendorid: 0463 driver.version: 2.0.4 driver.version.data: MGE HID 0.9 driver.version.internal: 0.28 input.transfer.high: 264.0 input.transfer.low: 184.0 outlet.0.desc: Main Outlet outlet.0.id: 1 outlet.0.switchable: 0 outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 2 outlet.1.switch: 1 outlet.1.switchable: 0 output.voltage: 230.0 ups.delay.shutdown: -1 ups.delay.start: -10 ups.load: 14 ups.mfr: MGE UPS SYSTEMS ups.model: Ellipse 600 ups.power.nominal: 600 ups.serial: AP8G3601C ups.status: OL CHRG ✄✄
Bug#322901: [Fwd: Re: Bug#322901: nut-usb: similar issue with newhidups]
2007/1/12, jeanmichel [EMAIL PROTECTED]: Package: nut-usb Version: 2.0.4-3 Followup-For: Bug #322901 With an ellipse 600: Jan 11 16:09:01 localhost /USR/SBIN/CRON[28115]: (root) CMD ( [ -d /var/lib/php5 ] find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm) Jan 11 16:14:11 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost upsd[25264]: Data for UPS [usb] is stale - check driver Jan 11 16:14:13 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:13 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] lost Jan 11 16:14:18 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:20 localhost upsd[25264]: UPS [usb] data is no longer stale Jan 11 16:14:23 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] established how often does it happen? This can help me in hunting a bit more that bug, but as stated before, I don't think I'll be able to completely remove the usbfs, but only the stale/restored communication. about 4 times a day: What's about the usbfs? computer:/var/log# grep [EMAIL PROTECTED] * daemon.log:Jan 28 09:17:10 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 28 09:17:10 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 28 09:17:15 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 28 10:52:49 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 28 10:52:49 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 28 10:52:54 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 29 09:46:57 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 29 09:46:57 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 29 09:47:02 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 29 13:07:32 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 29 13:07:32 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 29 13:07:37 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 29 15:19:29 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 29 15:19:29 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 29 15:19:34 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 29 15:19:39 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 29 18:29:28 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 29 18:29:28 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 29 18:29:33 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 30 00:28:21 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 30 00:28:21 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 30 00:28:26 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 30 03:05:54 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 30 03:05:54 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 30 03:05:59 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 31 04:30:18 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 31 04:30:18 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 31 04:30:23 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 31 04:30:28 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 31 10:26:15 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 31 10:26:15 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 31 10:26:20 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Jan 31 20:25:40 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Jan 31 20:25:40 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] lost daemon.log:Jan 31 20:25:45 computer upsmon[3335]: Communications with UPS [EMAIL PROTECTED] established daemon.log:Feb 1 00:02:06 computer upsmon[3335]: Poll UPS [EMAIL PROTECTED] failed - Data stale daemon.log:Feb 1 00:02:06 computer
Bug#322901: nut-usb: similar issue with newhidups
[please, keep the bug cc'ed] 2007/2/2, Jean-Michel [EMAIL PROTECTED]: ... how often does it happen? This can help me in hunting a bit more that bug, but as stated before, I don't think I'll be able to completely remove the usbfs, but only the stale/restored communication. about 4 times a day: can you also send me the output from upsc [EMAIL PROTECTED] What's about the usbfs? these are linked: the newhidups driver issue some usb requests, over usbfs (== libusb) which fails. This results in a temporary staleness (the UPS is not responding) of around 5 sec in your setup. While the later (staleness) can be addressed by setting MAXAGE to 20 (= 15 + 5) in upsd.conf, the former can't be guessed. what I have to check is the existence of a way to tell the kernel usbfs driver to not log every such failure... Finally, apart from the annoying log noise, this is more a warning than an error... Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD 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/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322901: nut-usb: similar issue with newhidups
reopen 322901 thanks Salut JM, 2007/1/12, jeanmichel [EMAIL PROTECTED]: Package: nut-usb Version: 2.0.4-3 Followup-For: Bug #322901 With an ellipse 600: Jan 11 16:09:01 localhost /USR/SBIN/CRON[28115]: (root) CMD ( [ -d /var/lib/php5 ] find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm) Jan 11 16:14:11 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost upsd[25264]: Data for UPS [usb] is stale - check driver Jan 11 16:14:13 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:13 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] lost Jan 11 16:14:18 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:20 localhost upsd[25264]: UPS [usb] data is no longer stale Jan 11 16:14:23 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] established how often does it happen? This can help me in hunting a bit more that bug, but as stated before, I don't think I'll be able to completely remove the usbfs, but only the stale/restored communication. FYI, this is (or should be) a temporary deny of service from the UPS. This can happen when the unit is too heavily loaded (ie quering too much the data, while the unit is auto testing its battery). Note that lowering the driver polling frequency should reduce (maybe suppress) this. See newhidups -h - pollfreq for more info. Finally, I've reopened the bug as a reminder. thanks for the report, Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD 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/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322901: nut-usb: similar issue with newhidups
Package: nut-usb Version: 2.0.4-3 Followup-For: Bug #322901 With an ellipse 600: Jan 11 16:09:01 localhost /USR/SBIN/CRON[28115]: (root) CMD ( [ -d /var/lib/php5 ] find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm) Jan 11 16:14:11 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost upsd[25264]: Data for UPS [usb] is stale - check driver Jan 11 16:14:13 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:13 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] lost Jan 11 16:14:18 localhost upsmon[25267]: Poll UPS [EMAIL PROTECTED] failed - Data stale Jan 11 16:14:20 localhost upsd[25264]: UPS [usb] data is no longer stale Jan 11 16:14:23 localhost upsmon[25267]: Communications with UPS [EMAIL PROTECTED] established -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-amd64 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages nut-usb depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii nut 2.0.4-3 The core system of the nut - Netwo ii udev 0.103-1 /dev/ and hotplug management daemo nut-usb recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
