Greetings; Nut pull & build from about two weeks ago, 2.4.3 I believe. Belkin UPS. I have everything working but a proper shutdown of upsd when I reboot, it hangs there and needs the hdwe reset button to reset it. That may be related to my finding more than 1 K##upsd and more than one K##upsmon, in /etc/rc5.d and which I have now nuked. However, while its working well enough to monitor, it is flooding the syslog every 2 seconds with: Nov 19 07:05:56 coyote upsd[4884]: mainloop: Interrupted system call Nov 19 07:05:56 coyote upsd[4884]: Signal 15: exiting Nov 19 07:05:56 coyote usbhid-ups[4874]: Signal 15: exiting Nov 19 07:05:58 coyote upsmon[1681]: Poll UPS [coyotes-ups at localhost] failed - Write error: Broken pipe Nov 19 07:05:58 coyote upsmon[1681]: Communications with UPS coyotes-ups at localhost lost Nov 19 07:05:58 coyote wall[11797]: wall: user gene broadcasted 1 lines (52 chars) Broadcast message from gene at coyote.coyote.den (Fri Nov 19 07:05:58 2010): Communications with UPS coyotes-ups at localhost lost Nov 19 07:06:03 coyote upsmon[1681]: UPS [coyotes-ups at localhost]: connect failed: Connection failure: Connection refused Nov 19 07:06:23 coyote last message repeated 4 times Nov 19 07:06:25 coyote klogd: usb 2-9: manual set_interface for iface 0, alt 0 Nov 19 07:06:26 coyote usbhid-ups[11879]: Startup successful Nov 19 07:06:26 coyote klogd: ohci_hcd 0000:00:02.0: urb ee0f3780 path 9 ep1in 93120000 cc 9 --> status -121 Nov 19 07:06:26 coyote upsd[11886]: listening on localhost port 3493 Nov 19 07:06:26 coyote upsd[11886]: listening on ::1 port 3493 Nov 19 07:06:26 coyote upsd[11886]: /var/state/ups is world readable Nov 19 07:06:26 coyote upsd[11886]: Connected to UPS [coyotes-ups]: usbhid-ups-coyotes-ups Nov 19 07:06:26 coyote upsd[11887]: Startup successful Nov 19 07:06:28 coyote klogd: ohci_hcd 0000:00:02.0: urb ee0f3200 path 9 ep1in 92120000 cc 9 --> status -121 Nov 19 07:06:28 coyote upsd[11887]: User gene at 127.0.0.1 logged into UPS [coyotes-ups] Nov 19 07:06:28 coyote upsmon[1681]: Communications with UPS coyotes-ups at localhost established Nov 19 07:06:28 coyote wall[11899]: wall: user gene broadcasted 1 lines (59 chars) Broadcast message from gene at coyote.coyote.den (Fri Nov 19 07:06:28 2010): Communications with UPS coyotes-ups at localhost established Nov 19 07:06:30 coyote klogd: ohci_hcd 0000:00:02.0: urb e7d21400 path 9 ep1in 93120000 cc 9 --> status -121 Nov 19 07:06:32 coyote klogd: ohci_hcd 0000:00:02.0: urb ee337e00 path 9 ep1in 92120000 cc 9 --> status -121 Nov 19 07:06:34 coyote klogd: ohci_hcd 0000:00:02.0: urb d88ae000 path 9 ep1in 93120000 cc 9 --> status -121 Nov 19 07:06:36 coyote klogd: ohci_hcd 0000:00:02.0: urb ee0f3b00 path 9 ep1in 92120000 cc 9 --> status -121 Nov 19 07:06:38 coyote klogd: ohci_hcd 0000:00:02.0: urb ea7d1880 path 9 ep1in 93120000 cc 9 --> status -121 Nov 19 07:06:40 coyote klogd: ohci_hcd 0000:00:02.0: urb e7d21000 path 9 ep1in 92120000 cc 9 --> status -121 Nov 19 07:06:42 coyote klogd: ohci_hcd 0000:00:02.0: urb ede6d900 path 9 ep1in 93120000 cc 9 --> status -121 And my syslog, rotated Sunday morning, is now 21+ megabytes and growing. Any idea how to stop this, or send it to /dev/null? Thanks -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Parents often talk about the younger generation as if they didn't have much of anything to do with it.
On Nov 19, 2010, at 7:13 AM, Gene Heskett wrote:> Greetings; > > Nut pull & build from about two weeks ago, 2.4.3 I believe.The 2.4.3 tarball, or from SVN? (If SVN, there should be a number after 2.4.3, such as 2.4.3-r1234).> Belkin UPS. > I have everything working but a proper shutdown of upsd when I reboot, > it hangs there and needs the hdwe reset button to reset it. That > may be > related to my finding more than 1 K##upsd and more than one > K##upsmon, in > /etc/rc5.d and which I have now nuked. > > However, while its working well enough to monitor, it is flooding the > syslog every 2 seconds with: > > Nov 19 07:05:56 coyote upsd[4884]: mainloop: Interrupted system call > Nov 19 07:05:56 coyote upsd[4884]: Signal 15: exiting > Nov 19 07:05:56 coyote usbhid-ups[4874]: Signal 15: exiting^^^ Is this part repeating, or was this just the first portion after restarting NUT? (In a normal setup, upsd should be started once, and shouldn't be killed until shutdown time.)> Nov 19 07:06:30 coyote klogd: ohci_hcd 0000:00:02.0: urb e7d21400 > path 9 ep1in 93120000 cc 9 --> status -121Looks like -121 is -EREMOTEIO, which apparently means this (from Documentation/usb/error-codes.txt in the kernel tree): "The data read from the endpoint did not fill the specified buffer, and URB_SHORT_NOT_OK was set in urb->transfer_flags." The fact that it is happening every two seconds might be a clue, but I am not familiar with the main status loop in usbhid-ups (I would have thought it would poll only once every 30 seconds, based on the man page). Perhaps one of the authors of usbhid-ups has a better idea of whether we can fix this (since libusb doesn't expose the URB transfer_flags options), or if it is something we can't work around.