Lars, the log ends around 41998 seconds (~ 11 1/2 hours) and, till
that point, from what I can see, nothing strange happens: both the
interrupt pipe and polling work as expected.
Now, you mentioned that something changes when you alter the polling
frequency (I think you refer to 'pollfreq' and not
I dont think the logs ends to early.
The UPS had been offline for 1 day at least before i stopped the process.
Could the issue be that NUT driver does not see the USB device disconnect?
Original Message
Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD
Local Time: 11
On 11/10/2016 07:12 PM, hyo...@gmail.com wrote:
> 2016-11-09 14:57 GMT+01:00 Lars de Bruin :
>> - 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 is my log with a Tripplite SMART1500LCDT on CentOS-6 with
n
2016-11-09 14:57 GMT+01:00 Lars de Bruin :
> 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)
Ok, if they do, we sho
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
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
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: hyo...@gmail.com
To: Lars de Bruin
nut-upsuser
2016-10-10 15
-2098.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: hyo
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: hyo...@gmail.com
To: Lars de Bruin
2016-10-10 15:28 GMT+02:00 Lars de Bruin :
> 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 pollfr
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: hyo...@gmail.com
To: Lars de Bruin
nut-upsuser
2016-10-03 14:56 GMT+02:00 Lars de Bruin :
> Hi,
>
> The U
2016-10-03 14:56 GMT+02:00 Lars de Bruin :
> 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
Hi,
The UPS is now connected via HID-USB, but seems to randomly disconnect.
Sometimes after a few hours, other times days...
Any suggestions?
Original Message
Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD
Local Time: October 2, 2016 11:50 PM
UTC Time: October 2, 2016
> [powerwalker]
>driver = blazer_usb
>vendorid = 06da
>port = auto
>desc = "Powerwalker VI 2200VA LCD"
>productid =
>bus = "001"
The VID/PID combo 06da/ is used by some devices supported by the
'usbhid-ups' driver: did you have a chance to t
14 matches
Mail list logo
