<div dir="ltr">Hi Charles,<div><br></div><div>Thank you for sticking with me through this!</div><div><br></div><div>Well, whaddya know, when run with -DDDDD it works! upsc consistently returns data. Maybe it's a timing thing, or a select affected by I/O or something tricky like that. Nonetheless, I ran it, hit upsc eaton multiple times, collected the output and attached it. If this doesn't give you what you need, I can retry with fewer/more D's or whatever you like.</div><div><br></div><div>I see upstart and systemd.</div><div><br></div><div><div># ps aux | egrep '[s]ystemd|[u]pstart'</div><div>root 527 0.0 0.0 18208 1740 ? S May03 0:00 upstart-udev-bridge --daemon</div><div>root 567 0.0 0.0 36784 1904 ? Ss May03 0:00 /lib/systemd/systemd-udevd --daemon</div><div>root 582 0.0 0.0 15404 740 ? S May03 0:00 upstart-file-bridge --daemon</div><div>root 614 0.0 0.0 30724 1648 ? Ss May03 0:00 /lib/systemd/systemd-logind</div><div>root 867 0.0 0.0 15260 648 ? S May03 0:00 upstart-socket-bridge --daemon</div></div><div><br></div><div>Apparmor is present, but disabled due to another application's requirements:</div><div><br></div><div><div># apparmor_status</div><div>apparmor module is loaded.</div><div>0 profiles are loaded.</div><div>0 profiles are in enforce mode.</div><div>0 profiles are in complain mode.</div><div>0 processes have profiles defined.</div><div>0 processes are in enforce mode.</div><div>0 processes are in complain mode.</div><div>0 processes are unconfined but have a profile defined.</div></div><div><br></div><div>I couldn't find any crashes in dmesg, just this over and over:</div><div><br></div><div><div>[167914.284728] usb 6-1: USB disconnect, device number 21</div><div>[167915.292292] usb 6-1: new low-speed USB device number 22 using uhci_hcd</div><div>[167916.162823] usb 6-1: New USB device found, idVendor=0463, idProduct=ffff</div><div>[167916.162827] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4</div><div>[167916.162829] usb 6-1: Product: Ellipse PRO</div><div>[167916.162831] usb 6-1: Manufacturer: EATON</div><div>[167916.162833] usb 6-1: SerialNumber: G343F52229</div><div>[167919.940287] hid-generic 0003:0463:FFFF.0015: hiddev0,hidraw0: USB HID v1.10 Device [EATON Ellipse PRO] on usb-0000:00:1d.0-1/input0</div></div><div><br></div><div>Thank you,</div><div>Ken</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 4, 2016 at 11:00 PM, 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"><span class="">On May 4, 2016, at 10:01 AM, Ken Marsh <<a href="mailto:ken.marsh@sparkpost.com">ken.marsh@sparkpost.com</a>> wrote:<br>
><br>
> Is this actually functional? Usually I don't consider NUT operational until upsc works (among other things).<br>
<br>
</span>You're right, the "ups.status: WAIT" isn't fully functional. I am surprised, though, since the usual problem area is driver-to-hardware rather than upsd-to-driver.<br>
<br>
>From the state where everything has been started, what if you kill the driver, and restart it from the command line with five "-D" flags? I'm looking for a line like this: "0.008735 dstate_init: sock /var/tmp/macosx-ups-osx open on fd 3" (although it potentially might happen several times in your case). Please check upsc as well, and after a few cycles between the two messages, you can kill the driver and zip up the log.<br>
<br>
A few more background things (since I guess I skipped the non-LTS versions between Ubuntu 12.04 and 14.04): which init system does this version run? Do you know if there are any apparmor profiles that might be preventing the driver and upsd from talking? Any crash messages in dmesg?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Charles Lepple<br>
clepple@gmail<br>
<br>
<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div><br><div class="gmail_signature"><div dir="ltr"><p><span><b></b></span></p></div></div>
</div></div>