[Nut-upsuser] NUT Installation failing under Debian Jessie

2014-09-29 Thread Leslie Rhorer
I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl

Re: [Nut-upsuser] Tripp-Lite USB constantlly disconnecting.

2014-09-29 Thread Shade Alabsa
Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran usbhid-ups -a upsunit -DDD output.log and I have attached the

Re: [Nut-upsuser] Tripp-Lite USB constantlly disconnecting.

2014-09-29 Thread Shade Alabsa
Charles, What is the new behavior? The CentOS minimal install had different print statements and a broadcast message whenever the UPS was disconnected. The broadcast isn't really important. Below are the differences I pasted though I'm not sure if they are important, I just noticed they

Re: [Nut-upsuser] TRIPPLITE OMNIVSINT80 Compatibility

2014-09-29 Thread Dave Williams
OMNIVS1000 USB (older; product ID: 0001) is shown correctly so maybe the OMNIVSING800 just needs to be added to the list next to it. Will do. Don't see the model in the compatibility web page yet at http://www.networkupstools.org/stable-hcl.html. Am I missing something? Dave

Re: [Nut-upsuser] TRIPPLITE OMNIVSINT80 Compatibility

2014-09-29 Thread Charles Lepple
On Sep 29, 2014, at 3:28 PM, Dave Williams d...@opensourcesolutions.co.uk wrote: OMNIVS1000 USB (older; product ID: 0001) is shown correctly so maybe the OMNIVSING800 just needs to be added to the list next to it. Will do. Don't see the model in the compatibility web page yet at

Re: [Nut-upsuser] Tripp-Lite USB constantlly disconnecting.

2014-09-29 Thread Charles Lepple
On Sep 29, 2014, at 12:50 PM, Shade Alabsa shade34...@gmail.com wrote: The lsusb command did not trigger a disconnect. The output of that command is below. If you run lsusb several times, does it still work? The exact output of lsusb isn't as important as whether anything gets logged by