Displaying 3 results from an estimated 3 matches for "modemtools".
Did you mean:
modeltools
2015 Jan 02
0
Data stale error after short while
Sorry, I messed up my reply a bit.
The output of the lsusb command is the same before and after the data goes
stale.
$ lsusb -d 0665:
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is
the same as in the previous attachment. I truncated the "before" log
because it just carried on with
2015 Jan 02
2
Data stale error after short while
Ok - before stale data:
After stale data:
$ lsusb -d 0665:
Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
After stale data:
And the gzipped log attached:
On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote:
>
> Not sure what other logs I can provide to try
2015 Jan 02
3
Data stale error after short while
...disconnecting. You can check dmesg to be sure, but the Device numbers usually increment the next time a USB device is plugged in.
Not sure how ESXi hands off the USB devices to the VMs, but is there a way to verify that other VMs are not seeing the UPS as well? Even simply probing the device (a la modemtools) will cause problems, especially if the USB-to-serial converter usually shows up as /dev/ttyUSB0 before NUT drivers start.
> And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is the same as in the previous attachment. I truncated the "before" log because i...