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>
The huge log doesn't show anything troublesome or problematic. The part of the driver output you posted on your third-to-last email only shows that the device disconnects and then it doesn't reconnect, or, at least, the driver doesn't see it: - At that point, does the device reconnet to the system? (Does it show up on dmesg? What does `lsusb -d 06da:ffff -v` return?) - It could be helpful to know what happened just before the disconnection to see if there is any correlation with driver activity: any chance you have the log of the driver running in debug mode till that point? A fair guess could be that the device is already busy doing something and considers communication of a lower priority and hence stops it. Were this the case (but, then, I would expect the device to reconnect and the driver to restart communication), a 'full update' would likely be the culprit, and hence increasing 'pollfreq', while not curing the problem, could at least decrease the chance of experiencing it.
Hi, - The device never re-connects to the system, i have to physically remove the USB plug and insert it again for the device to come back. - This does not happen when running the driver from the supplier. (java process) - When i poll every 60s it works for about 3 days, anything lower or higher causes it to disconnect faster - The big log i sent is not the output of the driver? if not how can i enable that ? Thank you for your time.. -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: November 9, 2016 12:54 AM UTC Time: November 8, 2016 11:54 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> The huge log doesn't show anything troublesome or problematic. The part of the driver output you posted on your third-to-last email only shows that the device disconnects and then it doesn't reconnect, or, at least, the driver doesn't see it: - At that point, does the device reconnet to the system? (Does it show up on dmesg? What does `lsusb -d 06da:ffff -v` return?) - It could be helpful to know what happened just before the disconnection to see if there is any correlation with driver activity: any chance you have the log of the driver running in debug mode till that point? A fair guess could be that the device is already busy doing something and considers communication of a lower priority and hence stops it. Were this the case (but, then, I would expect the device to reconnect and the driver to restart communication), a 'full update' would likely be the culprit, and hence increasing 'pollfreq', while not curing the problem, could at least decrease the chance of experiencing it. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161109/aceac0be/attachment.html>