On 02/09/2017 04:27 PM, Robert Moskowitz wrote: > > > On 02/09/2017 07:02 PM, Rick Stevens wrote: >> On 02/09/2017 03:15 PM, Robert Moskowitz wrote: >>> >>> On 02/09/2017 06:05 PM, Rick Stevens wrote: >>>> On 02/09/2017 02:25 PM, Robert Moskowitz wrote: >>>>> On 02/09/2017 04:59 PM, Rick Stevens wrote: >>>>>> On 02/09/2017 01:45 PM, Robert Moskowitz wrote: >>>>>>> Tripp Lite has their UPS management software available for Fedora >>>>>>> >>>>>>> Fedora 8 >>>>>>> >>>>>>> that is. SHEESH! >>>>>>> >>>>>>> Other that squeezing the source out of them and doing a build on a >>>>>>> more >>>>>>> modern Fedora, does anyone know of a UPS management software that >>>>>>> will >>>>>>> work with Tripp Lite UPS? >>>>>>> >>>>>>> BTW, I have been using Tripp Lite products since '84, so please >>>>>>> don't >>>>>>> recommend another brand of UPS. >>>>>>> >>>>>> Have you looked at NUT (Network Ups Tools)? It handles Tripp Lite >>>>>> and a >>>>>> whole bunch of others. Here's a list of the Tripp Lite stuff it >>>>>> manages: >>>>>> >>>>>> http://networkupstools.org/ddl/Tripp_Lite/ >>>>>> >>>>>> It's available from the standard repos: >>>>>> >>>>>> nut.x86_64 2.7.4-4.fc25 fedora >>>>>> nut-cgi.x86_64 2.7.4-4.fc25 fedora >>>>>> nut-client.x86_64 2.7.4-4.fc25 fedora >>>>>> nut-devel.x86_64 2.7.4-4.fc25 fedora >>>>>> nut-xml.x86_64 2.7.4-4.fc25 fedora >>>>>> >>>>> Looks like I need usbhid-ups, but can't find it. >>>>> >>>>> Plus little information on how to work with this interface. >>>> That's part of the main nut package, along with a man page: >>>> >>>> [root@prophead ~]# rpm -ql nut | grep usbhid >>>> /usr/sbin/usbhid-ups >>>> /usr/share/man/man8/usbhid-ups.8.gz >>> OK. I did not have the cable plugged in right to the UPS. >>> >>> I am now seeing /dev/hidraw0, but NUT wants a host/port. I assume >>> localhost, but what port is hidraw0 mapping to? >> I don't use nut myself, but grazing the man pages, you'd use >> something like this in the ups.conf file: >> >> [tripplite] >> driver = usbhid-ups >> port = auto >> vendorid = <vendor-id-from-lsusb> >> >> Do an "lsusb" and see what vendor ID is shown for your UPS. For example, >> scanning my USB bus, I see this sort of thing: >> >> [root@prophead ups]# lsusb >> Bus 002 Device 002: ID 8087:8001 Intel Corp. >> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> Bus 001 Device 002: ID 8087:8009 Intel Corp. >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> Bus 004 Device 002: ID 0bc2:ab21 Seagate RSS LLC Backup Plus Slim >> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >> Bus 003 Device 004: ID 0411:00a2 BUFFALO INC. (formerly MelCo., Inc.) >> >> I do NOT have a Tripp Lite UPS, but let's just say that the "BUFFALO >> INC." thing is my Tripp Lite. I'd set up my ups.conf thus: >> >> [tripplite] >> driver = usbhid-ups >> bus = "003" >> port = auto >> vendorid = 0411 >> >> The "bus = " isn't really necessary, but it'll keep the system from >> scanning ALL of your USB buses. I think that's all you need. > > I am doing this on another system and am looking back and forth between > screens... > > So in /etc/ups/ups.conf I have added: > > [SMART1000LCD] > driver = usbhid-ups > port = auto > bus = "003" > vendorid = 09ae > > I start up the NUT gui and it is showing host of localhost and port of 3493 > > and 'error connecting to localhost' connection refused. > > so what port is auto going to? Since this is localhost, I am not > supposed to set a firewalld rule for whatever port it is??? I think there's several things you need to do: 1. You shouldn't need to make any holes in your firewall if you're using "localhost". If you want a remote machine to access your upsd stuff, then yes, you need to poke a hole in your firewall for that port to allow the remote machine access. 2. Make sure that udev rule I mentioned is in place and udev has been reloaded. 3. The NUT GUI needs to talk to the upsd daemon (which probably isn't running yet). You probably need to start the drivers first via: systemctl start nut-driver.service then start the upsd daemon via: systemctl start nut-server.service At that point, the NUT GUI should be able to talk to the upsd daemon via whichever host and port is listed in the /etc/ups/upsd.conf file's "LISTEN" directive (by default, localhost and port 3493). 4. If it all works as you want, don't forget to set nut-driver.service and nut-server.service to start at boot by doing: systemctl enable nut-driver.service systemctl enable nut-server.service Have a good look at the steps here: http://tedfelix.com/software/nut-network-ups-tools.html Pretty useful. I haven't used NUT in a LONG time, and that was back when it only spoke to UPS devices via serial ports (yes, I'm that old), so this is all my interpretations of the documentation and drawing on fairly crusty old memory cells rattling around in my head. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - If your broker is so damned smart...why is he still working? - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
