The UPS seems to disconnect totally, i need to physically disconnect the cable to get the UPS connected again. A reboot is not enough. Also tried 2 different cables, the one i use now is shielded + 2 ferrite chokes to limit interference. But i want to use NUT since i dont have enough resources to run X.. -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: October 10, 2016 12:23 AM UTC Time: October 9, 2016 10:23 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> 2016-10-03 14:56 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>:> Hi, > > The UPS is now connected via HID-USB, but seems to randomly disconnect. > Sometimes after a few hours, other times days... > Any suggestions?A log would help, but, in general, if the device disconnects and, after a short time, the connection is restored, it could be a cable problem, or the UPS not keeping the pace needed to update all the necessary data. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161010/f77e3a67/attachment.html>
2016-10-10 15:28 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>:> The UPS seems to disconnect totally, i need to physically disconnect the > cable to get the UPS connected again. > A reboot is not enough.Ouch, this is more severe than what I thought. As a first step, you could try and increase the timeouts for pollfreq and pollinterval. Again, a log (compressed) of the driver running in debug mode when those problems occur would be helpful.
After about 12 hours when running debug this is the last message: 79073.364051 ================================================= 79073.365463 = device has been disconnected, try to reconnect 79073.365721 ================================================= 79073.367768 Checking device (0424/EC00) (001/003) 79073.371435 - VendorID: 0424 79073.373340 - ProductID: ec00 79073.373866 - Manufacturer: unknown 79073.375129 - Product: unknown 79073.375453 - Serial Number: unknown 79073.376150 - Bus: 001 79073.377569 Trying to match device 79073.377862 Device does not match - skipping 79073.378570 Checking device (0424/9512) (001/002) 79073.379685 - VendorID: 0424 79073.380404 - ProductID: 9512 79073.381658 - Manufacturer: unknown 79073.382314 - Product: unknown 79073.382564 - Serial Number: unknown 79073.383999 - Bus: 001 79073.384263 Trying to match device 79073.384620 Device does not match - skipping 79073.385769 Checking device (1D6B/0002) (001/001) 79073.387191 - VendorID: 1d6b 79073.388246 - ProductID: 0002 79073.388506 - Manufacturer: unknown 79073.389510 - Product: unknown 79073.389767 - Serial Number: unknown 79073.389998 - Bus: 001 79073.391054 Trying to match device 79073.391325 Device does not match - skipping 79073.392549 No appropriate HID device found DMESG LOG: [160014.322035] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160016.358003] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160018.202678] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160018.203008] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160020.324757] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160020.325172] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160022.362397] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160024.208642] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160024.208975] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160026.327614] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160026.328038] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160028.367136] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160030.214708] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160030.215123] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160032.330506] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160032.330934] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160034.369852] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160036.220658] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160036.220992] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160038.334177] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160038.334605] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160040.371685] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160040.384369] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160042.336466] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160042.336992] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160044.376027] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160046.230472] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160046.230804] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160048.340205] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160048.340635] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160050.378051] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160052.236502] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160052.236832] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160054.344607] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160054.345038] usb 1-1.2: usbfs: process 1079 (usbhid-ups) did not claim interface 0 before use [160056.382590] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160058.242638] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use [160058.243044] usb 1-1.2: usbfs: process 334 (usbhid-ups) did not claim interface 0 before use 223920.728609] usb 1-1.2: USB disconnect, device number 5 -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: October 16, 2016 11:47 PM UTC Time: October 16, 2016 9:47 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> 2016-10-10 15:28 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>:> The UPS seems to disconnect totally, i need to physically disconnect the > cable to get the UPS connected again. > A reboot is not enough.Ouch, this is more severe than what I thought. As a first step, you could try and increase the timeouts for pollfreq and pollinterval. Again, a log (compressed) of the driver running in debug mode when those problems occur would be helpful. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161019/e20a6955/attachment-0001.html>
I have run nut driver in debug level 6. Here is the log: http://www.filedropper.com/ups_1 Please have a look, i cannot see a pattern since i dont know what to look for. DMESG: [269391.234426] hid-generic 0003:06DA:FFFF.0003: hiddev0,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-20980000.usb-1.2/input0 [285040.957004] usb 1-1.2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 ret -75 -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: October 16, 2016 11:47 PM UTC Time: October 16, 2016 9:47 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> 2016-10-10 15:28 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>:> The UPS seems to disconnect totally, i need to physically disconnect the > cable to get the UPS connected again. > A reboot is not enough.Ouch, this is more severe than what I thought. As a first step, you could try and increase the timeouts for pollfreq and pollinterval. Again, a log (compressed) of the driver running in debug mode when those problems occur would be helpful. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161020/88330fd9/attachment.html>
Was anybody able to read the logs and come up with an error? -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: October 16, 2016 11:47 PM UTC Time: October 16, 2016 9:47 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> 2016-10-10 15:28 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>:> The UPS seems to disconnect totally, i need to physically disconnect the > cable to get the UPS connected again. > A reboot is not enough.Ouch, this is more severe than what I thought. As a first step, you could try and increase the timeouts for pollfreq and pollinterval. Again, a log (compressed) of the driver running in debug mode when those problems occur would be helpful. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161107/5f4c16d3/attachment.html>