Hi,
I set up a new test this afternoon. I can't find anything related to
upssched and a bogus connection. The timer is not cleared and lauches
the script at the deadline.
Here is the syslog:
Sep 18 19:46:40 debiandell upsmon[1694]: UPS EATON@localhost on battery
Sep 18 19:46:40 debiandell upssched[2965]: Timer daemon started
Sep 18 19:46:40 debiandell upssched[2965]: New timer: timerondubatterie
(600 seconds)
Sep 18 19:48:17 debiandell kernel: [1211506.936044] hub 2-0:1.0: port 2
disabled by hub (EMI?), re-enabling...
Sep 18 19:48:17 debiandell kernel: [1211506.936139] usb 2-2: USB
disconnect, address 5
Sep 18 19:48:17 debiandell kernel: [1211507.176010] usb 2-2: new low
speed USB device using uhci_hcd and address 6
Sep 18 19:48:18 debiandell kernel: [1211507.788578] usb 2-2: New USB
device found, idVendor=0463, idProduct=ffff
Sep 18 19:48:18 debiandell kernel: [1211507.788583] usb 2-2: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Sep 18 19:48:18 debiandell kernel: [1211507.788586] usb 2-2: Product:
Evolution
Sep 18 19:48:18 debiandell kernel: [1211507.788589] usb 2-2:
Manufacturer: EATON
Sep 18 19:48:18 debiandell kernel: [1211507.788591] usb 2-2:
SerialNumber: ARDM0204T
Sep 18 19:48:18 debiandell kernel: [1211507.788701] usb 2-2:
configuration #1 chosen from 1 choice
Sep 18 19:48:18 debiandell usbhid-ups[1688]: libusb_get_interrupt: error
submitting URB: No such device
Sep 18 19:48:18 debiandell kernel: [1211508.120592] generic-usb: probe
of 0003:0463:FFFF.0005 failed with error -71
Sep 18 19:48:18 debiandell kernel: [1211508.176059] hub 2-0:1.0: port 2
disabled by hub (EMI?), re-enabling...
Sep 18 19:48:18 debiandell kernel: [1211508.176136] usb 2-2: USB
disconnect, address 6
Sep 18 19:48:19 debiandell kernel: [1211508.416010] usb 2-2: new low
speed USB device using uhci_hcd and address 7
Sep 18 19:48:20 debiandell usbhid-ups[1688]: libusb_get_interrupt: error
submitting URB: No such device
Sep 18 19:48:20 debiandell usbhid-ups[1688]: libusb_get_report: error
sending control message: No such device
Sep 18 19:48:24 debiandell kernel: [1211513.532017] usb 2-2: device
descriptor read/64, error -32
Sep 18 19:48:24 debiandell kernel: [1211513.756014] usb 2-2: device
descriptor read/64, error -32
Sep 18 19:48:24 debiandell kernel: [1211513.972015] usb 2-2: new low
speed USB device using uhci_hcd and address 8
Sep 18 19:48:24 debiandell kernel: [1211514.092021] usb 2-2: device
descriptor read/64, error -32
Sep 18 19:48:25 debiandell kernel: [1211514.824895] usb 2-2: New USB
device found, idVendor=0463, idProduct=ffff
Sep 18 19:48:25 debiandell kernel: [1211514.824898] usb 2-2: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Sep 18 19:48:25 debiandell kernel: [1211514.824902] usb 2-2: Product:
Evolution
Sep 18 19:48:25 debiandell kernel: [1211514.824904] usb 2-2:
Manufacturer: EATON
Sep 18 19:48:25 debiandell kernel: [1211514.824907] usb 2-2:
SerialNumber: ARDM0204T
Sep 18 19:48:25 debiandell kernel: [1211514.825020] usb 2-2:
configuration #1 chosen from 1 choice
Sep 18 19:48:35 debiandell upsd[1690]: Data for UPS [EATON] is stale -
check driver
Sep 18 19:48:38 debiandell kernel: [1211528.041619]
/build/buildd-linux-2.6_2.6.32-35-amd64-aZSlKL/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
usb_submit_urb(ctrl) failed
Sep 18 19:48:38 debiandell kernel: [1211528.041749] generic-usb
0003:0463:FFFF.0006: timeout initializing reports
Sep 18 19:48:38 debiandell kernel: [1211528.041902] generic-usb
0003:0463:FFFF.0006: hiddev0,hidraw0: USB HID v1.10 Device [EATON
Evolution] on usb-0000:00:1d.0-2/input0
Sep 18 19:48:40 debiandell upsmon[1694]: Poll UPS [EATON@localhost]
failed - Data stale
Sep 18 19:48:40 debiandell upsmon[1694]: Communications with UPS
EATON@localhost lost
Sep 18 19:48:41 debiandell upsd[1690]: UPS [EATON] data is no longer stale
Sep 18 19:48:45 debiandell upsmon[1694]: Communications with UPS
EATON@localhost established
Sep 18 19:48:45 debiandell upsmon[1694]: UPS EATON@localhost on line power
Like you said the fact that upssched clears the connection with the ups
when data becomes unavailable may explain it can't stop the timer when
it should.
Thanks.
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
