3:45 p.m.
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.
thanks
3:53 p.m.
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.
thanks
I vote for squeeze. I too like Tripp Lite products and have for many
years. Maybe someone in the Fedora infrastructure could write them a
letter? Or send Luca Brasi?
--Doc Savage
Fairview Heights, IL
3:59 p.m.
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
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- grep me no patterns and I'll tell you no lines -
----------------------------------------------------------------------
4:08 p.m.
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/
Thanks. I will give it a try. My unit is listed.
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
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- grep me no patterns and I'll tell you no lines -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
4:25 p.m.
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.
5:05 p.m.
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
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- I don't suffer from insanity...I enjoy every minute of it! -
----------------------------------------------------------------------
5:15 p.m.
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?
thanks
6:02 p.m.
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.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- If Windows isn't a virus, then it sure as hell is a carrier! -
----------------------------------------------------------------------
6:27 p.m.
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???
6:27 p.m.
On 02/09/2017 04: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.
Oh, I forgot one thing. Make sure you add the udev rule needed. On my
system, you'd need to:
sudo cp /lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d
sudo udevadm -R (or reboot to make sure the new rule is used)
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Overweight: When you step on your dog's tail...and it dies. -
----------------------------------------------------------------------
7:01 p.m.
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(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- If your broker is so damned smart...why is he still working? -
----------------------------------------------------------------------
5:14 p.m.
On 02/09/2017 05:01 PM, Rick Stevens wrote:
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.
Bear with me, gang. I don't mean to revive this thread too much, but
I've been curious if Robert got nut to work for him on his Tripplite
UPS.
I just bought a Cyberpower UPS myself (they're doing a lot of
road work around me and the power's blipped several times) and I was
just going to start setting up nut to talk to it. While mine is not a
TrippLite, it does use a USB port for communications and it should be
similar. If you got it to work, Robert, great! If not, contact me off
list and I'll try to help. I hope to have mine functional tonight.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Always remember you're unique, just like everyone else. -
----------------------------------------------------------------------
8:30 p.m.
On Tue, Feb 14, 2017 at 03:14:28PM -0800, Rick Stevens wrote:
On 02/09/2017 05:01 PM, Rick Stevens wrote:
> 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.
Bear with me, gang. I don't mean to revive this thread too much, but
I've been curious if Robert got nut to work for him on his Tripplite
UPS.
I just bought a Cyberpower UPS myself (they're doing a lot of
road work around me and the power's blipped several times) and I was
just going to start setting up nut to talk to it. While mine is not a
TrippLite, it does use a USB port for communications and it should be
similar. If you got it to work, Robert, great! If not, contact me off
list and I'll try to help. I hope to have mine functional tonight.
Depending on the Cyberpower model, they offer Linux software for
shutting down your system on power failure, and you can define
a delay, and have it send email.
As I recall, it is all shellscripts, so its easy to hack.
I have one at work, so it is connected to my Linux workstation, and
I hacked the appropriate shellscript to send a shutdown command
to my windoze box a minute or two before Linux shuts down.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Always remember you're unique, just like everyone else. -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
I can do all things through Christ
who strengthens me.
------------------------------ Philippians 4:13 -------------------------------
8:34 p.m.
On 02/14/2017 06:30 PM, Fred Smith wrote:
On Tue, Feb 14, 2017 at 03:14:28PM -0800, Rick Stevens wrote:
> On 02/09/2017 05:01 PM, Rick Stevens wrote:
>> 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.
>
> Bear with me, gang. I don't mean to revive this thread too much, but
> I've been curious if Robert got nut to work for him on his Tripplite
> UPS.
>
> I just bought a Cyberpower UPS myself (they're doing a lot of
> road work around me and the power's blipped several times) and I was
> just going to start setting up nut to talk to it. While mine is not a
> TrippLite, it does use a USB port for communications and it should be
> similar. If you got it to work, Robert, great! If not, contact me off
> list and I'll try to help. I hope to have mine functional tonight.
Depending on the Cyberpower model, they offer Linux software for
shutting down your system on power failure, and you can define
a delay, and have it send email.
As I recall, it is all shellscripts, so its easy to hack.
I have one at work, so it is connected to my Linux workstation, and
I hacked the appropriate shellscript to send a shutdown command
to my windoze box a minute or two before Linux shuts down.
Thanks, Fred, but Robert had a Tripplite. I bought the Cyberpower for
my own use, but since nut will use the same driver as the Tripplite, I
figured I'd get nut up on it and offer the configs to Robert. Besides,
I'd just like to set up nut again after all these years (yes, I'm a
glutton for punishment).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- "Celibacy is not hereditary." -
- -- Guy Goden -
----------------------------------------------------------------------
10:49 p.m.
On 02/14/2017 05:14 PM, Rick Stevens wrote:
I just bought a Cyberpower UPS myself (they're doing a lot of
road work around me and the power's blipped several times) and I was
just going to start setting up nut to talk to it. While mine is not a
TrippLite, it does use a USB port for communications and it should be
similar.
I have two Cyberpower UPSs, one that runs the computers and one that is just monitored and
runs telephone base stations. I've attached diffs that show what I did to the supplied
nut configuration files in /etc/ups. The name "upsmon" is just an arbitrary name
I chose for UPS control access. It is not a login name on the system.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
2:05 p.m.
On 02/14/2017 08:49 PM, Robert Nichols wrote:
On 02/14/2017 05:14 PM, Rick Stevens wrote:
> I just bought a Cyberpower UPS myself (they're doing a lot of
> road work around me and the power's blipped several times) and I was
> just going to start setting up nut to talk to it. While mine is not a
> TrippLite, it does use a USB port for communications and it should be
> similar.
I have two Cyberpower UPSs, one that runs the computers and one that is
just monitored and runs telephone base stations. I've attached diffs
that show what I did to the supplied nut configuration files in
/etc/ups. The name "upsmon" is just an arbitrary name I chose for UPS
control access. It is not a login name on the system.
Yeah, mine came up just fine as well, once you sort out getting udev
to re-read its rules ("udevadm command -R") and unplug/replug the USB
cable to the UPS so the USB device's ownership and access mode changes
due to the rule (becomes group "dialout" with mode 0664).
To paraphrase the Stormtrooper at Mos Eisley in Star Wars episode IV,
"You weren't the Robert we're looking for."
The Robert that had the Tripplite was Robert Moscowitz and I was trying
to help him a bit. Now that I have fresh experience with nut, I can
help him with more detail, should he still be watching the list.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Is it progress if a cannibal uses a knife and fork? -
- -- Stanislaw J. Lec -
----------------------------------------------------------------------
10:03 p.m.
On 02/15/2017 02:05 PM, Rick Stevens wrote:
On 02/14/2017 08:49 PM, Robert Nichols wrote:
> On 02/14/2017 05:14 PM, Rick Stevens wrote:
>> I just bought a Cyberpower UPS myself (they're doing a lot of
>> road work around me and the power's blipped several times) and I was
>> just going to start setting up nut to talk to it. While mine is not a
>> TrippLite, it does use a USB port for communications and it should be
>> similar.
>
> I have two Cyberpower UPSs, one that runs the computers and one that is
> just monitored and runs telephone base stations. I've attached diffs
> that show what I did to the supplied nut configuration files in
> /etc/ups. The name "upsmon" is just an arbitrary name I chose for UPS
> control access. It is not a login name on the system.
Yeah, mine came up just fine as well, once you sort out getting udev
to re-read its rules ("udevadm command -R") and unplug/replug the USB
cable to the UPS so the USB device's ownership and access mode changes
due to the rule (becomes group "dialout" with mode 0664).
To paraphrase the Stormtrooper at Mos Eisley in Star Wars episode IV,
"You weren't the Robert we're looking for."
The Robert that had the Tripplite was Robert Moscowitz and I was trying
to help him a bit. Now that I have fresh experience with nut, I can
help him with more detail, should he still be watching the list.
No apologies. Even re-reading what you wrote, it still sounds to me like you are wondering
how to set up a Cyberpower UPS in nut. "I just bought a Cyberpower UPS myself ... and
I was just going to start setting up nut to talk to it." What the heck else was I
supposed to think?
And BTW for anyone who noticed, the passwords that I inadvertently left in those diffs
were for an old setup and not current.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
2619
days inactive
2626
days old
16 comments
5 participants
participants (5)
-
dsavage＠peaknet.net -
Fred Smith -
Rick Stevens -
Robert Moskowitz -
Robert Nichols