<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Jan 2, 2015, at 3:33 PM, Mike Raath <<a href="mailto:raathm@gmail.com">raathm@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Sorry, I messed up my reply a bit.<div><br></div><div>The output of the lsusb command is the same before and after the data goes stale.</div><div><br></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">$ lsusb -d 0665:</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial</div></div><div><br></div></div></blockquote><div>OK. That usually means that the VM kernel doesn't see that the device is disconnecting. You can check dmesg to be sure, but the Device numbers usually increment the next time a USB device is plugged in.</div><div><br></div><div>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.</div><br><blockquote type="cite"><div dir="ltr"><div>And the output of the <span style="font-family:Menlo;font-size:11px">/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 </span>command is the same as in the previous attachment. I truncated the "before" log because it just carried on with the same output after the broadcast notification that the UPS became unavailable (at 214.883342).</div></div><div class="gmail_extra"></div></blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">Hmm, that's odd.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I forgot to mention: be sure that there are no existing drivers running ('sudo killall blazer_usb' and 'sudo killall nutdrv_qx') before starting the driver in debug mode.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Can you run it again with <b>three</b> "-D" flags, and let it go past the point where upsd complains? The third "-D" will show all read and write results, which should definitely be different when problems arise.</div><div class="gmail_extra"><br></div><blockquote type="cite"><div class="gmail_extra"><div class="gmail_quote">On 2 January 2015 at 22:14, Mike Raath <span dir="ltr"><<a href="mailto:raathm@gmail.com" target="_blank">raathm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div dir="ltr">Ok - before stale data:<div><br></div><div>After stale data:</div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">$ lsusb -d 0665:</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"><br></div><p style="margin:0px;font-size:11px;font-family:Menlo"></p><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"></div><div><br class="webkit-block-placeholder"></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">After stale data:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">And the gzipped log attached:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"><br></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 2 January 2015 at 21:56, Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span>On Jan 2, 2015, at 2:43 PM, Mike Raath <<a href="mailto:raathm@gmail.com" target="_blank">raathm@gmail.com</a>> wrote:<br><div><br><blockquote type="cite"><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Not sure what other logs I can provide to try to troubleshoot this?</div><br></blockquote></div><div><br></div></span><div>Two things:</div><div><br></div><div>- the output of 'lsusb -d 0665:' before and after the 'stale data' warning</div><div>- the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee /tmp/nutdrv_qx.log'</div><div><br></div><div>(Please gzip nutdrv_qx.log before sending it, thanks.)</div><span><font color="#888888"><br><div>
<span style="border-collapse:separate;border-spacing:0px"><div>-- </div><div>Charles Lepple</div><div>clepple@gmail</div><div><br></div></span><br>
</div>
<br></font></span></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
_______________________________________________<br>Nut-upsuser mailing list<br><a href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div>A: Because it messes up the order in which people normally read text.</div><div>Q: Why is top-posting such a bad thing?</div><div>A: Top-posting.</div><div>Q: What is the most annoying thing on usenet and in e-mail?</div></div></div></span></span>
</div>
<br></body></html>